-
Notifications
You must be signed in to change notification settings - Fork 402
Update Update-AzRoleManagementPolicy.md #3718
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
Conversation
The current doc examples do not work. This suggested configuration works. Tested it my self. Credits to : Azure/azure-powershell#18781 (comment)
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 |
ExpectationsThanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it. To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details. The docs team begins to review your PR if you request them to or if your PR meets these conditions:
You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge. While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST). |
|
Learn Build status updates of commit a22253e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@B-Oudehinken, Thank you for the contribution. Please note that this doc is autogenerated reference content, and any changes made here won’t persist in future versions of the Az PowerShell module. The source for this content is maintained in the azure-powershell repository. |
mikefrobbins
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks for comment! |
The current doc examples do not work.
This suggested configuration works.
Tested it my self. Credits to :
Azure/azure-powershell#18781 (comment)
This pull request updates the usage of role management policy rule types in the documentation for
Update-AzRoleManagementPolicy. The main change is to use fully qualified type names in the PowerShell examples to avoid ambiguity and ensure correct type resolution.Documentation improvements:
$expirationRulevariable in both examples to use the fully qualified type nameMicrosoft.Azure.PowerShell.Cmdlets.Resources.Authorization.Models.Api20201001Preview.RoleManagementPolicyExpirationRuleinstead of the shorthandRoleManagementPolicyExpirationRule. [1] [2]$notificationRulevariable in Example 2 to use the fully qualified type nameMicrosoft.Azure.PowerShell.Cmdlets.Resources.Authorization.Models.Api20201001Preview.RoleManagementPolicyNotificationRuleinstead of the shorthandRoleManagementPolicyNotificationRule.