Skip to content

Commit 54d5ec2

Browse files
Merge pull request #276771 from bandersmsft/ingest-usage-details-overview
MCM - Update ingest-usage-detals-overview for Sharon
2 parents 0ce95a6 + 48c5073 commit 54d5ec2

File tree

4 files changed

+33
-19
lines changed

4 files changed

+33
-19
lines changed

articles/cost-management-billing/automate/automation-ingest-usage-details-overview.md

Lines changed: 28 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
44
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.
55
author: bandersmsft
66
ms.author: banders
7-
ms.date: 04/15/2024
7+
ms.date: 05/30/2024
88
ms.topic: conceptual
99
ms.service: cost-management-billing
1010
ms.subservice: cost-management
@@ -47,28 +47,42 @@ To learn more about Marketplace orders (also known as external services), see [U
4747

4848
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.
4949

50-
### Pricing behavior in cost details
50+
### Pricing behavior in cost and usage details
5151

52-
The cost details file exposes multiple price points. They're outlined as follows.
52+
The cost and usage details file exposes multiple price points. They're outlined as follows.
5353

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, `PayGPrice` 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.
54+
**PAYGPrice:** - The market price, also referred to as retail or list price, for a given product or service.
55+
- In all consumption usage records, `PayGPrice` reflects the market price of the meter, regardless of any benefit plan, such as reservations or savings plan, applied on that line item.
56+
- Purchases and refunds reflect the market price for that transaction.
5757

58-
When you deal with benefit-related records, where the `PricingModel` is `Reservations` or `SavingsPlan`, *PayGPrice* reflects the market price of the meter.
58+
In benefit-related records, where the `PricingModel` is `Reservations` or `SavingsPlan`, *PayGPrice* reflects the market price of the original meter, displaying what the price would have been without the application of a benefit.
5959

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.
60+
**UnitPrice:** - The price for a given product or service inclusive of any negotiated discount that is applied on top of the `PaygPrice` based on your contract.
61+
- In all consumption usage records, `UnitPrice` reflects the negotiated meter price based on your contract, regardless of any benefit plan such as reservations or savings plan, applied on that line item.
62+
- Purchases and refunds reflect the negotiated price for that transaction.
6363

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:
64+
**EffectivePrice** - The actual rate that you end up paying per unit for a given product or service. It's the price that should be used with the quantity to calculate charges (`price * quantity`) and reconcile them. The price considers the following scenarios:
6565
- Tiered pricing: For example: USD 10 for the first 100 units, USD 8 for the next 100 units.
6666
- 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.
6767
- 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.
6868

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.
69+
**Quantity:** - The number of units consumed per day by the given product or service. It relates to the unit of measure (UOM) used in actual resource usage.
7070

71-
If you want to reconcile costs with your price sheet or invoice, note the following information about unit of measure.
71+
## Reconcile charges
72+
73+
When you reconcile costs with your price sheet or invoice, the price points and quantity in cost and usage details file might differ in scale and granularity from these other documents.
74+
75+
For customers with an Enterprise Agreement, the cost and usage details might have a UOM (for example, per day vs per month) that is different from the invoice or price sheet. Cost and usage details is presented at a daily granularity, while the invoice is aggregated at a monthly, quarterly or a different custom billing period grain.
76+
77+
The following example illustrates how the same monthly total cost is represented differently across multiple reports for the same resource. This example considers a sample month of 31 days, and the invoice is generated every month.
78+
79+
| **Report** | **Unit of measure** | **Unit price** | **Total monthly quantity** | **Total month cost** | **Daily quantity** | **Daily cost** |
80+
| --- | --- | --- | --- | --- | --- | --- |
81+
| Invoice | 1/day | 100 | 31 | 3100 | N/A | N/A |
82+
| Cost and usage details | 1/month | 3100 | 1 | 3100 | 0.032257961<sup> 1 </sup>| 100 |
83+
| Price sheet | 1/day | 100 | N/A | N/A | N/A | N/A |
84+
85+
<sup> 1 </sup> Since the total monthly quantity is 1 unit, the daily quantity is estimated to be 1/31 = 0.03225796
7286

7387
**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.
7488

@@ -110,7 +124,7 @@ If you have charges that you don't recognize, there are several things you can d
110124
- Find people responsible for the resource and engage with them
111125
- Analyze the audit logs
112126
- Analyze user permissions to the resource's parent scope
113-
- Create an [Azure support request](https://go.microsoft.com/fwlink/?linkid=2083458) to help identify the charges
127+
- To help identify the charges, create an [Azure support request](https://go.microsoft.com/fwlink/?linkid=2083458)
114128

115129
For more information, see [Analyze unexpected charges](../understand/analyze-unexpected-charges.md).
116130

articles/cost-management-billing/automate/understand-usage-details-fields.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ MPA accounts have all MCA terms, in addition to the MPA terms, as described in t
7676
| MeterRegion | All | Name of the datacenter location for services priced based on location. See `Location`. |
7777
| MeterSubCategory | All | Name of the meter subclassification category. Purchases and Marketplace usage might be shown as blank or `unassigned`.|
7878
| OfferId¹ | EA, pay-as-you-go | Name of the Azure offer, which is the type of Azure subscription that you have. For more information, see supported [Microsoft Azure offer details](https://azure.microsoft.com/support/legal/offer-details/). |
79-
| pay-as-you-goPrice² ³| All | The market price, also referred to as retail or list price, for a given product or service. For more information, see [Pricing behavior in cost details](automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-details). |
79+
| pay-as-you-goPrice² ³| All | The market price, also referred to as retail or list price, for a given product or service. For more information, see [Pricing behavior in cost details](automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-and-usage-details). |
8080
| PartnerEarnedCreditApplied | MPA | Indicates whether the partner earned credit was applied. |
8181
| PartnerEarnedCreditRate | MPA | Rate of discount applied if there's a partner earned credit (PEC), based on partner admin link access. |
8282
| PartnerName | MPA | Name of the partner Microsoft Entra tenant. |
@@ -115,13 +115,13 @@ MPA accounts have all MCA terms, in addition to the MPA terms, as described in t
115115
| 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/). |
116116
| 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. |
117117
| UnitOfMeasure | All | The unit of measure for billing for the service. For example, compute services are billed per hour. |
118-
| UnitPrice² ³| All | 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. For more information, see [Pricing behavior in cost details](automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-details). |
118+
| UnitPrice² ³| All | 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. For more information, see [Pricing behavior in cost details](automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-and-usage-details). |
119119

120120
¹ Fields used to build a unique ID for a single cost record. Every record in your cost details file should be considered unique.
121121

122122
² 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.
123123

124-
³ 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).
124+
³ For more information about pricing terms and definitions, see [Pricing behavior in cost details](automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-and-usage-details).
125125

126126
⁴ The Connector for AWS in the Cost Management service retires on March 31, 2025. Users should consider alternative solutions for AWS cost management reporting. On March 31, 2024, Azure will disable the ability to add new Connectors for AWS for all customers. For more information, see [Retire your Amazon Web Services (AWS) connector](../costs/retire-aws-connector.md).
127127

articles/cost-management-billing/costs/get-started-partners.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,7 @@ The following data fields are found in usage detail files and Cost Management AP
239239
| tags | Tag that you assign to the meter. Use tags to group billing records. For example, you can use tags to distribute costs by the department that uses the meter. | Tags added by the customer.|
240240
| **partnerEarnedCreditRate** | Rate of discount applied if there's a partner earned credit (PEC) based on partner admin link access. | The rate of partner earned credit (PEC). For example, 0% or 15%. |
241241
| **partnerEarnedCreditApplied** | Indicates whether the partner earned credit was applied. | N/A |
242-
| unitPrice | 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. For more information, see [Pricing behavior in cost details](../automate/automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-details). | N/A |
242+
| unitPrice | 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. For more information, see [Pricing behavior in cost details](../automate/automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-and-usage-details). | N/A |
243243

244244
¹ The Connector for AWS in the Cost Management service retires on March 31, 2025. Users should consider alternative solutions for AWS cost management reporting. On March 31, 2024, Azure will disable the ability to add new Connectors for AWS for all customers. For more information, see [Retire your Amazon Web Services (AWS) connector](retire-aws-connector.md).
245245

articles/cost-management-billing/costs/manage-automation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Use the API to get all the data you need at the highest-level scope available. W
6262

6363
### Notes about pricing
6464

65-
If you want to reconcile usage and charges with your price sheet or invoice, see [Pricing behavior in cost details](../automate/automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-details).
65+
If you want to reconcile usage and charges with your price sheet or invoice, see [Pricing behavior in cost details](../automate/automation-ingest-usage-details-overview.md#pricing-behavior-in-cost-and-usage-details).
6666

6767
### A single resource might have multiple records for a single day
6868

0 commit comments

Comments
 (0)