Microsoft Cost Details API now generally available for EA and MCA customers #Azure - The Entrepreneurial Way with A.I.


Monday, July 25, 2022

Microsoft Cost Details API now generally available for EA and MCA customers #Azure


The Cost Details API is now generally available for use by Enterprise Agreement (EA) and Microsoft Customer Agreement (MCA) customers. This API provides on-demand download of the granular cost details (formerly referred to as usage details) associated with your Microsoft charges. The API replaces all existing Usage Details APIs and provides data for charges in your invoice. For customers with an MCA agreement this includes Microsoft 365, Dynamics 365, Power Platform, and Azure charges. This API is the go-to solution, along with Exports, for ingesting the raw cost data needed to build any custom reporting solution. To learn more about how to call the Cost Details API, please see our documentation on how to get small cost datasets on demand.

Customers that are not using Exports or the Cost Details API should migrate to one of these solutions moving forward. To learn more about which solution is best for your scenario, see our picking a cost details solution best practices.

Benefits of the new solutions

Both the Cost Details API and Exports provide extensive benefits on top of existing solutions today.

  • Security and stability—New solutions require Service Principal and/or user tokens in order to access data. For EA customers, keys used in the EA Reporting APIs are valid for six months. Going forward it is recommended to use token-based solutions through Service Principal or User authentication, consistent with Azure REST APIs.
  • ScalabilityThe EA Reporting APIs (available only for EA customers) and the Consumption Usage Details (available for both EA and MCA customers) aren't built to scale well as your Microsoft and Azure costs increase. The number of Azure cost records in your cost details dataset can get exceedingly large as you deploy more resources into the cloud. The new solutions are asynchronous and have extensive infrastructure enhancements behind them to ensure successful downloads for any size dataset.
  • Single dataset for all usage details—For EA customers, the existing EA Reporting APIs have separate endpoints for Azure usage charges versus Azure Marketplace charges. These datasets have been merged in the new solutions. A single dataset reduces the number of APIs that you need to call to see all your charges.
  • Purchase amortization—Customers who purchase Reservations can see an amortized view of their costs using the new solutions. You can request for amortized or actual cost datasets as part of report configuration. Learn more about using amortized cost details datasets.
  • Schema consistency—The Cost Details API and Exports provide files with matching fields. This allows you to easily move between solutions based on your scenario. Learn more about the fields available and understand cost details data fields.
  • Cost allocation integration—EA and MCA customers can use the new solutions to view charges in relation to the cost allocation rules that have been configured. Learn more about creating and managing Azure cost allocation rules.
  • Go forward improvements—The new solutions are being actively developed moving forward. They'll receive all new features as they're released.

Migrating to the new solutions

The EA Reporting APIs and the Consumption Usage Details API are no longer actively being developed. We strongly recommend migrating off these APIs as soon as possible. A retirement announcement will be made in the future with formal timelines for when the APIs will be turned off. However, the APIs will be fully supported from a reliability standpoint until the formal retirement date is reached.

When assessing the migration off existing usage details solutions, please use the documents below as a reference point:

Please note that pay-as-you-go, MSDN, and Visual Studio customers who are not a part of either an Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA) should continue using the Consumption Usage Details API.

Next steps

Follow us on Twitter @AzureCostMgmt for more exciting Cost Management updates.


Adam Wise, Khareem Sudlow