{"id":16985,"date":"2020-08-19T12:42:17","date_gmt":"2020-08-19T12:42:17","guid":{"rendered":"https:\/\/www.testpreptraining.com\/tutorial\/?page_id=16985"},"modified":"2022-03-14T11:33:55","modified_gmt":"2022-03-14T11:33:55","slug":"creating-azure-resource-locks","status":"publish","type":"page","link":"https:\/\/www.testpreptraining.ai\/tutorial\/creating-azure-resource-locks\/","title":{"rendered":"Creating Azure Resource Locks"},"content":{"rendered":"\n

Go back to AZ-500 Tutorials<\/a><\/p>\n\n\n\n

In this tutorial, we will learn and understand about creating and managing Azure Resource locks.<\/p>\n\n\n\n

However, you may require to lock a subscription, resource group, or resource for preventing other users as an administrator. For this, you can set the lock level to CanNotDelete or ReadOnly. Here, CanNotDelete means authorized users can still read and modify a resource, but they can’t delete the resource. Whereas, ReadOnly means authorized users can read a resource, but they can’t delete or update the resource. Applying this lock is similar to restricting all authorized users to the permissions granted by the Reader role.<\/p>\n\n\n\n

Applying locks<\/strong><\/h4>\n\n\n\n

When you apply a lock to a parent scope, it applies to all resources within that scope. Furthermore, any resources you add subsequently will inherit the parent’s lock. Unlike role-based access control, you use management locks to apply a restriction to all users and roles.<\/p>\n\n\n\n

Resource Manager locks, on the other hand, only apply to activities that take place on the management plane, such as those submitted to https:\/\/management.azure.com. The locks prevent resources from performing their own tasks.<\/p>\n\n\n\n

Considerations before applying locks<\/strong><\/h6>\n\n\n\n

Locks can have unanticipated consequences since certain procedures that don’t appear to affect the resource nonetheless need actions that the lock prevents. The following are some instances of procedures that are hindered by locks:<\/p>\n\n\n\n