CIS Microsoft Azure Foundations Benchmark v1.4.0/Identity and Access Management/22 of 115
1.22Ensure a Custom Role is Assigned Permissions for Administering Resource Locks
Control family: Identity and Access Management
Control description
Resource locking is a powerful protection mechanism that can prevent inadvertent modification/deletion of resources within Azure subscriptions/Resource Groups and is a recommended NIST configuration.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Resource locks protect critical resources from being deleted or changed (8.5), but anyone with Owner or User Access Administrator can remove them. A custom role that can manage locks, and nothing else, lets you give lock management to a small group without handing out full ownership.
Before you start
The same on every cloud, before the steps in the tabs.
- Name the people or group who manage resource locks, separate from those who run the resources.
- Agree how a lock removal is requested and approved.
Evidence
- The lock administrators and the lock removal procedure
On Azure the tasks create a lock-management custom role in Access control (IAM), then assign it to the people who manage locks.
Task 1Create a custom role for managing locks
- Sign in to the Azure portal at portal.azure.com and open Subscriptions, then the subscription.
- Select Access control (IAM), then + Add > Add custom role.
- Name it Resource Lock Administrator and start from scratch.
- On Permissions, select Add permissions, search for Microsoft.Authorization, and select the read, write and delete actions for locks.
- On Assignable scopes, keep the subscription (or add the management group).
- Select Review + create, then Create.
- Check it: the Roles tab lists Resource Lock Administrator with only the lock actions.
Task 2Assign the role to the lock administrators
- In Access control (IAM), select + Add > Add role assignment.
- Choose Resource Lock Administrator and select Next.
- Select the lock administrators' group as Members and select Review + assign.
- Check it: a member can add and remove a lock but can't change the resource itself.
Evidence
- The Resource Lock Administrator custom role and its permissions
- The role assignments for that role
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.