Skip to main content

Preventing accidentally resource deletion - Lock Resource | Azure

By
A week ago, one of our team member modified a script that clean (removes) Azure resources, based on a naming convention. Because the number of our Azure Subscription is limited, the Development Team is sharing the same subscription between them and for DEV and TEST environment.
To be able to have a control on resources and trace the owner of them we have:
  • Naming conventions: A prefix that specify the owner of the resource or the environment

    • rvteststorage (rv - Radu Vunvulea)
    • dv (Dev Environment) 
    • tt (Test Environment)
    • ...
  • Azure Resource Groups that give us the possibility to group resources together.
 
As we can see in the above diagram, Azure Resource Groups can be used with success to group together different resources that have a logic for your application or from a business perspective. 

Coming back to the initial cleaning script, there was a small bug in the script, that didn't took into account the prefix of Azure Resource Groups and removed all the resources that were under that subscription. 

Now, the questions is what we can do to avoid  this kind of things in the future. Of course, multiple subscriptions would be great, but this will not happen. A review of the script from another team member would work also, but not all the time there will be time for things like this and bugs like this cannot be seen each time.

How nice it would be to have a flag on our resources, that would not allow anybody to remove (delete) the resources. This features exist on AWS for some time and wait.... we forgot that from last year we have a similar feature on Azure also. 
This feature is called "Resource Lock" and allows us to lock a resource for deletion. People will be able to modify it, but as long as this flag is set, nobody will be able to delete this resource. In this way we can avoid in the future situations like this.
This lock can be set not only when we create the resource, but also after it and can be used for any time of resource. The Lock can be set using Power Shell by specifying LockLevel flag to 'CanNotDelete' of using ARM.

Power Shell
$resourceGroup = 'devenv'
$storageAccountName = 'devlogstorage'

New-AzureResourceLock -LockLevel CanNotDelete '
-LockNotes 'Delete is not allowed for DEV env storage' `
-LockName 'DevEnvStorageLock' `
-ResourceName $storageAccountName `
-ResourceType 'Microsoft.Storage/storageAccounts' `
-ResourceGroup $resourceGroup -Verbose

More information about this feature can be found on Azure page: https://azure.microsoft.com/en-us/documentation/articles/resource-group-lock-resources/
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more