-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Microsoft Graph - Application.ReadWrite.All perms #6750
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
base: main
Are you sure you want to change the base?
Conversation
Added Note to explain Microsoft Graph - Application.ReadWrite.All permissions. Customers are asking for more details as to why WAC requires this but PowerShell deployments do not. Feel free to follow up with cpuckett, arfong, and sushmad, if you need more details or clarification.
@cpuck : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Docs Build status updates of commit aa484f7:
|
File | Status | Preview URL | Details |
---|---|---|---|
WindowsServerDocs/manage/windows-admin-center/azure/azure-integration.md | Details |
WindowsServerDocs/manage/windows-admin-center/azure/azure-integration.md
- Line 36, Column 1: [Warning: invalid-note-section]
Text in the first line of Note/Section/Video is not valid. Will be rendered to <blockquote>
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #label:"aq-pr-triaged" |
@cpuck : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
1 similar comment
@cpuck : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
[NEW] SetSPN command line reference
Added Note to explain Microsoft Graph - Application.ReadWrite.All permissions. Customers are asking for more details as to why WAC requires this but PowerShell deployments do not. Feel free to follow up with cpuckett, arfong, and sushmad, if you need more details or clarification.