Forum Discussion

jagutierrezm's avatar
jagutierrezm
Frequent Visitor
2 years ago

connect to azure cost management

From power bi, I have used the "Azure cost management" connector, I use an account of type "Microsoft Customer Agreements" and I have the "Cost Management Reader" role.
I use the following string to connect "/providers/Microsoft.Billing/billingAccounts/{billingAccountId}"
Tables like "Usage details" come empty and all "RI" tables generate an error:
"DataSource.Error: Web.Contents could not get the content of 'https://management.azure.com/providers/Microsoft.Billing/billingAccounts/{billingAccountId}/providers/Microsoft.CostManagement/generateReservationDetailsReport?api-version=2019 -11-01&startDate=2024-06-01&endDate=2024-07-17' (400): Bad Request.
Details:
DataSourceKind=AzureCostManagement
DataSourcePath=Enrollment Number;{billingAccountId}
DataSourceKind.2=Web
DataSourcePath.2=https://management.azure.com/providers/Microsoft.Billing/billingAccounts/{billingAccountId}/providers/Microsoft.CostManagement/generateReservationDetailsReport
Url=https://management.azure.com/providers/Microsoft.Billing/billingAccounts/{billingAccountId}/providers/Microsoft.CostManagement/generateReservationDetailsReport?api-version=2019-11-01&startDate=2024-06-01&endDate=2024- 07-17"

What can I do to access the tables?

Need Help
Show and Tell
Tips and Tricks
Tutorial Requests

1 Reply

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi jagutierrezm 

     

    The error message you're seeing suggests there's a problem with the URL being used to access the data. The "400: Bad Request" error often means there's something wrong with the request itself. Here's how to troubleshoot:

    Make sure that `{billingAccountId}` in the URL is replaced with your actual billing account ID.

    Check that the dates in the URL are correct and formatted properly (YYYY-MM-DD).

    Ensure that the URL is correctly structured for the API call. It might be missing some parts or have some syntax errors.

    Verify that your role of "Cost Management Reader" has the necessary permissions to access the RI (Reserved Instance) tables.

     

     

     

     

     

    Best Regards,

    Jayleny

     

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.