Skip to content

Update permissions-reference.md#9840

Open
anders-alex wants to merge 1 commit intomicrosoftgraph:mainfrom
anders-alex:updates
Open

Update permissions-reference.md#9840
anders-alex wants to merge 1 commit intomicrosoftgraph:mainfrom
anders-alex:updates

Conversation

@anders-alex
Copy link
Copy Markdown

The consentrequest.create perm shows the same verbiage as the "consentrequest.read" perm , and I do believe it should read that it allows the app to "create" a consent request, not just read the request. But if this is true and simply ambiguous, I also need to know that.

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.

Th consentrequest.create perm shows the same verbiage as the "consentrequest.read" perm , and I do believe it should read that it allows the app to "create" a consent request, not just read the request. But if this is true and simply ambiguous, I also need to know that.
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit c66b08f:

✅ Validation status: passed

File Status Preview URL Details
concepts/permissions-reference.md ✅Succeeded

For more details, please refer to the build report.

@Danipocket
Copy link
Copy Markdown
Contributor

Hi @anders-alex, thanks for contributing to the public repo. Are you a MSFTE? If so, please use the private repo. Thanks!

@Danipocket Danipocket added the blocked PRs that are blocked from content review or getting merged for some reason. label Mar 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blocked PRs that are blocked from content review or getting merged for some reason.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants