Often, there is a need to secure your deployed environment so that there is no possibility to easily change them or even remove them by a mistake. As you cannot just rely on given conventions or communication between teams, you have to implement some kind of policy that will make resources read-only. In Azure, the way to achieve that is to leverage resource locks. In this section, we'll learn how to implement resource locks and secure our workloads against accidental changes.
There are two levels of locks in Azure:
- Subscription locks: These are applied to all the resources inside a subscription.
- Resource group locks: These are applied to all the resources inside a resource group (and the resource group itself).
Also, you can choose between two different kinds of those locks:
- Read-only: A lock that prevents you and others from introducing changes to the resources
- Delete: A lock that prevents you and others from deleting resources...
