Azure Sentinel: Enterprise Governance (Part 3 of 3)
To read part 1 of 3 please click here To read part 2 of 3 please click here Resource Locks There is always a need to lock a subscription, resource group or resource to prevent other users in your organization from accidentally deleting or modifying critical resources. The lock level can be easily set to CanNotDelete or ReadOnly. In the portal, the locks are called Delete and Read-only respectively. CanNotDelete means authorized users can still read and modify a resource, but they can't delete the resource. ReadOnly means authorized users can read a resource, but they can't delete or update the resource. This lock restricts all authorized users to the permissions granted by the Reader role. Not every Azure user should have permission to create or remove locks. This requires access to the RBAC permissions like Microsoft.Authorization/, Microsoft.Authorization/locks/ action. However these actions can be added to custom roles as and when required. Azure Blueprint Azure Bluep