Skip to content

Clarify role assignment requirements for delegated scenarios - #10030

Closed
Yuan Karppanen (yyuank) wants to merge 1 commit into
microsoftgraph:mainfrom
yyuank:patch-5
Closed

Clarify role assignment requirements for delegated scenarios#10030
Yuan Karppanen (yyuank) wants to merge 1 commit into
microsoftgraph:mainfrom
yyuank:patch-5

Conversation

@yyuank

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/msgraphcdk 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.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 80328e9:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/includes/users-passwordprofile-permissions.md ✅Succeeded

For more details, please refer to the build report.

@yyuank

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 28, 2026
@CelesteDG

Copy link
Copy Markdown
Collaborator

Closing this public PR as the equivalent change was made in the private repo.

learn-build-service-prod Bot pushed a commit that referenced this pull request Aug 28, 2026
Ports the change from #10030.

Co-authored-by: Yuan Karppanen <46729835+yyuank@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: e5a42631-965d-48c7-863d-51a4606d9b60
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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