Clarify scope of AllowedToUseSspr parameter#731
Clarify scope of AllowedToUseSspr parameter#731mcm223 wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Updates an example in Update-MgPolicyAuthorizationPolicy.md to clarify scope of the parameter.
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 47aa19e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@mcm223 - Thanks for your contribution. Since the content in this repo is autogenerated, I will make this update from the source to ensure that this update isn't overwritten in the next refresh. Thanks. I have made the update in this PR and the changes should reflect in the next docs refresh at the end of week. |
|
@msewaweru It looks like this doc still haven't been updated from your PR. Is there anything else pending? |
Updates an example in
Update-MgPolicyAuthorizationPolicy.mdto clarify scope of the parameterAllowedToUseSSPR. The previous example was flagged by a customer as misleading, as it suggested the parameter affected users instead of administrators. The parameter description does indicate it only affects administrators.Additionally, the example was modified to show the parameter being set to
false, as it is typically enabled by default.