Skip to content

Conversation

@B-Oudehinken
Copy link
Contributor

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:

  • Updated the $expirationRule variable in both examples to use the fully qualified type name Microsoft.Azure.PowerShell.Cmdlets.Resources.Authorization.Models.Api20201001Preview.RoleManagementPolicyExpirationRule instead of the shorthand RoleManagementPolicyExpirationRule. [1] [2]
  • Updated the $notificationRule variable in Example 2 to use the fully qualified type name Microsoft.Azure.PowerShell.Cmdlets.Resources.Authorization.Models.Api20201001Preview.RoleManagementPolicyNotificationRule instead of the shorthand RoleManagementPolicyNotificationRule.

The current doc examples do not work.

This suggested configuration works.
Tested it my self. Credits to : 
 Azure/azure-powershell#18781 (comment)
@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@github-actions
Copy link

github-actions bot commented Sep 3, 2025

Expectations

Thanks 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:

  • It is not a draft PR.
  • It does not have a WIP prefix in the title.
  • It passes validation and build steps.
  • It does not have any merge conflicts.
  • You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

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-service-prod
Copy link
Contributor

Learn Build status updates of commit a22253e:

✅ Validation status: passed

File Status Preview URL Details
azps-14.4.0/Az.Resources/Update-AzRoleManagementPolicy.md ✅Succeeded View (azps-14.4.0)

For more details, please refer to the build report.

@mikefrobbins
Copy link
Contributor

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

Copy link
Contributor

@mikefrobbins mikefrobbins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mikefrobbins mikefrobbins merged commit aea23b7 into MicrosoftDocs:main Sep 3, 2025
2 checks passed
@B-Oudehinken B-Oudehinken deleted the patch-2 branch September 4, 2025 05:58
@B-Oudehinken
Copy link
Contributor Author

B-Oudehinken commented Sep 4, 2025

@mike

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

Thanks for comment!
I've created a pull request in the suggest repo
Azure/azure-powershell#28502

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants