Merge pull request #220479 from bandersmsft/rename-ea-portal-rest-apis

MCM - Renamed file ea-portal-rest-apis

Author: v-stsavell

articles/cost-management-billing/.openpublishing.redirection.cost-management-billing.json

@@ -207,7 +207,12 @@
         },
         {
             "source_path_from_root": "/articles/billing/billing-ea-portal-rest-apis.md",
-            "redirect_url": "/azure/cost-management-billing/manage/ea-portal-rest-apis",
+            "redirect_url": "/azure/cost-management-billing/manage/enterprise-rest-apis",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/cost-management-billing/manage/ea-portal-rest-apis.md",
+            "redirect_url": "/azure/cost-management-billing/manage/enterprise-rest-apis",
             "redirect_document_id": true
         },
         {

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

@@ -139,7 +139,7 @@ sections:
           See [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs](automate/migrate-ea-reporting-arm-apis-overview.md).
       - question: Why do I get Usage Details API timeouts?
         answer: |
-          The Usage Details dataset can often be very 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/usagedetails/list) might timeout before your data is provided. If you are encounter timeouts or have processes that frequently need to pull a large amount of usage details, see [Retrieve large usage datasets recurringly with Exports](costs/ingest-azure-usage-at-scale.md).
+          The Usage Details dataset can often be very 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/usagedetails/list) might timeout before your data is provided. If your encounter timeouts or has processes that frequently need to pull a large number of usage details, see [Retrieve large usage datasets recurringly with Exports](costs/ingest-azure-usage-at-scale.md).
       - question: How do I migrate from the EA Reporting APIs to the Microsoft Customer Agreement APIs?
         answer: |
           See [Migrate from Enterprise Agreement to Microsoft Customer Agreement APIs](costs/migrate-cost-management-api.md).
@@ -148,7 +148,7 @@ sections:
     questions:
       - question: Why do I get Usage Details API timeouts?
         answer: |
-          The Usage Details dataset can often be very 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 might timeout before your data is provided. If you encounter timeouts or have processes that frequently need to pull a large amount of usage details, see [Retrieve large usage datasets recurringly with Exports](costs/ingest-azure-usage-at-scale.md).
+          The Usage Details dataset can often be very 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 might timeout before your data is provided. If you encounter timeouts or have processes that frequently need to pull a large number of usage details, see [Retrieve large usage datasets recurringly with Exports](costs/ingest-azure-usage-at-scale.md).
       - question: What is the difference between legacy and modern usage details?
         answer: |
           A legacy versus modern usage details record is identified by the *kind* field in the [Usage Details API](/rest/api/consumption/usage-details). The field is used to distinguish between data that’s returned for different customer types. The call patterns to obtain legacy and modern usage details are essentially the same. The granularity of the data is the same. The main difference is the fields available in the usage details records themselves. If you’re an EA customer, you’ll always get legacy usage details records. If you’re a Microsoft Customer Agreement customer, you will always get modern usage details records.
@@ -340,7 +340,7 @@ sections:
           
           After you have created departments and subscriptions, you can see data in the usage report. This information can help you track usage and manage cost and spend at the department level.
           
-          You can also access usage data via the reporting API. For detailed information and sample code, see [Azure Enterprise REST APIs](manage/ea-portal-rest-apis.md).
+          You can also access usage data via the reporting API. For detailed information and sample code, see [Azure Enterprise REST APIs](manage/enterprise-rest-apis.md).
           
           Direct enterprise customers can view usage and spending at different department levels in the Azure portal. Navigate to the **Department** menu to view charges.
       - question: Can I set a spending quota and get alerts as I approach my limit?
@@ -352,7 +352,7 @@ sections:
         answer: |
           If you use _resource groups_ and _tags_, this information is tracked at service level, and you can access it in the detailed usage download (CSV) file. See the [download usage report](https://ea.azure.com/report/downloadusage) in the Azure Enterprise portal.
           
-          You can also access usage via API. For detailed information and sample code, see [Azure Enterprise REST APIs](manage/ea-portal-rest-apis.md).
+          You can also access usage via API. For detailed information and sample code, see [Azure Enterprise REST APIs](manage/enterprise-rest-apis.md).
           
           > [!NOTE]
           > You can only apply tags to resources that support Azure Resource Manager operations. If you created a virtual machine, virtual network, or storage through the classic deployment model (such as through the classic portal), you cannot apply a tag to that resource. You must re-deploy these resources through the Resource Manager to support tagging. All other resources support tagging.

articles/cost-management-billing/manage/ea-portal-get-started.md

@@ -66,7 +66,7 @@ To view usage summary, download reports, and manage enrollment invoices, see [Az
 
 If you'd like to know about how Azure reservations for VM reserved instances can help you save money with your enterprise enrollment, see [Azure EA VM reserved instances](./ea-portal-vm-reservations.md).
 
-For information on which REST APIs to use with your Azure enterprise enrollment and an explanation for how to resolve common issues with REST APIs, see [Azure Enterprise REST APIs](./ea-portal-rest-apis.md).
+For information on which REST APIs to use with your Azure enterprise enrollment and an explanation for how to resolve common issues with REST APIs, see [Azure Enterprise REST APIs](./enterprise-rest-apis.md).
 
 [Azure EA agreements and amendments](./ea-portal-agreements.md) describes how Azure EA agreements and amendments might affect your access, use, and payments for Azure services.
 

articles/cost-management-billing/manage/ea-portal-rest-apis.md renamed to articles/cost-management-billing/manage/enterprise-rest-apis.md

@@ -39,7 +39,7 @@ Role owners can perform the following steps in the Azure portal to enable API da
 3. Select **Billing scopes** from the navigation menu and then select the billing account that you want to work with.
 4. In the left navigation menu, select **Usage + Charges**.
 5. Select **Manage API Access Keys** to open the Manage API Access Keys window.  
-    :::image type="content" source="./media/ea-portal-rest-apis/manage-api-access-keys.png" alt-text="Screenshot showing the Manage API Access Keys option." lightbox="./media/ea-portal-rest-apis/manage-api-access-keys.png" :::
+    :::image type="content" source="./media/enterprise-rest-apis/manage-api-access-keys.png" alt-text="Screenshot showing the Manage API Access Keys option." lightbox="./media/enterprise-rest-apis/manage-api-access-keys.png" :::
 
 In the Manage API Access Keys window, you can perform the following tasks:
 
@@ -55,9 +55,9 @@ In the Manage API Access Keys window, you can perform the following tasks:
 4. In the navigation menu, select **Usage + Charges**.
 5. Select **Manage API Access Keys**.
 6. Select **Generate** to generate the key.  
-    :::image type="content" source="./media/ea-portal-rest-apis/manage-api-access-keys-window.png" alt-text="Screenshot showing the Manage API Access Keys window." lightbox="./media/ea-portal-rest-apis/manage-api-access-keys-window.png" :::
+    :::image type="content" source="./media/enterprise-rest-apis/manage-api-access-keys-window.png" alt-text="Screenshot showing the Manage API Access Keys window." lightbox="./media/enterprise-rest-apis/manage-api-access-keys-window.png" :::
 7. Select the **expand symbol** or select **Copy** to get the API access key for immediate use.  
-    :::image type="content" source="./media/ea-portal-rest-apis/expand-symbol-copy.png" alt-text="Screenshot showing the expand symbol and Copy option." lightbox="./media/ea-portal-rest-apis/expand-symbol-copy.png" :::
+    :::image type="content" source="./media/enterprise-rest-apis/expand-symbol-copy.png" alt-text="Screenshot showing the expand symbol and Copy option." lightbox="./media/enterprise-rest-apis/expand-symbol-copy.png" :::
 
 ### Regenerate the primary or secondary API key
 
@@ -86,7 +86,7 @@ The steps give API access to key holders so they can view cost and pricing infor
 1. In the left navigation window, select **Policies**.
 2. Select **On** under the DEPARTMENT ADMINS CAN VIEW CHARGES section and then select **Save**.
 3. Select **On** under the ACCOUNT OWNERS CAN VIEW CHARGES section and then select **Save**.  
-    :::image type="content" source="./media/ea-portal-rest-apis/policies-view-charges.png" alt-text="Screenshot showing the Polices window where you change view charges options." lightbox="./media/ea-portal-rest-apis/policies-view-charges.png" :::
+    :::image type="content" source="./media/enterprise-rest-apis/policies-view-charges.png" alt-text="Screenshot showing the Polices window where you change view charges options." lightbox="./media/enterprise-rest-apis/policies-view-charges.png" :::
 
 ## Pass keys in the API