You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cost-management-billing/automate/automation-ingest-usage-details-overview.md
+45-21Lines changed: 45 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
title: Ingest cost details data
3
3
titleSuffix: Microsoft Cost Management
4
-
description: This article explains how to use cost details records to correlate meter-based charges with the specific resources responsible for the charges so that you can properly reconcile your bill.
4
+
description: This article explains how to use cost details records to correlate meter-based charges with the specific resources responsible for the charges. Then you can properly reconcile your bill.
5
5
author: bandersmsft
6
6
ms.author: banders
7
-
ms.date: 11/17/2023
7
+
ms.date: 12/11/2023
8
8
ms.topic: conceptual
9
9
ms.service: cost-management-billing
10
10
ms.subservice: cost-management
@@ -13,21 +13,21 @@ ms.reviewer: jojoh
13
13
14
14
# Ingest cost details data
15
15
16
-
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](../costs/understand-cost-mgt-data.md).
16
+
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](../costs/understand-cost-mgt-data.md).
17
17
18
18
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.
19
19
20
20
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](../costs/assign-access-acm-data.md) and [Assign permissions to Cost Management APIs](cost-management-api-permissions.md).
21
21
22
22
## How to get cost details
23
23
24
-
You can use [exports](../costs/tutorial-export-acm-data.md) or the [Cost Details](/rest/api/cost-management/generate-cost-details-report) report to get cost details programmatically. To learn more about which solutions are best for your scenarios, see [Choose a cost details solution](usage-details-best-practices.md).
24
+
You can get cost details programmatically with [exports](../costs/tutorial-export-acm-data.md) or the [Cost Details](/rest/api/cost-management/generate-cost-details-report) report. To learn more about which solutions are best for your scenarios, see [Choose a cost details solution](usage-details-best-practices.md).
25
25
26
26
For Azure portal download instructions, see [How to get your Azure billing invoice and daily usage data](../manage/download-azure-invoice-daily-usage-date.md). 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.
27
27
28
28
## Cost details data format
29
29
30
-
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.
30
+
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.
31
31
32
32
The following table shows the charges that are included in your cost details dataset for each account type.
33
33
@@ -37,7 +37,7 @@ The following table shows the charges that are included in your cost details dat
A single Azure resource often has multiple meters emitting charges. For example, a VM may have both Compute and Networking related meters.
40
+
A single Azure resource often has multiple meters emitting charges. For example, a VM might have both Compute and Networking related meters.
41
41
42
42
To understand the fields that are available in cost details records, see [Understand cost details fields](understand-usage-details-fields.md).
43
43
@@ -49,33 +49,57 @@ Azure resource providers emit usage and charges to the billing system and popula
49
49
50
50
### Pricing behavior in cost details
51
51
52
-
The cost details file exposes multiple price points today. These are outlined below.
52
+
The cost details file exposes multiple price points. They're outlined as follows.
53
53
54
-
-**PAYGPrice:** It's the list price or on demand price for a given product or service.
55
-
- PAYGPrice is populated only for first party Azure usage charges where `PricingModel` is `OnDemand`. So for EA customers, `PAYGprice` isn't populated when `PricingModel` = `Reservations`, `Spot`, `Marketplace`, or `SavingsPlan`.
56
-
- PAYGPrice is the price customers pay if the VM was consumed as a Standard VM, instead of a Spot VM.
54
+
**PAYGPrice:** It's the market price, also referred to as retail or list price, for a given product or service.
55
+
- In all consumption usage records, `UnitPrice` reflects the market price of the meter, regardless of the benefit plan such as reservations or savings plan.
56
+
- Purchases and refunds have the market price for that transaction.
57
57
58
-
-**UnitPrice:** It's the price for a given product or service inclusive of any negotiated discounts on top of the pay-as-you-go price.
58
+
When you deal with benefit-related records, where the `PricingModel` is `Reservations` or `SavingsPlan`, *PayGPrice* reflects the market price of the meter.
59
59
60
-
-**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 takes into account the following scenarios:
61
-
-*Tiered pricing:* For example: $10 for the first 100 units, $8 for the next 100 units.
62
-
-*Included quantity:* For example: The first 100 units are free and then $10 for each unit.
63
-
-*Reservations:* For example, a VM that got a reservation benefit on a given day. In amortized data for reservations, the effective price is the prorated hourly reservation cost. The cost is the total cost of reservation usage by the resource on that day.
64
-
-*Rounding that occurs during calculation:* Rounding takes into account the consumed quantity, tiered/included quantity pricing, and the scaled unit price.
60
+
**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.
61
+
- 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.
62
+
- Purchases and refunds have the negotiated price for that transaction.
65
63
66
-
-**Quantity:** This is the number of units used by the given product or service for a given day and is aligned to the unit of measure used in actual resource usage.
64
+
**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:
65
+
- Tiered pricing: For example: USD 10 for the first 100 units, USD 8 for the next 100 units.
66
+
- 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.
67
+
- 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.
68
+
69
+
**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.
67
70
68
71
If you want to reconcile costs with your price sheet or invoice, note the following information about unit of measure.
69
72
70
-
**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.
73
+
**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.
71
74
72
75
**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.
73
76
74
77
#### Example pricing scenarios seen in cost details for a resource
Copy file name to clipboardExpand all lines: articles/cost-management-billing/automate/understand-usage-details-fields.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ MPA accounts have all MCA terms, in addition to the MPA terms, as described in t
56
56
| CustomerName | MPA | Name of the Microsoft Entra tenant for the customer's subscription. |
57
57
| CustomerTenantId | MPA | Identifier of the Microsoft Entra tenant of the customer's subscription. |
58
58
| Date¹ | All | The usage or purchase date of the charge. |
59
-
| EffectivePrice² | All |Blended unit price for the period. Blended prices average out any fluctuations in the unit price, like graduated tiering, which lowers the price as quantity increases over time. |
59
+
| EffectivePrice² ³ | All |The price for a given product or service that represents the actual rate that you end up paying per unit. |
60
60
| ExchangeRateDate | MCA | Date the exchange rate was established. |
61
61
| ExchangeRatePricingToBilling | MCA | Exchange rate used to convert the cost in the pricing currency to the billing currency. |
62
62
| Frequency | All | Indicates whether a charge is expected to repeat. Charges can either happen once (**OneTime**), repeat on a monthly or yearly basis (**Recurring**), or be based on usage (**UsageBased**). |
@@ -72,8 +72,8 @@ MPA accounts have all MCA terms, in addition to the MPA terms, as described in t
72
72
| MeterRegion | All | Name of the datacenter location for services priced based on location. See Location. |
73
73
| MeterSubCategory | All | Name of the meter subclassification category. Purchases and Marketplace usage might be shown as blank or `unassigned`.|
74
74
| OfferId¹ | All | Name of the offer purchased. |
75
-
| pay-as-you-goPrice² | All |Retail pricefor the resource. |
76
-
| PartnerEarnedCreditApplied | MPA | Indicates whether the partner earned credit has been applied. |
75
+
| pay-as-you-goPrice² ³| All |The market price, also referred to as retail or list price, for a given product or service. |
76
+
| PartnerEarnedCreditApplied | MPA | Indicates whether the partner earned credit was applied. |
77
77
| PartnerEarnedCreditRate | MPA | Rate of discount applied if there's a partner earned credit (PEC), based on partner admin link access. |
78
78
| PartnerName | MPA | Name of the partner Microsoft Entra tenant. |
79
79
| PartnerTenantId | MPA | Identifier for the partner's Microsoft Entra tenant. |
@@ -90,7 +90,7 @@ MPA accounts have all MCA terms, in addition to the MPA terms, as described in t
90
90
| PublisherId | MCA | The ID of the publisher. It's only available after the invoice is generated. |
91
91
| PublisherName | All | Publisher for Marketplace services. |
92
92
| PublisherType | All | Supported values: **Microsoft**, **Azure**, **AWS**, **Marketplace**. Values are `Microsoft` for MCA accounts and `Azure` for EA and pay-as-you-go accounts. |
93
-
| Quantity | All | The number of units purchased or consumed. |
93
+
| Quantity³| All | The number of units used by the given product or service for a given day. |
94
94
| ResellerName | MPA | The name of the reseller associated with the subscription. |
95
95
| ResellerMpnId | MPA | ID for the reseller associated with the subscription. |
96
96
| ReservationId¹ | EA, MCA | Unique identifier for the purchased reservation instance. |
@@ -111,12 +111,14 @@ MPA accounts have all MCA terms, in addition to the MPA terms, as described in t
111
111
| Tags¹ | All | Tags assigned to the resource. Doesn't include resource group tags. Can be used to group or distribute costs for internal chargeback. For more information, see [Organize your Azure resources with tags](https://azure.microsoft.com/updates/organize-your-azure-resources-with-tags/). |
112
112
| Term | All | Displays the term for the validity of the offer. For example: For reserved instances, it displays 12 months as the Term. For one-time purchases or recurring purchases, Term is one month (SaaS, Marketplace Support). Not applicable for Azure consumption. |
113
113
| UnitOfMeasure | All | The unit of measure for billing for the service. For example, compute services are billed per hour. |
114
-
| UnitPrice² | EA, pay-as-you-go | The price per unit for the charge. |
114
+
| UnitPrice² ³| EA, pay-as-you-go | The price for a given product or service inclusive of any negotiated discount that you might have on top of the market price (pay-as-you-go price) for your contract. |
115
115
116
116
¹ Fields used to build a unique ID for a single cost record. Every record in your cost details file should be considered unique.
117
117
118
118
² For MCA customers, prices are shown in the pricing currency in the Actual Cost and Amortized Cost reports. In contrast, for EA customers, the billing and pricing currencies are the same.
119
119
120
+
³ For more information about pricing terms and definitions, see [Pricing behavior in cost details](automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-details).
121
+
120
122
The cost details file itself doesn’t uniquely identify individual records with an ID. Instead, you can use fields in the file flagged with ¹ to create a unique ID yourself.
121
123
122
124
Some fields might differ in casing and spacing between account types. Older versions of pay-as-you-go cost details files have separate sections for the statement and daily cost.
0 commit comments