Show Virtual Machine name in detailed bill
Show each virtual machine from a Cloud Service as its own line within the detailed bill.
You can see the Virtual Machine name in the v2 detailed usage file available under your subscriptions billing history page.
Azure Billing Team
Nick Shaw commented
The VM name is obscured from billing deliberately, it stops users from being able to easily consolidate or minimise your azure costs.
Brandon Spilove commented
We need to understand the usage by each individual VM. On the bill it groups them all together if they are the same size and then it is impossible to see the individual usage. I was able to view the individual VM charges in the daily usage section, however this section only shows "overage" usage, not "all" usage. Since we have a monthly commitment amount, any charges covered by the commitment amount are simply not reported. This is unacceptable. If you are using my commitment amount towards daily usage, then I need to see what you are using it for without aggregating the totals. It makes me suspicious that you are not billing me correctly since you don't break it down and show me each individual resource that is getting billed.
Aidan Finn commented
The V2 bill that I get does not show VM names - it simply aggregates hours per spec. I have found myself repeatedly doing forensic accounting for customers to determine where credit disappeared to. The level of detail in the billing reports and auditing is completely insufficient - I can only say that more hours of this spec were spent on this day - but I have no idea when that machine was created, by who, or what it was called.
Sam Khanjar commented
I am logged in to our billing portal, downloaded the detailed usage file but I still can't see the VM name in there. What am I missing?
Hi, I think it gives usage of cloud service. In the instance id column it show value as "cloudservicelabel(deploymentlabel)". If my cloud service have multiple VMs say (VM1, VM2, VM3 in CloudService1) then in this case how can we know usage of individual VM.
Matt Allison commented
We currently do this for internal chargeback with over 8,000 on-premises VMs. We absolutely need the same in Azure - even if it's thousands of VMs.
I think reporting options that show a monthly per-VM cost rather than a daily/hourly cost would be acceptable for most of our use cases.
Dan Ulrich commented
I agree. Virtual Machine names for tracking are essential, seems odd we've not had this included so far.
Know bandwidth to each virtual machine on the bill