Merge pull request #218452 from bandersmsft/cm-misc-updates-11152022

MCM - Misc Cost Management updates for Adam

Author: prmerger-automator[bot]

articles/cost-management-billing/cost-management-billing-faq.yml

@@ -133,7 +133,7 @@ sections:
     questions:
       - question: When are the EA Reporting APIs going to be deprecated?
         answer: |
-          The Cost Management + Billing team hasn't announced a deprecation timeline for the APIs. The APIs are no longer in active development. We recommend that you plan any needed work to migrate away from them.
+          The Cost Management + Billing team has formally announced the retirement of the APIs with a timeline of Oct 2023. We recommend that you migrate away from the APIs before their retirement. For more information, [Migrate from Azure Enterprise Reporting APIs to Microsoft Cost Management APIs](./automate/migrate-ea-reporting-arm-apis-overview.md).
       - question: How do I migrate off of the EA Reporting APIs and what new APIs should I call?
         answer: |
           See [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs](automate/migrate-ea-reporting-arm-apis-overview.md).

articles/cost-management-billing/costs/tutorial-export-acm-data.md

@@ -20,7 +20,7 @@ Watch the [How to schedule exports to storage with Cost Management](https://www.
 
 >[!VIDEO https://www.youtube.com/embed/rWa_xI1aRzo]
 
-The examples in this tutorial walk you though exporting your cost management data and then verify that the data was successfully exported.
+The examples in this tutorial walk you through exporting your cost management data and then verify that the data was successfully exported.
 
 In this tutorial, you learn how to:
 
@@ -75,7 +75,7 @@ To create or view a data export or to schedule an export, choose a scope in the
     :::image type="content" source="./media/tutorial-export-acm-data/basics_exports.png" alt-text="New export example" lightbox="./media/tutorial-export-acm-data/basics_exports.png":::
 1. Review your export details and select **Create**.
 
-Your new export appears in the list of exports. By default, new exports are enabled. If you want to disable or delete a scheduled export, select any item in the list and then select either **Disable** or **Delete**.
+Your new export appears in the list of exports. By default, new exports are enabled. If you want to disable or delete a scheduled export, select any item in the list, and then select either **Disable** or **Delete**.
 
 Initially, it can take 12-24 hours before the export runs. However, it can take up longer before data is shown in exported files.
 
@@ -120,7 +120,7 @@ Start by preparing your environment for the Azure CLI:
    --schedule-status Active --storage-directory demodirectory
    ```
 
-   For the **--type** parameter, you can choose `ActualCost`, `AmortizedCost`, or `Usage`.
+   For the `--type` parameter, you can choose `ActualCost`, `AmortizedCost`, or `Usage`.
 
    This example uses `MonthToDate`. The export creates an export file daily for your month-to-date costs. The latest data is aggregated from previous daily exports this month.
 
@@ -241,20 +241,20 @@ Remove-AzCostManagementExport -Name DemoExport -Scope 'subscriptions/00000000-00
 
 ### Export schedule
 
-Scheduled exports are affected by the time and day of week of when you initially create the export. When you create a scheduled export, the export runs at the same frequency for each export that runs later. For example, for a daily export of month-to-date costs export set at a daily frequency, the export runs daily. Similarly for a weekly export, the export runs every week on the same day as it is scheduled. The exact delivery time of the export isn't guaranteed and the exported data is available within four hours of run time.
+Scheduled exports are affected by the time and day of week of when you initially create the export. When you create a scheduled export, the export runs at the same frequency for each export that runs later. For example, for a daily export of month-to-date costs export set at a daily frequency, the export runs during once each UTC day. Similarly for a weekly export, the export runs every week on the same UTC day as it is scheduled. Individual export runs can occur at different times throughout the day. So, avoid taking a firm dependency on the exact time of the export runs. Run timing depends on the active load present in Azure during a given UTC day. When an export run begins, your data should be available within 4 hours.
 
 Exports are scheduled using Coordinated Universal Time (UTC). The Exports API always uses and displays UTC.
 
 - When you create an export using the [Exports API](/rest/api/cost-management/exports/create-or-update?tabs=HTTP), specify the `recurrencePeriod` in UTC time. The API doesn’t convert your local time to UTC.
     - Example - A weekly export is scheduled on Friday, August 19 with `recurrencePeriod` set to 2:00 PM. The API receives the input as 2:00 PM UTC, Friday, August 19. The weekly export will be scheduled to run every Friday.
 - When you create an export in the Azure portal, its start date time is automatically converted to the equivalent UTC time.
-    - Example - A weekly export is scheduled on Friday, August 19 with the local time of 2:00 AM IST (UTC+5:30) from the Azure portal. The API receives the input as 8:30 PM, Thursday, August 18th. The weekly export will be scheduled to run every Thursday.
+    - Example - A weekly export is scheduled on Friday, August 19 with the local time of 2:00 AM IST (UTC+5:30) from the Azure portal. The API receives the input as 8:30 PM, Thursday, August 18. The weekly export will be scheduled to run every Thursday.
 
 Each export creates a new file, so older exports aren't overwritten.
 
 #### Create an export for multiple subscriptions
 
-If you have an Enterprise Agreement, then you can use a management group to aggregate subscription cost information in a single container. Then you can export cost management data for the management group. Exports for management groups only support actual costs.
+If you have an Enterprise Agreement, then you can use a management group to aggregate subscription cost information in a single container. Then you can export cost management data for the management group. When you create an export in the Azure portal, select the **Actual Costs** option. When you create a management group export using the API, create a *usage export*. Currently, exports at the management group scope only support usage charges. Purchases including reservations and savings plans aren't present in your exports file.
 
 Exports for management groups of other subscription types aren't supported.
 
@@ -311,7 +311,6 @@ When you create a scheduled export in the Azure portal or with the API, it alway
 
 If you want to use the latest data and fields available, we recommend that you create a new export in the Azure portal. To update an existing export to the latest version, update it in the Azure portal or with the latest Export API version. Updating an existing export might cause you to see minor differences in the fields and charges in files that are produced afterward.
 
-
 ## Verify that data is collected
 
 You can easily verify that your Cost Management data is being collected and view the exported CSV file using Azure Storage Explorer.
@@ -355,7 +354,6 @@ Select an export to view its run history.
 
 If you've created a daily export, you'll have two runs per day for the first five days of each month. One run executes and creates a file with the current month’s cost data. It's the run that's available for you to see in the run history. A second run also executes to create a file with all the costs from the prior month. The second run isn't currently visible in the run history. Azure executes the second run to ensure that your latest file for the past month contains all charges exactly as seen on your invoice. It runs because there are cases where latent usage and charges are included in the invoice up to 72 hours after the calendar month has closed. To learn more about Cost Management usage data updates, see [Cost and usage data updates and retention](understand-cost-mgt-data.md#cost-and-usage-data-updates-and-retention). 
 
-
 ## Access exported data from other systems
 
 One of the purposes of exporting your Cost Management data is to access the data from external systems. You might use a dashboard system or other financial system. Such systems vary widely so showing an example wouldn't be practical.  However, you can get started with accessing your data from your applications at [Introduction to Azure Storage](../../storage/common/storage-introduction.md).

articles/cost-management-billing/savings-plan/purchase-recommendations.md

@@ -9,7 +9,7 @@ ms.service: cost-management-billing
 ms.subservice: reservations
 ms.custom: ignite-2022
 ms.topic: conceptual
-ms.date: 11/04/2022
+ms.date: 11/15/2022
 ---
 
 # Azure savings plan recommendations
@@ -45,7 +45,7 @@ The minimum value doesn't necessarily represent the hourly commitment necessary
 
 1. Download your price list.
 2. For each reservation order you're returning, find the product in the price sheet and determine its unit price under either a 1-year or 3-year savings plan (filter by term and price type).
-3. Multiple the rate by the number of instances that are being returned.
+3. Multiply the rate by the number of instances that are being returned.
 4. Repeat for each reservation order to be returned.
 5. Sum the values and enter it as the hourly commitment.