-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify access requirements for Search on SharePoint Embedded #10184
Clarify access requirements for Search on SharePoint Embedded #10184
Conversation
Learn Build status updates of commit df0eb63: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit 5f6586e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Interestingly, I'm not able to use the request review feature in PRs :) Pinging Cindy for interim approval |
Changes to auth article look good, ready to merge. I don't see an approve button only a merge button |
Learn Build status updates of commit f36af14: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Apologies, didn't have the review button in the top right-- approved now |
Category
Related issues
What's in this Pull Request?
We are instructing callers to request two scopes when using Microsoft Graph Search for SharePoint Embedded content:
Files.Read.All
(exceptional access pattern) andFileStorageContainer.Selected
(future contract). This will ensure their implementation is ready for the time when the contract aligns with the rest of the SPE model.Also, made the note for exceptional access patterns important instead.