Skip to content

Clarify permissions needed for changing RBAC model#143

Closed
FabianGonzalez-MS wants to merge 1 commit into
MicrosoftDocs:mainfrom
FabianGonzalez-MS:patch-2
Closed

Clarify permissions needed for changing RBAC model#143
FabianGonzalez-MS wants to merge 1 commit into
MicrosoftDocs:mainfrom
FabianGonzalez-MS:patch-2

Conversation

@FabianGonzalez-MS

Copy link
Copy Markdown

Added requirement for 'Microsoft.KeyVault/vaults/write' permission when using User Access Administrator role.

Added requirement for 'Microsoft.KeyVault/vaults/write' permission when using User Access Administrator role.
@prmerger-automator

Copy link
Copy Markdown
Contributor

@FabianGonzalez-MS : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@v-regandowner

Copy link
Copy Markdown
Contributor

@msmbaldwin

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


> [!NOTE]
> Changing the permission model requires unrestricted 'Microsoft.Authorization/roleAssignments/write' permission, which is part of the [Owner](/azure/role-based-access-control/built-in-roles#owner) and [User Access Administrator](/azure/role-based-access-control/built-in-roles#user-access-administrator) roles. Classic subscription administrator roles like 'Service Administrator' and 'Co-Administrator', or restricted 'Key Vault Data Access Administrator' cannot be used to change permission model.
> Changing the permission model requires unrestricted 'Microsoft.Authorization/roleAssignments/write' permission, which is part of the [Owner](/azure/role-based-access-control/built-in-roles#owner) and [User Access Administrator](/azure/role-based-access-control/built-in-roles#user-access-administrator) roles. If using the latter, you will also need 'Microsoft.KeyVault/vaults/write' permission, which is part of [Key Vault Contributor](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/security#key-vault-contributor) role.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
> Changing the permission model requires unrestricted 'Microsoft.Authorization/roleAssignments/write' permission, which is part of the [Owner](/azure/role-based-access-control/built-in-roles#owner) and [User Access Administrator](/azure/role-based-access-control/built-in-roles#user-access-administrator) roles. If using the latter, you will also need 'Microsoft.KeyVault/vaults/write' permission, which is part of [Key Vault Contributor](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/security#key-vault-contributor) role.
> Changing the permission model requires unrestricted 'Microsoft.Authorization/roleAssignments/write' permission, which is part of the [Owner](/azure/role-based-access-control/built-in-roles#owner) and [User Access Administrator](/azure/role-based-access-control/built-in-roles#user-access-administrator) roles. If using the latter, you will also need 'Microsoft.KeyVault/vaults/write' permission, which is part of [Key Vault Contributor](/azure/role-based-access-control/built-in-roles/security#key-vault-contributor) role.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit dae9af2:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/key-vault/general/rbac-guide.md ⚠️Warning Details

articles/key-vault/general/rbac-guide.md

  • Line 116, Column 416: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/security#key-vault-contributor' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 116, Column 416: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/security#key-vault-contributor' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build 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.

@msmbaldwin msmbaldwin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for the clarification — the technical content is correct, but a couple of markdown issues to fix before this can merge:

  1. Broken NOTE blockquote — the new sentence beginning "Classic subscription administrator roles..." is missing its leading > , so it renders outside the > [!NOTE] block. Add > to that line.

  2. Link path — the Key Vault Contributor link uses a bare https://learn.microsoft.com/en-us/... URL. Use a relative path to match the other two links in the same note:
    [Key Vault Contributor](/azure/role-based-access-control/built-in-roles/security#key-vault-contributor)

Once these are addressed, add a comment containing #sign-off (without the backticks) to submit for publication.

@msmbaldwin

Copy link
Copy Markdown
Contributor

learn-build-service-prod Bot pushed a commit that referenced this pull request Jun 16, 2026
Incorporates contribution from #143 by
@FabianGonzalez-MS, with the reviewer suggestion from @v-regandowner applied
(relative link, single blockquote).

- Note that the User Access Administrator role also needs
  'Microsoft.KeyVault/vaults/write' (part of Key Vault Contributor) to
  change the permission model.

Files modified:
- articles/key-vault/general/rbac-guide.md

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants