Microsoft Customer Agreement price sheet schema
This article lists all of the data fields available in the Microsoft Customer Agreement price sheet. It's a data file that contains all of the prices for your Azure services.
Version 2023-05-01
Heres the list of all of the data fields found in your price sheet.
Column | Field Name | Description |
---|---|---|
1 | basePrice | The unit price at the time the customer signs the agreement. Or, the unit price at the time that the service meter becomes generally available (GA) if GA is after the agreement is signed. |
2 | billingAccountId | Unique identifier for the billing account. |
3 | billingAccountName | Name of the billing account. |
4 | billingCurrency | Currency in which charges are posted. |
5 | billingProfileId | Unique identifier for the billing profile. |
6 | billingProfileName | Name of the billing profile that is set up to receive invoices. The prices in the price sheet are associated with this billing profile. |
7 | currency | Currency in which all the prices are reflected. |
8 | discount | The price discount offered for Graduation Tier, Free Tier, Included Quantity, or Negotiated discounts when applicable. Represented as a percentage. Not available in the updated version of the price sheet. |
9 | effectiveEndDate | End date of the price sheet billing period. |
10 | effectiveStartDate | Start date of the price sheet billing period. |
11 | includedQuantity | Quantities of a specific service to which a customer is entitled to consume without incremental charges. Not available in the updated version of the price sheet. |
12 | marketPrice | The current list price for a given product or service. The price is without any negotiations and is based on your Microsoft Agreement type. For PriceType Consumption, marketPrice is reflected as the pay-as-you-go price. For PriceType Savings Plan, market price reflects the Savings plan benefit on top of pay-as-you-go price for the corresponding commitment term. For PriceType ReservedInstance, marketPrice reflects the total price of the one or three-year commitment. |
13 | meterId | Unique identifier for the meter. |
14 | meterCategory | Name of the classification category for the meter. For example, Cloud services, and Networking |
15 | meterName | Name of the meter. The meter represents the deployable resource of an Azure service. |
16 | meterSubCategory | Name of the meter subclassification category. |
17 | meterType | Name of the meter type. |
18 | meterRegion | Name of the region where the meter for the service is available. Identifies the location of the datacenter for certain services that are priced based on datacenter location. |
19 | priceType | Price type for a product. For example, an Azure resource has its pay-as-you-go rate with priceType as Consumption. If the resource is eligible for a savings plan, it also has its savings plan rate with another priceType as SavingsPlan. Other priceTypes include ReservedInstance. |
20 | Product | Name of the product accruing the charges. For example, Basic SQL DB vs Standard SQL DB. |
21 | productId | Unique identifier for the product whose meter is consumed. |
22 | serviceFamily | Type of Azure service. For example, Compute, Analytics, and Security. |
23 | SkuID | Unique identifier of the SKU. |
24 | Term | Duration associated with priceType. For example, SavingsPlan priceType has two commitment options: one year and three years. The Term is P1Y for a one-year commitment and P3Y for a three-year commitment. |
25 | tierMinimumUnits | Defines the lower bound of the tier range for which prices are defined. For example, if the range is 0 to 100, tierMinimumUnits would be 0. |
26 | unitOfMeasure | Identifies the units of measure for billing for the service. For example, compute services are billed per hour. |
27 | unitPrice | The per-unit price at the time of billing for a given product or service. It includes any negotiated discounts on top of the market price. For PriceType ReservedInstance, unitPrice reflects the total cost of the one or three-year commitment including discounts. Note: The unit price isn't the same as the effective price in usage details downloads when services have differential prices across tiers. If services have multi-tiered pricing, the effective price is a blended rate across the tiers and doesn't show a tier-specific unit price. The blended price or effective price is the net price for the consumed quantity spanning across the multiple tiers, where each tier has a specific unit price. |