Update legacy alerts API retirement date - #10007
Conversation
|
Learn Build status updates of commit 34399c8: ✅ Validation status: passed
For more details, please refer to the build report. |
|
#sign-off |
microsoft-github-policy-service
Bot
added
the
ready to merge
| @@ -12,12 +12,12 @@ ms.topic: upgrade-and-migration-article | |||
|
|
|||
| # Migrate from legacy alerts to the alerts and incidents API | |||
There was a problem hiding this comment.
Hello Mor Moverman (@mormov),
please validate the following topics as they also contain the "old" retirement date.
- api-reference/beta/includes/security-alerts-v1-deprecation.md
- api-reference/v1.0/includes/security-alerts-v1-deprecation.md
Please, also update the What's new topic to increase the visibility of this change.
Thanks!
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Jarbas Horst (@JarbasHorst) Any update on this?
|
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! |
Regan Downer (v-regandowner)
added
the
aq-pr-triaged
David1997sb
removed
the
ready to merge
|
Jarbas Horst (@JarbasHorst) David1997sb Can someone please explain why this hasn't been merged yet??? |
Hi David1997sb, Danipocket, would it be best for Mor Moverman (@mormov) to open this PR in the [private repo](https://github.com/microsoftgraph/microsoft-graph-docs instead, so we can get it merged? |
|
Jarbas Horst (@JarbasHorst) David1997sb Danipocket Any updates?? |
|
#sign-off |
microsoft-github-policy-service
Bot
added
the
ready to merge
|
Jarbas Horst (@JarbasHorst) David1997sb and Danipocket - Following up on behalf of Mor Moverman (@mormov) and checking in with you about this PR and if there's anything else. Thank you. |
* Update legacy alerts API retirement date Ported from #10007. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add revised alerts API retirement date to What's New Ported from #10029. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Mor Moverman <312480154+mormov@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
5 participants
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.