Cost Analysis in Microsoft Azure allows you to analyse the cost of your services; these services can be scoped into Resource Groups, Resources and Services; you can also group your services by Tags.
Azure tags are name-value pairs used to organize resources. You can apply tags for individual resources, display show back or ownership and can be used for automation - but what assigning parent/child relationships to your resources?
Tags work well for most used cases, but there may be times when you want to get a more in-depth view of the service and dependencies - this is where the “cm-resource-parent” tag comes in.
Introduced in Cost Analysis preview, Q3 of 2022, the ‘cm-resource-parent tag’ allows you to Group related resources together - to help give you a quick view of the solution’s total cost in a parent/child relationship. The ‘cm’ in the tag stands for: Cost Management.
To use the cm-resource-parent tag, you must choose a parent resource (an example may be an App Service or an Azure Virtual Desktop host pool). No changes will be made to this resource, but you need the ResourceID of the resource to apply to Child resources.
To find the ResourceID of the parent resource, you can use the Azure Portal, by
- Open the resource that you want to be the parent of.
- Select Properties in the resource menu.
- Find the Resource ID property and copy its value.
You can easily use PowerShell to find the ResourceID as well:
$ResourceName = 'Parent Resource' Get-AzResource -Name $ResourceName | Select-Object ResourceId
A resource ID looks like this (you will need to copy the full thing, this will be used on your child’s resources):
Once you have the Resource ID of your resource, it is time to tag your Child’s resources.
As an Azure Tag is a Key/Value pair - the tags will be similar to:
To apply the ResourceID of the parent resource, you can use the Azure Portal, by
- Open the resource you want to be the child of the parent you selected above.
- Click Tags
- Add in: cm-resource-parent in the value and the resource ID of your parent as a value.
Note: You cannot have a multi-hierarchy, i.e. a Parent, then Child and Child off that - it is purely a Parent and Child relationship at this stage. Also, the Resource ID will change if the Parent resources are moved to another Resource group or subscription.
These Tags can work easily with other cost management tags you may be using (but you cannot have more than one cm-resource-parent tag), so it doesn’t replace but supplements your visibility. They are supported on any resource that is Tag-capable.
You may have to wait up to a day (24 hours) before the changes are visible in Azure Cost Analysis.
I have the Azure Naming Tool deployed in my example and would like to see the overall cost; these resources are deployed across multiple resources in the same subscription.
Choosing my WebApp as my parent resource, I tagged all child resources (App Service Plan, Container Registry, Storage Account) with the relevant tag and resource ID as seen below:
After 24 hours, I then went to the Cost Analysis (Preview) and selected Resources and could view the current cost of my service after a few days of use.
And another example can be seen below - where I have added a Public IP as a child resource of the Azure storage account, which, although the parent in this relationship, is a child in the Azure Naming Tool.
As you can see, the ‘cm-resource-parent’ is another way to group related resources of different types from a cost analysis angle; still, in preview, this tag opens up the door for various other initiatives across observability, security stacks etc.
Although not tested, you also should be able to output the resource ID of your Bicep code and add that as a variable for any resources deployed via Infrastructure as Code.
It’s worth noting that this feature is still in Preview at the time of this article, so if you incur any bugs or have feature requests, you can use the ‘Rate the Cost Analysis Preview’ feature in the Azure Portal to supply feedback to the product teams.