Not possible to connect to EA or MCA
ew-ewim opened this issue · 4 comments
Hey,
I am billing account owner and billing profile owner.
We have both an EA and MCA where we switched in Feb '23 from EA to MCA for Azure consumption.
I wrote my own basic reports in Power BI connecting to both the EA and MCA.
Currently we do not have any reservations
Trying to connect to your reports (version 3.1) however fails:
- With enrollment number for the EA I do get errors on both recommendation tables: "Bad Request" and no other queries are run
- With account nbr and profile ID for the MCA, all queries keep on spinning, without doing anything. Though it seems that thet are waiting for the query parameters table.
Any idea what might cause this? (I am in EU region)
The issues seem to originate from not using any reservations that result in non existing tables.
After removing the queries with non existing tables, the data is available and reports are shown ...
Hi @ew-ewim. Are you still experiencing the issue? There were issues in 3.0 with empty RI tables, however that should have been resolved with 3.1. Bad Request is something coming from the underlying consumption REST APIs, which I have seen before when the Billing Profile ID or Account ID is malformed, and on occasion there has been a "bug" in the API where it stopped working for a few days, and was timing out to read RI usage data.
Can you try to run Query Diagnostics for the RI steps and check which step/API is failing for the bad request?
Firstly thanks for creating and sharing this, and if I can get it working it will be brilliant.
I have the same issue as ew-ewim with the RI, or lack of, pic attached. Using 3.1.
Also is there any support for CSP?
@ahcargill - are you able to run the query diagnostics for the steps, to see what the underlying error is? Thinking out loud it could also be that you have no recommendations in Azure Advisor (do you run VMs?), are you able to hop into Azure Advisor and check there?
Only EA / MCA accounts are supported by the PowerBI connector for Azure Cost Management which the report uses, so I do not believe it will work with CSP.