Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Consumption Insights connector: No cost data retrieved #913

Closed
A141135 opened this issue Mar 24, 2019 — with docs.microsoft.com · 9 comments

Comments

Projects
None yet
10 participants
Copy link

commented Mar 24, 2019 — with docs.microsoft.com

I've been using this connector for some time and it's generally great.

However as of 22-March, all cost data in the Detail Charges and PriceSheets tables is showing as $0.

Can this please be fixed?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

This comment has been minimized.

Copy link

commented Mar 25, 2019 — with docs.microsoft.com

I too have been using the connector for a while without issue - until last week. Now when I refresh the Detail Charges data going back to July 2018 (when our enrollment started) some months show the costs whilst others report £0.

@MPEV

This comment has been minimized.

Copy link

commented Mar 25, 2019

I have the same with zero cost (if only) since the beginning of March.

@tom-ditlev

This comment has been minimized.

Copy link

commented Mar 25, 2019

I have the exact same problem. Saw it first on 19-March. Doing two or three on demand refreshes "fixed" it but now it broke again. I have done one on demand refresh, but that did not help. I have several different datasets against Azure Consumption Insights and they are all broken.

Wondering if this is the right place to report this issue...?

This comment has been minimized.

Copy link

commented Mar 25, 2019 — with docs.microsoft.com

similar issues here. Is there a known cause or workaround? Also the consumption insights app you download from marketplace has the same issues, not indicative of all months, it appears to be select months that costs are @0. 201810, 201812, 201901, 201903 Costs are still populated for other months.

@pbeckman01

This comment has been minimized.

Copy link

commented Mar 25, 2019

I have the same problem but I'm missing a different set of months. In my case all data after November 2018 is missing.

This is a serious issue for us as we track all Azure spend using PowerBI reports. The monthly and quarterly reports for the exec team are all based on Azure Consumption Insights.

@sonalimanohar

This comment has been minimized.

Copy link

commented Mar 25, 2019

Someone just mentioned to me that we now have to use a new connector called "Azure Cost Management" instead of Azure Consumption Insights. Is that true? I do not find references of this anywhere except this article that mentions that this connector is coming up: https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-march-2019-feature-summary/. Has anyone verified this?
Note that I do not even see the new connector "Azure Cost Management" in my list.

@A141135 A141135 changed the title No cost data retrieved Azure Consumption Insights connector: No cost data retrieved Mar 25, 2019

@mgblythe

This comment has been minimized.

Copy link
Contributor

commented Mar 27, 2019

Thanks for opening this, @A141135 and for the followup feedback everyone. I'll keep this open b/c this might have a doc component, but you might find a solution in the Power BI Community, at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.

This comment has been minimized.

Copy link

commented Mar 28, 2019 — with docs.microsoft.com

Hello all, I submitted a Support request and communicated with the Azure Cost Management team last Friday and this zeroes issue was resolved on Monday. It was impacting the EA portal, ACI PBI connector and ACI PBI content pack.

@A141135

This comment has been minimized.

Copy link
Author

commented Mar 28, 2019

Also submitted a support case and had confirmation this was resolved on Tuesday. The data has been looking good for us since then. Thanks!

@A141135 A141135 closed this Mar 28, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.