Skip to content

Conversation

@dylanstetts
Copy link
Contributor

Payload for POST request was incorrect; updated to reflect the correct payload, including grantedToIdentities/application with id AND displayName

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): N/A

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.

Payload for POST request was incorrect; updated to reflect the correct payload, including grantedToIdentities/application with id AND displayName
@dylanstetts dylanstetts added customer support issue Doc issue raised from customer support ready for content review PR is ready for a content review - content development and tech review are complete. labels Dec 30, 2025
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 8d00319:

✅ Validation status: passed

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

For more details, please refer to the build report.

Copy link
Contributor

@FaithOmbongi FaithOmbongi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @dylanstetts for propsing these fixes. While your changes are valid, I also note that the grantedToIdentities property is deprecated in favor of grantedToIdentitiesV2. If you don't mind, can you update the sample to use grantedToIdentitiesV2? Or if you prefer, I can push this to the product team to update the article. Your contribution is very welcome.

@FaithOmbongi FaithOmbongi self-assigned this Dec 30, 2025
@FaithOmbongi FaithOmbongi added awaiting internal response changes requested content review in progress and removed ready for content review PR is ready for a content review - content development and tech review are complete. labels Dec 30, 2025
@dylanstetts
Copy link
Contributor Author

Hi @FaithOmbongi, the request payload only accepts grantedToIdentities, so the proposed changes I made are the only supported, working payload to send to the endpoint as of today.

I.e.,

WorkingV1 NotWorkingV2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants