Edit

Ingest cost details data

  • Article

Cost details (formerly referred to as usage details) are the most granular cost records that are available across Microsoft. Cost details records allow you to correlate Azure meter-based charges with the specific resources responsible for the charges so that you can properly reconcile your bill. The data also includes charges associated with New Commerce products like Microsoft 365 and Dynamics 365 that are invoiced along with Azure. Currently, only Partners can purchase New Commerce non-Azure products. To learn more, see Understand cost management data.

This document outlines the main solutions available to you as you work with cost details data. You might need to download your cost data to merge it with other datasets. Or you might need to integrate cost data into your own systems. There are different options available depending on the amount of data involved.

You must have Cost Management permissions at the appropriate scope to use APIs and tools in any case. For more information, see Assign access to data and Assign permissions to Cost Management APIs.

How to get cost details

You can get cost details programmatically with exports or the Cost Details report. To learn more about which solutions are best for your scenarios, see Choose a cost details solution.

For Azure portal download instructions, see How to get your Azure billing invoice and daily usage data. If you have a small cost details dataset that you maintain from one month to another, you can open your CSV file in Microsoft Excel or another spreadsheet application.

Cost details data format

The Azure billing system uses cost details records at the end of the month to generate your bill. Your bill is based on the net charges that were accrued, by meter. Cost records contain daily rated usage based on negotiated rates, purchases (for example, reservations, Marketplace fees), and refunds for the specified period. Fees don't include credits, taxes, or other charges or discounts.

The following table shows the charges that are included in your cost details dataset for each account type.

Account type Azure usage Marketplace usage Purchases Refunds
Enterprise Agreement (EA) ✔ ✔ ✔ ✘
Microsoft Customer Agreement (MCA) ✔ ✔ ✔ ✔
Pay-as-you-go (PAYG) ✔ ✔ ✘ ✘

A single Azure resource often has multiple meters emitting charges. For example, a VM might have both Compute and Networking related meters.

To understand the fields that are available in cost details records, see Understand cost details fields.

To learn more about Marketplace orders (also known as external services), see Understand your Azure external service charges.

A single resource might have multiple records per day

Azure resource providers emit usage and charges to the billing system and populate the Additional Info field of the usage records. Occasionally, resource providers might emit usage for a given day and stamp the records with different datacenters in the Additional Info field of the cost records. It can cause multiple records for a meter or resource to be present in your cost file for a single day. In that situation, you aren't overcharged. The multiple records represent the full cost of the meter for the resource on that day.

Pricing behavior in cost details

The cost details file exposes multiple price points. They're outlined as follows.

PAYGPrice: It's the market price, also referred to as retail or list price, for a given product or service.

  • In all consumption usage records, PayGPrice reflects the market price of the meter, regardless of the benefit plan such as reservations or savings plan.
  • Purchases and refunds have the market price for that transaction.

When you deal with benefit-related records, where the PricingModel is Reservations or SavingsPlan, PayGPrice reflects the market price of the meter.

UnitPrice: It's the price for a given product or service inclusive of any negotiated discount that you might have on top of the market price (PayG price column) for your contract.

  • In all consumption usage records, UnitPrice reflects the negotiated meter price that you have on your contract, regardless of the benefit plan such as reservations or savings plan.
  • Purchases and refunds have the negotiated price for that transaction.

EffectivePrice It's the price for a given product or service that represents the actual rate that you end up paying per unit. It's the price that should be used with the quantity to do price * quantity calculations to reconcile charges. The price considers the following scenarios:

  • Tiered pricing: For example: USD 10 for the first 100 units, USD 8 for the next 100 units.
  • Reservation/savings plan actual cost record: In the actual cost report, the effective price for a usage record is 0 because the resource, for example VM, is covered by prepaid commitment. The effective price for a purchase record shows the price of the purchase transaction.
  • Reservation/savings plan amortized cost record: In the amortized cost report, the effective price for a usage record is the prorated hourly price of the reservation/savings plan.

Quantity: It's the number of units used by the given product or service for a given day. It aligns to the unit of measure used in actual resource usage.

If you want to reconcile costs with your price sheet or invoice, note the following information about unit of measure.

Price Sheet unit of measure behavior - The prices shown on the price sheet are the prices that you receive from Azure. They're scaled to a specific unit of measure.

Cost details unit of measure behavior - The unit of measure associated with the usage quantities and pricing seen in cost details aligns with actual resource usage.

Example pricing scenarios seen in cost details for a resource

Here are some example scenarios that show how an actual cost report or amortized cost report might look like.

Sample actual cost report:

MeterId PricingModel ChargeType Quantity PAYGPrice UnitPrice EffectivePrice UnitOfMeasure Cost Notes
xxxxxxxx-xxxx- xxxx - xxxx -xxxxxxxxxxx OnDemand Usage 24 1 0.8 0.8 1 hour 19.2 Manual calculation of the actual charge: multiply 24 * 0.8 * 1 hour.
xxxxxxxx-xxxx- xxxx - xxxx -xxxxxxxxxxx Reservations/SavingsPlan Usage 24 1 0.8 0 1 hour 0 Manual calculation of the actual charge: multiply 24 * 0 * 1 hour.
xxxxxxxx-xxxx- xxxx - xxxx -xxxxxxxxxxx Reservations Purchase 15 120 120 120 1 hour 1800 Manual calculation of the actual charge: multiply 15 * 120 * 1 hour.

Sample amortized cost report:

MeterId PricingModel ChargeType Quantity PAYGPrice UnitPrice EffectivePrice UnitOfMeasure Cost Notes
xxxxxxxx-xxxx- xxxx - xxxx -xxxxxxxxxxx OnDemand Usage 24 1 0.8 0.8 1 hour 19.2 Manual calculation of the actual charge: multiply 24 * 0.8 * 1 hour.
xxxxxxxx-xxxx- xxxx - xxxx -xxxxxxxxxxx Reservations/SavingsPlan Usage 24 1 0.8 0.3 1 hour 7.2 Manual calculation of the actual charge: multiply 24 * 0.3 * 1 hour.

Note

  • Limitations on PayGPrice
    • For EA customers PayGPrice isn't populated when PricingModel = Reservations or Marketplace.
    • For MCA customers, PayGPrice isn't populated when PricingModel = Reservations or Marketplace.
  • Limitations on UnitPrice
    • For EA customers, UnitPrice isn't populated when PricingModel = MarketPlace. If the cost allocation rule is enabled, the UnitPrice will be 0 where PricingModel = Reservations. For more information, see Current limitations.
    • For MCA customers, UnitPrice isn't populated when PricingModel = Reservations.

Unexpected charges

If you have charges that you don't recognize, there are several things you can do to help understand why:

  • Review the invoice that has charges for the resource
  • Review your invoiced charges in Cost analysis
  • Find people responsible for the resource and engage with them
  • Analyze the audit logs
  • Analyze user permissions to the resource's parent scope
  • Create an Azure support request to help identify the charges

For more information, see Analyze unexpected charges.

Azure doesn't log most user actions. Instead, Azure logs resource usage for billing. If you notice a usage spike in the past and you didn't have logging enabled, Azure can't pinpoint the cause. Enable logging for the service that you want to view the increased usage for so that the appropriate technical team can assist you with the issue.

Next steps