Skip to content

Update legacy alerts API retirement date - #10007

Open
Mor Moverman (mormov) wants to merge 1 commit into
microsoftgraph:mainfrom
mormov:patch-1
Open

Update legacy alerts API retirement date#10007
Mor Moverman (mormov) wants to merge 1 commit into
microsoftgraph:mainfrom
mormov:patch-1

Conversation

@mormov

Copy link
Copy Markdown
Contributor

Updates the legacy Microsoft Graph security alerts API retirement date from August 31, 2026 to October 15, 2026 in the migration guidance.

This is a documentation-only date update; no API/schema changes.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 34399c8:

✅ Validation status: passed

File Status Preview URL Details
concepts/alertsv1-alertsv2-migration.md ✅Succeeded

For more details, please refer to the build report.

@mormov

Copy link
Copy Markdown
Contributor Author

#sign-off

@microsoft-github-policy-service microsoft-github-policy-service Bot added the ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master. label Aug 3, 2026
@@ -12,12 +12,12 @@ ms.topic: upgrade-and-migration-article

# Migrate from legacy alerts to the alerts and incidents API

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello Mor Moverman (@mormov),

please validate the following topics as they also contain the "old" retirement date.

Please, also update the What's new topic to increase the visibility of this change.

Thanks!

@mormov Mor Moverman (mormov) Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Jarbas Horst (@JarbasHorst) Thanks for pointing me to the 2 topics you linked above, I updated them as well and opened a PR for the fixes -
#10012

What's the What's new topic? How do I update it?

Will these changes fix the snippets in existing articles? (such as https://learn.microsoft.com/en-us/graph/api/resources/security-api-overview?view=graph-rest-1.0#legacy-alerts and https://learn.microsoft.com/en-us/graph/api/resources/alert?view=graph-rest-1.0)

Or do I need to commit changes to these articles directly as well?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Mor Moverman (@mormov), thanks for fixing the include files via PR https://github.com/microsoftgraph/microsoft-graph-docs-contrib/pull/10012/changes. Yes, these fixes will fix the snippets in the existing articles.

This is the link for the What's new topic: https://github.com/microsoftgraph/microsoft-graph-docs-contrib/blob/main/concepts/whats-new-overview.md

Please add the following section under "August 2026: New and generally available"

## August 2026: New and generally available

### Security

Updated the retirement date for the legacy Microsoft Graph [security alerts API](/graph/api/resources/alert) from August 31, 2026 to October 15, 2026.

@mormov Mor Moverman (mormov) Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, I added the section into the What's new topic.
Jarbas Horst (@JarbasHorst), Can you take a look to see if you see what I added? Not sure it was saved correctly.

And is anything still blocking this PR from being merged?

@JarbasHorst

Copy link
Copy Markdown
Contributor

Hi Mor Moverman (@mormov), Daniela Bonilla Montero (@Danielabom), this PR isn't ready to merge yet. Mor Moverman (@mormov), please take a look at my comment: #10007 (comment). Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aq-pr-triaged PR has been processed by the Aquent PR review team ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants