We are excited to announce the preview release of the new Azure Consumption and Charge APIs for Enterprise customers. This follows the release of our new Power BI content pack that addressed issues related to performance and data size limitations. Users can now have the ability to query Azure Usage details and Marketplace Charges by any desired date range or billing period. These APIs enable organizations  to gain deep insights into their usage and spend for all workloads running on Azure. This is an important first step in our journey over the next few months to light up additional features to enable our customers to accurately monitor, predict, and optimize costs on Azure. Learn more by reading the detailed documentation on getting started with the APIs.

Details of the APIs:

• Balance and Summary: The Balance and Summary API offers a monthly summary of information on balances, new purchases, Azure Marketplace service charges, adjustments, and overage charges.

• Usage Details: The Usage Detail API offers a daily breakdown of consumed quantities and estimated charges by an enrollment. The result also includes information on instances, meters, and departments. The API can be queried by billing period or by a specified start and end date.

• Marketplace Store Charge: The Marketplace Store Charge API returns the usage-based marketplace charges breakdown by day for the specified billing period or start and end dates.

• Price Sheet: The Price Sheet API provides the applicable rate for each meter for the given enrollment and billing period.

• Billing Periods: The Billing Periods API returns a list of billing periods that have consumption data for the specified enrollment in reverse chronological order. Each period contains a property pointing to the API route for the four sets of data, BalanceSummary, UsageDetails, Marketplace Charges, and PriceSheet.

What’s next?

We are work on providing this data in ARM as part of a consistent channel agnostic API set. As always, please reach out to us on the Azure Feedback forum and through the Azure MSDN forum.