This is a powerful and useful script that must be used with caution!
The Remove-AzureBulkDeleteResource.ps1 script vastly accelerates removing large number of Azure resources in an unattended manner. Its primary use case is when a large ARM deployment template is being tested and many resources must be added/removed repeatedly. It can also be helpful to fully remove a single VM, which often is tedious. It's difficult and time consuming, and sometime completely impractical to remove resources by hand.
-
Before resources are removed, users are:
-
Prompted 3 times: 2 with mouse clicks to confirm selection, and once by typing to confirm that they really want to remove the resources
-
Shown a "- WhatIf" output of what will happen before it’s executed
-
-
Users are narrowed to resources within a singe Subscription and Resource Group
-
Resources are removed in an order that allows us to accommodate common dependencies that make this operation hard do manually. For example, you can't delete a VM’s disk & NIC, until the parent VM Resource has been removed.
-
The script relies heavily on PowerShell Out-GridView. Out-GridView has some powerful filtering capabilities that are very helpful.
-
Open Script in Admin ISE or VS Code i.e. do not run from PowerShell command line
-
Run the script
-
Starts a logon to Azure, if you are not logged in
-
Asks user to pick subscription
- Asks user to select Target Resource Group
- User filters/selects Target Resource for Removal
- Scripts presents the selection again for double verification
- A -WhatIf scenario is performed on the target resources
- Script prompts for a typed response to proceed with removed
- Items are removed based on a defined 'order of operations'
The script uses an array of Resource names to dictate the order resources are removed. We may need to add resources to this list as time passes to properly handle the order of operations on deletions.