Skip to content

Commit c105709

Browse files
authored
Update alertsv1-alertsv2-migration.md
1 parent 5178692 commit c105709

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

concepts/alertsv1-alertsv2-migration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.topic: upgrade-and-migration-article
1212

1313
# Migrate from legacy alerts to the alerts and incidents API
1414

15-
The legacy Microsoft Graph security alerts API available through the `/security/alerts` endpoint is deprecated and will be retired on **August 31, 2026**. If your app currently uses the legacy alerts API to retrieve, monitor, or manage security alerts, you should migrate to the new [alerts and incidents API](/graph/api/resources/security-alert) in Microsoft 365 Defender.
15+
The legacy Microsoft Graph security alerts API available through the `/security/alerts` endpoint is deprecated and will be retired on **August 31, 2026**. If your app currently uses the legacy alerts API to retrieve, monitor, or manage security alerts, you should migrate to the new [alerts and incidents API](/graph/api/resources/security-alert) in Microsoft 365 Defender, available through the `/security/alerts_v2` endpoint.
1616

1717
This article describes the key differences between the two APIs, provides a field mapping reference, and outlines the steps to migrate your app.
1818

0 commit comments

Comments
 (0)