updated tables with new defs and superscript notes and links

Author: bandersmsft

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

@@ -13,7 +13,7 @@ ms.reviewer: jojoh
 
 # Ingest cost details data
 
-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).
+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). 
 
 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.
 

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

@@ -56,7 +56,7 @@ MPA accounts have all MCA terms, in addition to the MPA terms, as described in t
 | CustomerName | MPA | Name of the Microsoft Entra tenant for the customer's subscription. |
 | CustomerTenantId | MPA | Identifier of the Microsoft Entra tenant of the customer's subscription. |
 | Date¹ | All | The usage or purchase date of the charge. |
-| 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. |
+| EffectivePrice² ³ | All | The price for a given product or service that represents the actual rate that you end up paying per unit. |
 | ExchangeRateDate | MCA | Date the exchange rate was established. |
 | ExchangeRatePricingToBilling | MCA | Exchange rate used to convert the cost in the pricing currency to the billing currency. |
 | 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
 | MeterRegion | All | Name of the datacenter location for services priced based on location. See Location. |
 | MeterSubCategory | All | Name of the meter subclassification category. Purchases and Marketplace usage might be shown as blank or `unassigned`.|
 | OfferId¹ | All | Name of the offer purchased. |
-| pay-as-you-goPrice² | All | Retail price for the resource. |
-| PartnerEarnedCreditApplied | MPA | Indicates whether the partner earned credit has been applied. |
+| pay-as-you-goPrice² ³| All | The market price, also referred to as retail or list price, for a given product or service. |
+| PartnerEarnedCreditApplied | MPA | Indicates whether the partner earned credit was applied. |
 | PartnerEarnedCreditRate | MPA | Rate of discount applied if there's a partner earned credit (PEC), based on partner admin link access. |
 | PartnerName | MPA | Name of the partner Microsoft Entra tenant. |
 | 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
 | PublisherId | MCA | The ID of the publisher. It's only available after the invoice is generated. |
 | PublisherName | All | Publisher for Marketplace services. |
 | PublisherType | All | Supported values: **Microsoft**, **Azure**, **AWS**, **Marketplace**. Values are `Microsoft` for MCA accounts and `Azure` for EA and pay-as-you-go accounts. |
-| Quantity | All | The number of units purchased or consumed. |
+| Quantity³ | All | The number of units used by the given product or service for a given day. |
 | ResellerName | MPA | The name of the reseller associated with the subscription. |
 | ResellerMpnId | MPA | ID for the reseller associated with the subscription. |
 | 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
 | 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/). |
 | 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. |
 | UnitOfMeasure | All | The unit of measure for billing for the service. For example, compute services are billed per hour. |
-| UnitPrice² | EA, pay-as-you-go | The price per unit for the charge. |
+| 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. |
 
 ¹ Fields used to build a unique ID for a single cost record. Every record in your cost details file should be considered unique. 
 
 ² 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.
 
+³ 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).
+
 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.
 
 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.

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

@@ -3,11 +3,11 @@ title: Manage Azure costs with automation
 description: This article explains how you can manage Azure costs with automation.
 author: bandersmsft
 ms.author: banders
-ms.date: 11/22/2022
+ms.date: 12/11/2023
 ms.topic: conceptual
 ms.service: cost-management-billing
 ms.subservice: cost-management
-ms.reviewer: adwise
+ms.reviewer: jojo
 ---
 
 # Manage costs with automation
@@ -20,7 +20,7 @@ You might need to download your Azure cost data to merge it with other datasets.
 
 ## Suggestions for handling large datasets
 
-If your organization has a large Azure presence across many resources or subscriptions, you'll have a large amount of usage details data. Excel often can't load such large files. In this situation, we recommend the following options:
+If your organization has a large Azure presence across many resources or subscriptions, you'll have a large amount of usage details data results. Excel often can't load such large files. In this situation, we recommend the following options:
 
 **Power BI**
 
@@ -62,19 +62,7 @@ Use the API to get all the data you need at the highest-level scope available. W
 
 ### Notes about pricing
 
-If you want to reconcile usage and charges with your price sheet or invoice, note the following information.
-
-Price Sheet price 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. Unfortunately, the unit of measure doesn't always align to the unit of measure at which the actual resource usage and charges are emitted.
-
-Usage Details price behavior - Usage files show scaled information that may not match precisely with the price sheet. Specifically:
-
-- Unit Price - The price is scaled to match the unit of measure at which the charges are actually emitted by Azure resources. If scaling occurs, then the price won't match the price seen in the Price Sheet.
-- Unit of Measure - Represents the unit of measure at which charges are actually emitted by Azure resources.
-- Effective Price / Resource Rate - The price represents the actual rate that you end up paying per unit, after discounts are taken into account. 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 and the scaled unit price that's also present in the files. As a result, it might differ from the scaled unit price.
-  - Tiered pricing - For example: $10 for the first 100 units, $8 for the next 100 units.
-  - Included quantity - For example: The first 100 units are free and then $10 per unit.
-  - Reservations
-  - Rounding that occurs during calculation – Rounding takes into account the consumed quantity, tiered/included quantity pricing, and the scaled unit price.
+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).
 
 ### A single resource might have multiple records for a single day
 
@@ -314,7 +302,7 @@ The following quotas are configured per tenant. Requests are throttled when any
 - 60 QPU per 1 min
 - 600 QPU per 1 hour
 
-The quotas maybe be changed as needed and more quotas may be added.
+The quotas maybe be changed as needed and more quotas can be added.
 
 #### Response headers