Merge pull request #272496 from MicrosoftDocs/main

4/17 OOB Publish at 11am

Author: huypub

articles/advisor/advisor-how-to-calculate-total-cost-savings.md

@@ -1,11 +1,15 @@
 ---
-title: Export cost savings in Azure Advisor
+title: Calculate cost savings in Azure Advisor
 ms.topic: article
 ms.date: 02/06/2024
 description: Export cost savings in Azure Advisor and calculate the aggregated potential yearly savings by using the cost savings amount for each recommendation.
 ---
 
-# Export cost savings
+# Calculate cost savings
+
+This article provides guidance on how to calculate total cost savings in Azure Advisor. 
+
+## Export cost savings for recommendations
 
 To calculate aggregated potential yearly savings, follow these steps: 
 
@@ -21,5 +25,14 @@ The Advisor **Overview** page opens.
     [![Screenshot of the Azure Advisor cost recommendations page that shows download option.](./media/advisor-how-to-calculate-total-cost-savings.png)](./media/advisor-how-to-calculate-total-cost-savings.png#lightbox)
 
 > [!NOTE]
-> Recommendations show savings individually, and may overlap with the savings shown in other recommendations, for example – you can only benefit from savings plans for compute or reservations for virtual machines, but not from both.
+> Different types of cost savings recommendations are generated using overlapping datasets (for example, VM rightsizing/shutdown, VM reservations and savings plan recommendations all consider on-demand VM usage). As a result, resource changes (e.g., VM shutdowns) or reservation/savings plan purchases will impact on-demand usage, and the resulting recommendations and associated savings forecast. 
+
+## Understand cost savings
+
+Azure Advisor provides recommendations for resizing/shutting down underutilized resources, purchasing compute reserved instances, and savings plans for compute.
+
+These recommendations contain one or more calls-to-action and forecasted savings from following the recommendations. Recommendations should be followed in a specific order: rightsizing/shutdown, followed by reservation purchases, and finally, the savings plan purchase. This sequence allows each step to impact the subsequent ones positively.
+
+For example, rightsizing or shutting down resources reduces on-demand costs immediately. This change in your usage pattern essentially invalidates your existing reservation and savings plan recommendations, as they were based on your pre-rightsizing usage and costs. Updated reservation and savings plan recommendations (and their forecasted savings) should appear within three days. 
 
+The forecasted savings from reservations and savings plans are based on actual rates and usage, while the forecasted savings from rightsizing/shutdown are based on retail rates. The actual savings may vary depending on the usage patterns and rates. Assuming there are no material changes to your usage patterns, your actual savings from reservations and savings plan should be in line with the forecasts. Savings from rightsizing/shutdown vary based on your actual rates. This is important if you intend to track cost savings forecasts from Azure Advisor.

articles/advisor/toc.yml

@@ -74,7 +74,7 @@
     href: advisor-azure-resource-graph.md
   - name: Consume Advisor score 
     href: azure-advisor-score.md
-  - name: Export cost savings
+  - name: Calculate total cost savings
     href: advisor-how-to-calculate-total-cost-savings.md
 - name: Reference
   items:

articles/ai-services/document-intelligence/disaster-recovery.md

@@ -8,7 +8,7 @@ ms.service: azure-ai-document-intelligence
 ms.custom:
   - ignite-2023
 ms.topic: how-to
-ms.date: 03/06/2024
+ms.date: 04/17/2024
 ms.author: lajanuar
 ---
 
@@ -65,7 +65,7 @@ The process for copying a custom model consists of the following steps:
 The following HTTP request gets copy authorization from your target resource. You need to enter the endpoint and key of your target resource as headers.
 
 ```http
-POST https://<your-resource-name>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview
+POST https://<your-resource-endpoint>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview
 Ocp-Apim-Subscription-Key: {<your-key>}
 ```
 
@@ -96,7 +96,7 @@ You receive a `200` response code with response body that contains the JSON payl
 The following HTTP request starts the copy operation on the source resource. You need to enter the endpoint and key of your source resource as the url and header. Notice that the request URL contains the model ID of the source model you want to copy.
 
 ```http
-POST https://<your-resource-name>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview
+POST https://<your-resource-endpoint>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview
 Ocp-Apim-Subscription-Key: {<your-key>}
 ```
 
@@ -117,7 +117,7 @@ You receive a `202\Accepted` response with an Operation-Location header. This va
 
 ```http
 HTTP/1.1 202 Accepted
-Operation-Location: https://<your-resource-name>.cognitiveservices.azure.com/documentintelligence/operations/{operation-id}?api-version=2024-02-29-preview
+Operation-Location: https://<your-resource-endpoint>.cognitiveservices.azure.com/documentintelligence/operations/{operation-id}?api-version=2024-02-29-preview
 ```
 
 > [!NOTE]
@@ -126,7 +126,7 @@ Operation-Location: https://<your-resource-name>.cognitiveservices.azure.com/doc
 ## Track Copy progress
 
 ```console
-GET https://<your-resource-name>.cognitiveservices.azure.com/documentintelligence/operations/{<operation-id>}?api-version=2024-02-29-preview
+GET https://<your-resource-endpoint>.cognitiveservices.azure.com/documentintelligence/operations/{<operation-id>}?api-version=2024-02-29-preview
 Ocp-Apim-Subscription-Key: {<your-key>}
 ```
 
@@ -135,7 +135,7 @@ Ocp-Apim-Subscription-Key: {<your-key>}
 You can also use the **[Get model](/rest/api/aiservices/document-models/get-model?view=rest-aiservices-2023-07-31&preserve-view=true&tabs=HTTP)** API to track the status of the operation by querying the target model. Call the API using the target model ID that you copied down from the [Generate Copy authorization request](#generate-copy-authorization-request) response.
 
 ```http
-GET https://<your-resource-name>/documentintelligence/documentModels/{modelId}?api-version=2024-02-29-preview" -H "Ocp-Apim-Subscription-Key: <your-key>
+GET https://<your-resource-endpoint>/documentintelligence/documentModels/{modelId}?api-version=2024-02-29-preview" -H "Ocp-Apim-Subscription-Key: <your-key>
 ```
 
 In the response body, you see information about the model. Check the `"status"` field for the status of the model.
@@ -155,7 +155,7 @@ The following code snippets use cURL to make API calls. You also need to fill in
 **Request**
 
 ```bash
-curl -i -X POST "<your-resource-name>/documentintelligence/documentModels:authorizeCopy?api-version=2024-02-29-preview"
+curl -i -X POST "<your-resource-endpoint>/documentintelligence/documentModels:authorizeCopy?api-version=2024-02-29-preview"
 -H "Content-Type: application/json"
 -H "Ocp-Apim-Subscription-Key: <YOUR-KEY>"
 --data-ascii "{
@@ -182,7 +182,7 @@ curl -i -X POST "<your-resource-name>/documentintelligence/documentModels:author
 **Request**
 
 ```bash
-curl -i -X POST "<your-resource-name>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview"
+curl -i -X POST "<your-resource-endpoint>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview"
 -H "Content-Type: application/json"
 -H "Ocp-Apim-Subscription-Key: <YOUR-KEY>"
 --data-ascii "{
@@ -200,7 +200,7 @@ curl -i -X POST "<your-resource-name>/documentintelligence/documentModels/{model
 
 ```http
 HTTP/1.1 202 Accepted
-Operation-Location: https://<your-resource-name>.cognitiveservices.azure.com/documentintelligence/operations/{operation-id}?api-version=2024-02-29-preview
+Operation-Location: https://<your-resource-endpoint>.cognitiveservices.azure.com/documentintelligence/operations/{operation-id}?api-version=2024-02-29-preview
 ```
 
 ### Track copy operation progress