This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 52%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Hi all,
I have an Azure Visual Studio Enterprise Subscription, but I cannot see any cost management data in the subscription.
In the Overview tab of the subscription, it says I am an "Account admin". According ot the IAM permission, I am an account owner of the subscription.
When I try to load Cost analysis, I get the following error, any ideas?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
You can submit a ticket here for support. https://visualstudio.microsoft.com/subscriptions/support/ https://support.microsoft.com/en-us/supportrequestform/7a3f017a-c951-7e06-1bd7-64bf7fc202ff?SL=en&SC=US
or chat online with them https://docs.microsoft.com/en-us/visualstudio/subscriptions/vs-concierge-chat
--please don't forget to close up the thread here by marking answer if the reply is helpful--
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 19%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPN%3C/text%3E%3C/svg%3E)
Same issue. Apparently its effecting a lot of users (including me). Waiting for an update from MS
Just checking if there's any progress or updates?
--please don't forget to close up the thread here by marking answer if the reply is helpful--
Hello Michael,
Just to add to Dave Patrick's response: This seems to be an issue with Azure customers right now. I'd recommend opening a ticket with Azure Billing Support:
https://azure.microsoft.com/en-ca/support/create-ticket
I too have been experiencing this with my Azure Subscriptions.
If this is helpful please accept answer.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 59%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Same problem with my subscription. I already lost several hours of work because cost monitoring is very important, not to MS....
I saw on Reddit /r/Azure that other people have the same issue. It looks multiple people can't view the billing dashboards.
Hi @Michael She ,
Yes, this is a known issue and team is working to resolve it. Will keep you informed as I hear an update.
Thanks, it looks like my billing dashboard in Canada East is now functional again!
Hi @Michael She ,
Yes, it is mitigated with a deployment change and issue is resolved for most of the customers across various regions.
Hi tbgangav-MSFT. Why didn't this appear as in issue under Azure Status? This is the first place people look for known Azure issues?
Hi @Michael She ,
Even this feedback on this incident not being captured at Azure Status is shared with the product team. It is acknowledged and being discussed upon. Will get back to you as I hear more information with this regard.
<<Sharing in answer section for better visibility and to benefit broader community members>>
The cost analysis access denied issue was caused due to a recent deployment problem. The incident has been mitigated by reverting the deployment and then the issue was resolved.