Skip to main content

Vampires | How to clean you Azure Subscription

Playing and testing different scenarios and use cases in Azure can generate a lot of ‘garbage’ under your subscriptions.

Vampires
When I say garbage I’m referring to different resources that you create but forget to remove. Don't think at resources like Storage, Web Apps or Worker Roles, but many times when you remove things in odd order, you can end up with some resources that are allocated, but you don’t use anymore and you forget about them. For example the storage of a VM, or Traffic Manager that was used for a Web App.
I named 'vampires' this kind of resources. Why? They consume small amount of money every month. Even the value is not high, you can end up at the end of the month with $10 or $20 consumed on them. They are like electrical vampires that we have in our house – a TV that is in standby, a phone/tablet charger, audio system.

Best Practice
The best practice is very clear and simple. Remove all the time resources that you don’t use anymore. But, sometimes you are in hurry or you don’t have time to double check if you removed everything.
In this situations, you can use a simple rule that will help you to save time and avoid this kind of situations. Add all resources that you create under an Azure Subscription for a demo or for a specific test under the same Azure Resource Group.
A Resource Group is like a container where you can put together resources for the same solution. Don’t forget to give a meaningful name to the Resource Group. Otherwise, you will don’t know what was the purpose of it.
After you finish playing with a demo or with an Azure Solution, the only thing that you need to do is to remove the Resource Group. Removing the Resource Group will remove all the resources that were created under it.

Cleaning
But, what you do if you realize that after a few months playing with Azure, you have under your subscription a lot of resources that you forgot about or a lot of resource groups that are empty.
Well, deleting each of them would take a lot of time. It is a boring task and you don’t want to do this. The other solution is to run a power shell script that remove all the Resource Groups that you have under you Azure Subscription. Let’s call it CleanStartScript.

$selectedSubscription = Get-AzureSubscription -Current
Write-Host Subscription in use: $selectedSubscription.SubscriptionName

Write-Host Start Deleting all Resource Groups

$selectedResourceGroups = Get-AzureRmResourceGroup
foreach($currentResourceGroup in $selectedResourceGroups)
{
  Write-Host Deleting Resource Group: $currentResourceGroup.ResourceGroupName
    Remove-AzureRmResourceGroup -Name $currentResourceGroup.ResourceGroupName -Force -Verbose
  Write-Host Deleted Resource Group:  $currentResourceGroup.ResourceGroupName
}

Write-Host Ended Deleting all Resource Groups
The scrips can be found on GitHub: https://github.com/vunvulear/Stuff/tree/master/Azure/CleanAzureSubscription

Don't forget to select the right subscription before running this script. Do do this, you might find the following power shell scrips usefull:

  • Get-AzureSubscription -Current |> Get Current Subscription
  • Login-AzureRmAccount |> Login to Azure account
  • Get-AzureAccount |> Get A list of all Azure Subscription under the current account
  • Get-AzureSubscription -SubscriptionId XXX | Select-AzureRmSubscription |> Set the given subscription as the current one 

Comments

Popular posts from this blog

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

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(

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

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

Navigating Cloud Strategy after Azure Central US Region Outage

 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