Even with careful role-based access control (RBAC), a person with the right role can accidentally delete or change an important resource, for example by removing the wrong resource group while cleaning up test environments. Resource locks add a safety net: they prevent resources from being deleted or modified, regardless of the user's role, until the lock is removed. Locks are one of the governance features in Azure, alongside Azure Policy and tags, and they are especially valuable for production databases, networking resources and anything that would take a long time to rebuild.
Keep reading for free
Create a free StudyToCert account to read the rest of this lesson: 7 more sections, 6 key terms, a real-world example, an exam tip and self-check questions. Every lesson, lab and practice test is free with an account.