Merge pull request #272161 from bandersmsft/automate-ingest-usage-details-overview

MCM - Limitation on unitprice

Author: prmerger-automator[bot]

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

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
 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.
 author: bandersmsft
 ms.author: banders
-ms.date: 02/22/2024
+ms.date: 04/15/2024
 ms.topic: conceptual
 ms.service: cost-management-billing
 ms.subservice: cost-management
@@ -98,7 +98,7 @@ Sample amortized cost report:
 >    - 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`.
+>    - 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](../costs/allocate-costs.md#current-limitations).
 >    - For MCA customers, `UnitPrice` isn't populated when `PricingModel` = `Reservations`.
 
 ## Unexpected charges