Update grantedTo structure in permissions overview

[dylanstetts]

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.

[learn-build-service-prod]

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.

[FaithOmbongi]

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.

[dylanstetts]

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.,

[FaithOmbongi]

Hi @dylanstetts - I see the property's return type, sharePointIdentitySet, is a little different so likely, application isn't the only required property. I'm adding the SME team, @spgraph-docs-team to assist.

[Danipocket]

@dluces , @shweta-bedmutha, is this something that you could help us with? It seems that the issue derives from this issue. It's not clear how to configure a specific property. The customer proposed valid changes but it would be good to use the new property instead of the deprecated property. The SharePoint folks can help make the related documentation clearer, including possible providing better examples._

I appreciate your help.

[dluces]

Thanks @Danipocket. I've asked the product group to look into this. It makes sense that the API supports the new request properties and not just the deprecated one.

[dluces]

The contribution is correct in that grantedToIdentitiesV2 is not currently supported by the endpoint but grantedToIdentities is. That said, the product team is looking at prioritizing supporting for the non-deprecated properties. There's no ETA for this at the moment. @Danipocket / @FaithOmbongi can we approve this in the meantime while the product team works on updating functionality and then we can update the docs to use the non-deprecated properties?

[dylanstetts]

Hi @FaithOmbongi and @Danipocket, following up on this request to approve this change. Let me know what else is needed from my side.

[FaithOmbongi]

Approving and merging based on feedback from the product team.