# Azure resource locks: what it can block and where it stops

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Azure resource locks is a Azure mechanism. A lock on a subscription, resource group or resource blocks deletion (CanNotDelete) or modification and deletion (ReadOnly) of the locked scope. It applies to control plane operations on the locked scope and the resources under it.

A lock on a subscription, resource group or resource blocks deletion (CanNotDelete) or modification and deletion (ReadOnly) of the locked scope. Microsoft documents that the lock overrides any user permissions.

A lock on a subscription, resource group or resource blocks deletion (CanNotDelete) or modification and deletion (ReadOnly) of the locked scope, and Microsoft documents that the lock overrides any user permissions. It applies to control plane operations on the scope and the resources under it.

Limits: locks do not apply to data plane operations; a ReadOnly lock blocks operations that look like reads but use POST, such as starting a virtual machine; locks cannot be added to management groups; and users with Owner or User Access Administrator roles can create and delete locks. No dry run was found on 2026-11-10. 1 library entry uses resource locks.

## Documented limits

- Locks apply only to control plane operations, not data plane operations. ([source](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources))
- A ReadOnly lock blocks operations that look like reads but use POST, such as starting a virtual machine. ([source](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources))
- Locks cannot be added to management groups. ([source](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources))
- Users with Owner or User Access Administrator roles can create and delete locks. ([source](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources))

## Testing before enforcement

none found on 2026-11-10

## The 1 library entry written in it

- [Resource locks (CanNotDelete and ReadOnly)](/guardrails/azure-lock-cannotdelete-readonly/): Azure, Azure resource locks, organization integrity

**Where Act is behind.** Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

## Related pages

- [Management group assignment: how it works, its limits and how to test it](/mechanisms/management-groups/)
- [Organization Policy Service (managed and legacy constraints): how it works, its limits and how to test it](/mechanisms/org-policy/)
- [Custom organization policy constraints: how it works, its limits and how to test it](/mechanisms/custom-org-policy/)

## Sources

- Azure resource locks: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/mechanisms/resource-lock/
