Azure-docs: PriceSheet API call for EA errors with "Report type and report view are not compatible"

[vinnielima]

Is there any additional filters/parameters which can be passed to the "https://consumption.azure.com/v2/enrollments/<ea id>/pricesheet" API to specify as such? receiving this error:

{"error":{"code":"401","message":"Report type and report view are not compatible. Report Type: PriceSheet, Report View: AccountOwner"}}

---

Document Details

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

• ID: 6ed7b604-d89f-1d59-87d6-d32e29eb6245
• Version Independent ID: 0113a6ce-3f69-73ce-b063-c07b52348f92
• Content: Azure Billing Enterprise APIs
• Content Source: articles/billing/billing-enterprise-api.md
• Service: billing
• GitHub Login: @mumami
• Microsoft Alias: erikre

[SadiqhAhmed-MSFT]

@vinnielima Thanks for the question! We will investigate this issue and get back to you soon.

@mumami Would you've any insights on this?

[mumami]

Thanks for reaching out.
Account Owners are not authorized to view Pricesheets and Balances. You need to reach out to your Enrollment Admin.

[vinnielima]

@mumami what privilege is required to view Pricesheets and Balances? Any detail would be helpful so we can make the right request to the Enrollment Admin.

[SadiqhAhmed-MSFT]

@mumami Any comments?

[quinten-miller]

We are getting a similar error when interacting with some of the Enterprise Consumption API's.

This is a new problem to us, in that with over 100+ different Azure enrolment integrations we have not seen this.

In this particular case, the API key used from the EA portal cannot access the following API's

• Balance Summaries V2 & V3
• Price Sheet V2 & V3
• Reserved Instances V2 & V3

The billing API key can however access the Usage and Marketplace API's.

In each case, a 401 is returned with the following structure:
Report type and report view are not compatible. Report Type: _Summary_, Report View: _AccountOwner_

Each return is for the Account Owner, and the report type changes.

We are using the Billing API Key from within the EA portal. Not sure how it is being _confused_ for the Account Owner. This kind of feels like an issue with the API key or permissions associated. If I put in the wrong key I get a different 401, so I know the API key is correct.

@mumami or @SadiqhAhmed-MSFT - any insights into this?

[ms-premp]

@quinten-miller it looks like the key being used here is having only account level access.
All the three APIs, you mentioned, need Enrollment level access.
Please use a different API_Key, which has Enrollment level access. This can be generated from EA portal using an Enterprise Admin login. The login account permissions are used to generate the access permissions for API_Key.
Hope that helps.

[quinten-miller]

Thanks @ms-premp - we were not even aware that Account Owners were able to create Billing API keys and that they had less privlidges.
The account owner turned out to be the Admin as well, however he had an MSA the same as his Work 0365, once sorted all fixed :)

[quinten-miller]

@vinnielima as you might gather from above comments, Account Admins can create API Billing keys, yet those keys don't have access to the full suite of Billing and Management API's. You will need an EA Admin to log in and create the keys.

The easy way to know if you are logged in as an Admin you would see Enrollment under the manage options, and under that you will see a list of Admins. The Account owner doesnt get to see the Enrollment Details, they see Account.

[vinnielima]

@quinten-miller Thank you, as well as @ms-premp for the guidance. The issue here is due to access as an EA Admin in the scenario of a reseller to an Entity, and inside that entity there are multiple other Microsoft Tier 1/Tier 2 CSPs. Usually only the reseller has EA Admin rights.

Thank you again.

[srpomeroy]

Experiencing the same problem. Is there documentation around which roles are required to access the EA billing APIs?
This page(https://docs.microsoft.com/en-us/azure/billing/billing-understand-ea-roles) does a good job explaining what is accessible by what role, but it would be nice to have a simple breakdown of what permissions are required to access each api.

[bandersmsft]

@vinnielima I apologize this old issue wasn’t resolved. In an effort to refocus resources on current issues, I’m closing this one. If you feel that the issue wasn’t adequately addressed and you still need assistance, please feel free to reactivate.

please-close