Skip to content

Fix broken link error#9944

Merged
FaithOmbongi merged 1 commit into
mainfrom
FaithOmbongi-patch-5
Jun 22, 2026
Merged

Fix broken link error#9944
FaithOmbongi merged 1 commit into
mainfrom
FaithOmbongi-patch-5

Conversation

@FaithOmbongi

Copy link
Copy Markdown
Contributor

Important

Use the AI-powered workflow for Graph onboarding to author and self-review schema-related changes. See https://aka.ms/msgo for more information.

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

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.

@FaithOmbongi FaithOmbongi enabled auto-merge (squash) June 22, 2026 16:31
@microsoft-github-policy-service microsoft-github-policy-service Bot added the do not merge Use this label to indicate to the repository admins that your PR Is not ready to merge into master. label Jun 22, 2026
@github-actions github-actions Bot added this to the Community Contributions milestone Jun 22, 2026
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 391d709:

✅ Validation status: passed

File Status Preview URL Details
changelog/Microsoft.M365.Defender.json ✅Succeeded

For more details, please refer to the build report.

@FaithOmbongi FaithOmbongi merged commit 0ea9afd into main Jun 22, 2026
9 checks passed
@FaithOmbongi FaithOmbongi deleted the FaithOmbongi-patch-5 branch June 22, 2026 16:38
@FaithOmbongi FaithOmbongi changed the title Simplify description for protectionRule addition Fix broken link error Jun 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Use this label to indicate to the repository admins that your PR Is not ready to merge into master.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant