While deleting a virtual system in Azure, not all the associated resources are deleted with it. Webmasters can easily identify un-associated Azure resources using Powershell.

As a part of our Server Management Services, we help our Customers to fix Azure related requests regularly.

Let us today discuss the steps to identify un-associated Azure resources using Powershell.

How to identify unassociated Azure resources using PowerShell?

After the deletion of a virtual system in Azure, it does not remove all the associated resources with it. Let us see how to identify unassociated resources left behind after deletions in Azure.

The initial step in identifying the unassociated Azure resources through PowerShell is to install the Azure PowerShell modules. A detailed writeup on the same is available here.

Identify and remove Unassociated Azure Resources

Now let us discuss the steps to identify the unassociated resource. First, we need to log on to the subscription using:

Login-AzAccountCopy Code

Once logged in, we can now use PowerShell to manage things in Azure Cloud.

Network Interfaces

At times, network interfaces do not get deleted along with their VMs. Finding unassociated Azure resources Azure portal can be a bit tricky.

However, we could get this result easily with the command below:

Get-AZNetworkInterfaceCopy Code

This command will output a large volume of data. Thus, to narrow it down, use the format below:

Get-AzNetworkInterface | Select-Object name, virtualmachineCopy Code

From the output, we can understand which Network Interface resources are not associated with a virtual machine. Finally, to remove those excess resources, run the command given below:

Get-AzNetworkInterface | Where-Object { $_.virtualmachine -eq $null } | Remove-AzNetworkInterfaceCopy Code

Disk

Similarly, we can get a list of the unallocated disk with the Get-AzDisk command below.

Get-AzDisk | Select-Object name,managedbyCopy Code

For instance, a sample output would look like:

Here, the “empty field for ManagedBy” indicates an unallocated disk. Further, we can remove the leftover disks from the previous system builds with the command below:

Get-AzDisk | Where-Object { $_.ManagedBy -eq $null } | Remove-AzDiskCopy Code

Network Security Groups

Similarly, to find unallocated resources for Network Security Groups, use the format below:

Get-AZNetworkSecurityGroup | Where-Object { $_.NetworkInterfaces.count -eq 0 } | Select-Object nameCopy Code

[Need any further assistance to identify azure resources using PowerShell? – We’re available 24*7]

Conclusion

In short, we can easily identify un-associated Azure resources using Powershell. Today, we saw how our Support Engineers perform this task.