Microsoft Graph
/v1.0/security/alerts/* endpoint removal
Stopped workingSubscribe to Microsoft GraphShare
The /v1.0/security/alerts/* endpoints were retired on October 15, 2026. Microsoft Graph deprecated this legacy alerts API, and requests made to these endpoints fail since that date.
Calls it hits
/v1.0/security/alerts/*
What to use instead of these calls
Migrate to the alerts and incidents API (/security/alerts_v2).
In Microsoft Graph's words
The legacy alerts API is deprecated and will be retired on October 15, 2026.
Facts
- API
- Microsoft Graph
graph.microsoft.com - Kind
- Endpoint removal
- Announced
- April 15, 2024
- Takes effect
- October 15, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Microsoft Graph's own pages
Questions
When does this change take effect?
Calls to /v1.0/security/alerts/* on Microsoft Graph stopped working on October 15, 2026.
What happens to calls after October 15, 2026?
They have failed since October 15, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Microsoft Graph 6
-
/v1.0/privacy/subjectRightsRequests*Endpoint removal Stopped working -
GET /v1.0/security/alertsEndpoint removal Stopped working -
GET /v1.0/me/drive/recentEndpoint removal Stops workingin 25 days -
GET /v1.0/me/drive/sharedWithMeEndpoint removal Stops workingin 25 days -
GET /v1.0/me/insights/sharedEndpoint removal Stops workingin 25 days -
GET /v1.0/me/insights/usedEndpoint removal Stops workingin 25 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.