Add "Locks Contributor" Built-in Role to Security #125455
Conversation
|
Learn Build status updates of commit cbf7ae8:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/role-based-access-control/built-in-roles/security.md | Details | ||
| articles/role-based-access-control/built-in-roles.md | ✅Succeeded |
articles/role-based-access-control/built-in-roles/security.md
- Line 1575, Column 1: [Warning: code-block-unclosed - See documentation]
Unclosed code block. Code blocks must begin and end with triple backticks (```).
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.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
|
@microsoft-github-policy-service agree |
|
@Iam-Manishkumar : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Iam-Manishkumar
force-pushed
the
Iam-Manishkumar/azure-docs
branch
from
cbf7ae8 to
f1785a6
Compare
|
Suggested changes have been made, and the PR has been updated |
|
Learn Build status updates of commit f1785a6: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @rolyon |
|
Learn Build status updates of commit f1785a6: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
This PR introduces the addition of the "Locks Contributor" built-in role within Security. The role allows users to manage Azure resource locks, providing them with the necessary permissions to perform lock-related operations on resources.
This PR updates the built-in-roles.md and security.md documentation to reflect the addition of the "Locks Contributor" built-in role and its associated permissions.
Key Additions:
Microsoft.Authorization/locks/read): Allows users to view the properties of locks on resources.Microsoft.Authorization/locks/write): Enables users to create or modify locks on resources.Microsoft.Authorization/locks/delete): Grants the ability to remove locks from resources.Purpose:
The "Locks Contributor" role is for users who need to manage resource locks without giving them full control over the resources themselves. This ensures a more granular level of access.