Skip to content

Update deprecation notice for legacy alerts API#9896

Merged
FaithOmbongi merged 3 commits into
microsoftgraph:mainfrom
EdB-MSFT:patch-2
May 11, 2026
Merged

Update deprecation notice for legacy alerts API#9896
FaithOmbongi merged 3 commits into
microsoftgraph:mainfrom
EdB-MSFT:patch-2

Conversation

@EdB-MSFT
Copy link
Copy Markdown
Contributor

Removed the removal date for the legacy alerts API.

Important

Required for API changes:

  • [] Link to API.md file: ADD LINK HERE
  • [] Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE
  • [] Attach the documentation plan generated for AI-assisted docs authoring and validation to help speed up content review.

Add other supporting information, such as a description of the PR changes:

ADD INFORMATION HERE


Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

EdB-MSFT added 2 commits May 11, 2026 12:33
Removed the removal date for the legacy alerts API.
Updated deprecation notice for legacy alerts API and included a reference to the new alerts and incidents API.
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 94ce6ab:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/includes/security-alerts-v1-deprecation.md ✅Succeeded

For more details, please refer to the build report.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 804294c:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/includes/security-alerts-v1-deprecation.md ✅Succeeded
api-reference/v1.0/resources/security-api-overview.md ✅Succeeded

For more details, please refer to the build report.

Comment thread api-reference/v1.0/resources/security-api-overview.md Outdated
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit f516aee:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/includes/security-alerts-v1-deprecation.md ✅Succeeded
api-reference/v1.0/resources/security-api-overview.md ✅Succeeded

For more details, please refer to the build report.

@FaithOmbongi FaithOmbongi merged commit f25cac1 into microsoftgraph:main May 11, 2026
7 checks passed
@FaithOmbongi FaithOmbongi added the ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master. label May 11, 2026
learn-build-service-prod Bot added a commit that referenced this pull request May 11, 2026
…s://github.com/microsoftgraph/microsoft-graph-docs-contrib (branch main) (#28848)

* Add ServiceHealth to MCP Server scope (#9884)

* Remove preview mention and add ServiceHealth MCP Server scope

* Revert removal of preview info

* Apply suggestion from @FaithOmbongi

---------

Co-authored-by: Faith Moraa Ombongi <ombongi.moraa.fe@gmail.com>

* Update authenticationMethodsRegistrationCampaign details (#9888)

Updated the date and modified the description to include passkey support.

* Update beta authenticationMethodsRegistrationCampaign: date and passkey description (#9889)

Agent-Logs-Url: https://github.com/microsoftgraph/microsoft-graph-docs-contrib/sessions/75827775-1cd1-430a-a6cd-fc31c526c364

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: FaithOmbongi <14026935+FaithOmbongi@users.noreply.github.com>

* Update deprecation notice for legacy alerts API (#9896)

* Update deprecation notice for legacy alerts API

Removed the removal date for the legacy alerts API.

* Revise legacy alerts deprecation notice

Updated deprecation notice for legacy alerts API and included a reference to the new alerts and incidents API.

* Apply suggestion from @FaithOmbongi

---------

Co-authored-by: Faith Moraa Ombongi <ombongi.moraa.fe@gmail.com>

---------

Co-authored-by: Danipocket <88507770+Danipocket@users.noreply.github.com>
Co-authored-by: Mary-Katherine Bond Sims <mabond@microsoft.com>
Co-authored-by: Faith Moraa Ombongi <ombongi.moraa.fe@gmail.com>
Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com>
Co-authored-by: Justin Hall <Justinha@microsoft.com>
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: FaithOmbongi <14026935+FaithOmbongi@users.noreply.github.com>
Co-authored-by: Ed Baynash <105771311+EdB-MSFT@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: security 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.

2 participants