Fixed PR review issues

Author: bandersmsft

articles/cost-management-billing/automate/automation-faq.md

@@ -20,7 +20,7 @@ Both are different names for the same dataset. Usage Details is the original nam
 
 ### Why do I get Usage Details API timeouts?
 
-Cost datasets available from the Usage Details API can often be overly large (multiple GBs or more). The larger the size of the dataset that you request, the longer the service takes to compile the data before sending it to you. Because of the delay, synchronous API solutions like the paginated [JSON Usage Details API](/rest/api/consumption/usage-details/list) might timeout before your data is provided. If you encounter timeouts or have processes that frequently need to pull a large amount of cost data, see [Retrieve large cost datasets recurringly with Exports](../costs/tutorial-export-acm-data.md).
+Cost datasets available from the Usage Details API can often be overly large (multiple GBs or more). The larger the size of the dataset that you request, the longer the service takes to compile the data before sending it to you. Because of the delay, synchronous API solutions like the paginated [JSON Usage Details API](/rest/api/consumption/usage-details/list) might time out before your data is provided. If you encounter timeouts or have processes that frequently need to pull a large amount of cost data, see [Retrieve large cost datasets recurringly with Exports](../costs/tutorial-export-acm-data.md).
 
 ### What is the difference between legacy and modern usage details?
 

articles/cost-management-billing/automate/migrate-consumption-usage-details-api.md

@@ -75,7 +75,7 @@ Enterprise Agreement customers who are using the Consumption Usage Details API h
 } 
 ```
 
-An full example legacy Usage Details record is shown at [Usage Details - List - REST API (Azure Consumption)](/rest/api/consumption/usage-details/list#billingaccountusagedetailslist-legacy)
+A full example legacy Usage Details record is shown at [Usage Details - List - REST API (Azure Consumption)](/rest/api/consumption/usage-details/list#billingaccountusagedetailslist-legacy)
 
 The following table provides a mapping between the old and new fields. New properties are available in the CSV files produced by Exports and the Cost Details API. To learn more about the fields, see [Understand usage details fields](understand-usage-details-fields.md).
 

articles/cost-management-billing/automate/migrate-ea-reporting-arm-apis-overview.md

@@ -1,7 +1,7 @@
 ---
 title: Migrate from EA Reporting to Azure Resource Manager APIs overview
 titleSuffix: Microsoft Cost Management
-description: This article provides and overview about migrating from EA Reporting to Azure Resource Manager APIs.
+description: This article provides an overview about migrating from EA Reporting to Azure Resource Manager APIs.
 author: bandersmsft
 ms.author: banders
 ms.date: 07/15/2022
@@ -25,7 +25,7 @@ The following information describes the differences between the older Reporting
 | Scopes and permissions | All requests are at the enrollment scope. API Key permission assignments will determine whether data for the entire enrollment, a department, or a specific account is returned. No user authentication. | Users or service principals are assigned access to the enrollment, department, or account scope. |
 | URI Endpoint | [https://consumption.azure.com](https://consumption.azure.com/) | [https://management.azure.com](https://management.azure.com/) |
 | Development status | In maintenance mode. On the path to deprecation. | In active development |
-| Available APIs | Limited to what's currently available | Equivalent APIs are available to replace each EA API. Additional [Cost Management APIs](/rest/api/cost-management/) are also available, including: <ul><li>Budgets<li>Alerts<li>Exports</ul> |
+| Available APIs | Limited to what's currently available | Equivalent APIs are available to replace each EA API. Additional [Cost Management APIs](/rest/api/cost-management/) are also available, including: <br>- Budgets<br>- Alerts<br>- Exports |
 
 ## Migration checklist
 

articles/cost-management-billing/automate/migrate-ea-usage-details-api.md

@@ -23,8 +23,8 @@ The following table provides a summary of the migration destinations that are av
 
 | Solution | Description | Considerations | Onboarding info |
 | --- | --- | --- | --- |
-| **Exports** | Recurring data dumps to storage on a schedule | <ul><li>The most scalable solution for your workloads. <li>Can be configured to use file partitioning for bigger datasets.<li>Great for establishing and growing a cost dataset that can be integrated with your own queryable data stores.<li>Requires access to a storage account that can hold the data.</ul> | <ul><li>[Configure in Azure portal](../costs/tutorial-export-acm-data.md)<li>[Automate Export creation with the API](../costs/ingest-azure-usage-at-scale.md)<li>[Export API Reference](/rest/api/cost-management/exports/create-or-update)</ul> |
-| **Cost Details API** | On demand download | <ul><li>Useful for small cost datasets.<li>Useful for scenarios when Exports to Azure storage aren't feasible due to security or manageability concerns.</ul> | <ul><li>[Get small cost datasets on demand](get-small-usage-datasets-on-demand.md)<li>[Cost Details](/rest/api/cost-management/generate-cost-details-report) API</ul> |
+| **Exports** | Recurring data dumps to storage on a schedule | - The most scalable solution for your workloads.<br> - Can be configured to use file partitioning for bigger datasets.<br> - Great for establishing and growing a cost dataset that can be integrated with your own queryable data stores.<br> -Requires access to a storage account that can hold the data. | - [Configure in Azure portal](../costs/tutorial-export-acm-data.md)<br>[Automate Export creation with the API](../costs/ingest-azure-usage-at-scale.md)<br> - [Export API Reference](/rest/api/cost-management/exports/create-or-update) |
+| **Cost Details API** | On demand download | - Useful for small cost datasets.<br> - Useful for scenarios when Exports to Azure storage aren't feasible due to security or manageability concerns. | - [Get small cost datasets on demand](get-small-usage-datasets-on-demand.md)<br> - [Cost Details](/rest/api/cost-management/generate-cost-details-report) API |
 
 Generally we recommend using [Exports](../costs/tutorial-export-acm-data.md) if you have ongoing data ingestion needs and/or a large monthly cost details dataset. For more information, see [Ingest cost details data](automation-ingest-usage-details-overview.md). If you need additional information to help you make a decision for your workload, see [Choose a cost details solution](usage-details-best-practices.md).
 
@@ -60,23 +60,23 @@ The table below summarizes the different APIs that you may be using today to ing
 
 | Endpoint | API Comments | 
 | --- | ---|
-| `/v3/enrollments/{enrollmentNumber}/usagedetails/download?billingPeriod={billingPeriod}` | <ul><li>API method: GET<li>Synchronous (non polling)<li>Data format: CSV</ul> |
-| `/v3/enrollments/{enrollmentNumber}/usagedetails/download?startTime=2017-01-01&endTime=2017-01-10` | <ul><li>API method: GET<li>Synchronous (non polling)<li>Data format: CSV</ul> |
-| `/v3/enrollments/{enrollmentNumber}/usagedetails` | <ul><li>API method: GET<li>Synchronous (non polling)<li>Data format: JSON</ul> | 
-| `/v3/enrollments/{enrollmentNumber}/billingPeriods/{billingPeriod}/usagedetails` | <ul><li>API method: GET<li>Synchronous (non polling)<li>Data format: JSON</ul> |
-| `/v3/enrollments/{enrollmentNumber}/usagedetailsbycustomdate?startTime=2017-01-01&endTime=2017-01-10` | <ul><li>API method: GET<li>Synchronous (non polling)<li>Data format: JSON</ul> |
-| `/v3/enrollments/{enrollmentNumber}/usagedetails/submit?billingPeriod={billingPeriod}` | <ul><li>API method: POST<li>Asynchronous (polling based)<li>Data format: CSV</ul> |
-| `/v3/enrollments/{enrollmentNumber}/usagedetails/submit?startTime=2017-04-01&endTime=2017-04-10` | <ul><li>API method: POST<li>Asynchronous (polling based)<li>Data format: CSV</ul> |
+| `/v3/enrollments/{enrollmentNumber}/usagedetails/download?billingPeriod={billingPeriod}` | - API method: GET<br> - Synchronous (non polling)<br> - Data format: CSV |
+| `/v3/enrollments/{enrollmentNumber}/usagedetails/download?startTime=2017-01-01&endTime=2017-01-10` | - API method: GET <br> - Synchronous (non polling)<br> - Data format: CSV |
+| `/v3/enrollments/{enrollmentNumber}/usagedetails` | - API method: GET<br> - Synchronous (non polling)<br> - Data format: JSON | 
+| `/v3/enrollments/{enrollmentNumber}/billingPeriods/{billingPeriod}/usagedetails` | - API method: GET<br> - Synchronous (non polling)<br> - Data format: JSON |
+| `/v3/enrollments/{enrollmentNumber}/usagedetailsbycustomdate?startTime=2017-01-01&endTime=2017-01-10` | - API method: GET<br> - Synchronous (non polling)<br> - Data format: JSON |
+| `/v3/enrollments/{enrollmentNumber}/usagedetails/submit?billingPeriod={billingPeriod}` | - API method: POST<br> - Asynchronous (polling based)<br> - Data format: CSV |
+| `/v3/enrollments/{enrollmentNumber}/usagedetails/submit?startTime=2017-04-01&endTime=2017-04-10` | - API method: POST<br> - Asynchronous (polling based)<br> - Data format: CSV |
 
 ## Enterprise Marketplace Store Charge APIs to migrate off
 
 In addition to the usage details APIs outlined above, you'll need to migrate off the [Enterprise Marketplace Store Charge APIs](/rest/api/billing/enterprise/billing-enterprise-api-marketplace-storecharge). All Azure and Marketplace charges have been merged into a single file that is available through the new solutions. You can identify which charges are *Azure* versus *Marketplace* charges by using the `PublisherType` field that is available in the new dataset. The table below outlines the applicable APIs. All of the following APIs are behind the *https://consumption.azure.com* endpoint.
 
 | Endpoint | API Comments | 
 | --- | --- |
-| `/v3/enrollments/{enrollmentNumber}/marketplacecharges` | <ul><li>API method: GET<li>Synchronous (non polling)<li>Data format: JSON</ul> |
-| `/v3/enrollments/{enrollmentNumber}/billingPeriods/{billingPeriod}/marketplacecharges` | <ul><li>API method: GET<li>Synchronous (non polling)<li>Data format: JSON</ul> |
-| `/v3/enrollments/{enrollmentNumber}/marketplacechargesbycustomdate?startTime=2017-01-01&endTime=2017-01-10` | <ul><li>API method: GET<li>Synchronous (non polling)<li>Data format: JSON</ul> | 
+| `/v3/enrollments/{enrollmentNumber}/marketplacecharges` | - API method: GET<br> - Synchronous (non polling)<br> - Data format: JSON |
+| `/v3/enrollments/{enrollmentNumber}/billingPeriods/{billingPeriod}/marketplacecharges` | - API method: GET<br> - Synchronous (non polling)<br> - Data format: JSON |
+| `/v3/enrollments/{enrollmentNumber}/marketplacechargesbycustomdate?startTime=2017-01-01&endTime=2017-01-10` | - API method: GET<br> - Synchronous (non polling)<br> - Data format: JSON | 
 
 ## Data field mapping
 

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

@@ -30,48 +30,48 @@ The following table describes the important terms used in the latest version of
 | Term | Account type | Description |
 | --- | --- | --- |
 | AccountName | EA, pay-as-you-go | Display name of the EA enrollment account or pay-as-you-go billing account. |
-| AccountOwnerId<sup>1</sup> | EA, pay-as-you-go | Unique identifier for the EA enrollment account or pay-as-you-go billing account. |
+| AccountOwnerId¹ | EA, pay-as-you-go | Unique identifier for the EA enrollment account or pay-as-you-go billing account. |
 | AdditionalInfo | All | Service-specific metadata. For example, an image type for a virtual machine. |
-| BillingAccountId<sup>1</sup> | All | Unique identifier for the root billing account. |
+| BillingAccountId¹ | All | Unique identifier for the root billing account. |
 | BillingAccountName | All | Name of the billing account. |
 | BillingCurrency | All | Currency associated with the billing account. |
 | BillingPeriod | EA, pay-as-you-go | The billing period of the charge. |
 | BillingPeriodEndDate | All | The end date of the billing period. |
 | BillingPeriodStartDate | All | The start date of the billing period. |
-| BillingProfileId<sup>1</sup> | All | Unique identifier of the EA enrollment, pay-as-you-go subscription, MCA billing profile, or AWS consolidated account. |
+| BillingProfileId¹ | All | Unique identifier of the EA enrollment, pay-as-you-go subscription, MCA billing profile, or AWS consolidated account. |
 | BillingProfileName | All | Name of the EA enrollment, pay-as-you-go subscription, MCA billing profile, or AWS consolidated account. |
 | ChargeType | All | Indicates whether the charge represents usage (**Usage**), a purchase (**Purchase**), or a refund (**Refund**). |
 | ConsumedService | All | Name of the service the charge is associated with. |
-| CostCenter<sup>1</sup> | EA, MCA | The cost center defined for the subscription for tracking costs (only available in open billing periods for MCA accounts). |
+| CostCenter¹ | EA, MCA | The cost center defined for the subscription for tracking costs (only available in open billing periods for MCA accounts). |
 | Cost | EA, pay-as-you-go | See CostInBillingCurrency. |
 | CostInBillingCurrency | MCA | Cost of the charge in the billing currency before credits or taxes. |
 | CostInPricingCurrency | MCA | Cost of the charge in the pricing currency before credits or taxes. |
 | Currency | EA, pay-as-you-go | See `BillingCurrency`. |
-| Date<sup>1</sup> | All | The usage or purchase date of the charge. |
+| 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. |
 | 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**). |
 | InvoiceId | pay-as-you-go, MCA | The unique document ID listed on the invoice PDF. |
 | InvoiceSection | MCA | See `InvoiceSectionName`. |
-| InvoiceSectionId<sup>1</sup> | EA, MCA | Unique identifier for the EA department or MCA invoice section. |
+| InvoiceSectionId¹ | EA, MCA | Unique identifier for the EA department or MCA invoice section. |
 | InvoiceSectionName | EA, MCA | Name of the EA department or MCA invoice section. |
 | IsAzureCreditEligible | All | Indicates if the charge is eligible to be paid for using Azure credits (Values: `True` or `False`). |
 | Location | MCA | Datacenter location where the resource is running. |
 | MeterCategory | All | Name of the classification category for the meter. For example, _Cloud services_ and _Networking_. |
-| MeterId<sup>1</sup> | All | The unique identifier for the meter. |
+| MeterId¹ | All | The unique identifier for the meter. |
 | MeterName | All | The name of the meter. |
 | MeterRegion | All | Name of the datacenter location for services priced based on location. See Location. |
 | MeterSubCategory | All | Name of the meter subclassification category. |
-| OfferId<sup>1</sup> | All | Name of the offer purchased. |
+| OfferId¹ | All | Name of the offer purchased. |
 | pay-as-you-goPrice | All | Retail price for the resource. |
-| PartNumber<sup>1</sup> | EA, pay-as-you-go | Identifier used to get specific meter pricing. |
+| PartNumber¹ | EA, pay-as-you-go | Identifier used to get specific meter pricing. |
 | PlanName | EA, pay-as-you-go | Marketplace plan name. |
 | PreviousInvoiceId | MCA | Reference to an original invoice if the line item is a refund. |
 | PricingCurrency | MCA | Currency used when rating based on negotiated prices. |
 | PricingModel | All | Identifier that indicates how the meter is priced. (Values: `On Demand`, `Reservation`, and `Spot`) |
 | Product | All | Name of the product. |
-| ProductId<sup>1</sup> | MCA | Unique identifier for the product. |
+| ProductId¹ | MCA | Unique identifier for the product. |
 | ProductOrderId | All | Unique identifier for the product order. |
 | ProductOrderName | All | Unique name for the product order. |
 | Provider | All | Identifier for product category or Line of Business. For example, Azure, Microsoft 365, and AWS. |
@@ -81,24 +81,24 @@ The following table describes the important terms used in the latest version of
 | ReservationId | EA, MCA | Unique identifier for the purchased reservation instance. |
 | ReservationName | EA, MCA | Name of the purchased reservation instance. |
 | ResourceGroup | All | Name of the [resource group](../../azure-resource-manager/management/overview.md) the resource is in. Not all charges come from resources deployed to resource groups. Charges that don't have a resource group will be shown as null or empty, **Others**, or **Not applicable**. |
-| ResourceId<sup>1</sup> | All | Unique identifier of the [Azure Resource Manager](/rest/api/resources/resources) resource. |
+| ResourceId¹ | All | Unique identifier of the [Azure Resource Manager](/rest/api/resources/resources) resource. |
 | ResourceLocation | All | Datacenter location where the resource is running. See `Location`. |
 | ResourceName | EA, pay-as-you-go | Name of the resource. Not all charges come from deployed resources. Charges that don't have a resource type will be shown as null/empty, **Others** , or **Not applicable**. |
 | ResourceType | MCA | Type of resource instance. Not all charges come from deployed resources. Charges that don't have a resource type will be shown as null/empty, **Others** , or **Not applicable**. |
 | ServiceFamily | MCA | Service family that the service belongs to. |
-| ServiceInfo<sup>1</sup> | All | Service-specific metadata. |
+| ServiceInfo¹ | All | Service-specific metadata. |
 | ServiceInfo2 | All | Legacy field with optional service-specific metadata. |
 | ServicePeriodEndDate | MCA | The end date of the rating period that defined and locked pricing for the consumed or purchased service. |
 | ServicePeriodStartDate | MCA | The start date of the rating period that defined and locked pricing for the consumed or purchased service. |
-| SubscriptionId<sup>1</sup> | All | Unique identifier for the Azure subscription. |
+| SubscriptionId¹ | All | Unique identifier for the Azure subscription. |
 | SubscriptionName | All | Name of the Azure subscription. |
-| Tags<sup>1</sup> | 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/). |
+| 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: In case of 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. |
 | CostAllocationRuleName | EA, MCA | Name of the Cost Allocation rule that's applicable to the record. |
 
-<sup>1</sup> Fields used to build a unique ID for a single cost record.
+¹ Fields used to build a unique ID for a single cost record.
 
 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.