Merge pull request #301333 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md

@@ -3,7 +3,7 @@ title: 'Invoke an App Service web app from Azure AI Foundry Agent Service'
 description: Learn how to integrate App Service with AI Foundry Agent Service and get started with agentic AI
 author: seligj95
 ms.author: jordanselig
-ms.date: 05/28/2025
+ms.date: 06/13/2025
 ms.topic: article
 ms.custom:
   - devx-track-dotnet
@@ -84,7 +84,7 @@ For detailed guidance with screenshots and additional information, see [Add Open
     </pre>
 
 1. Leave the authentication method as anonymous. There's no authentication on the web app. If the app required an API key or managed identity to access it, this location is where you would specify this information.
-1. Copy and paste the OpenAPI specification in the text box. The OpenAPI specification is provided in the Codespace in the `src/webapp` directory and is called `swagger.json`.
+1. Copy and paste the OpenAPI specification in the text box. The OpenAPI specification is provided in the Codespace in the `src/webapp` directory and is called [swagger.json](https://github.com/Azure-Samples/ai-agent-openai-web-app/blob/main/src/webapp/swagger.json).
 1. Before you complete creating the tool, you need to copy and paste your app's URL into the OpenAPI specification. Replace the placeholder `<APP-SERVICE-URL>` in line 10 of the OpenAPI specification with your app's URL. It's in the format `https://<app-name>.azurewebsites.net`.
     - To find your app's URL, go back to your resource group and navigate to your **App Service**. The URL is on the **Overview** page of your App Service.
 1. Select **Next**, review the details you provided, and then select **Create Tool**.

articles/azure-functions/functions-bindings-mcp.md

@@ -48,7 +48,7 @@ To use this experimental bundle in your app, replace the existing `extensionBund
 
 ```json
 "extensionBundle": {
-  "id": "Microsoft.Azure.Functions.ExtensionBundle.Experimental",
+  "id": "Microsoft.Azure.Functions.ExtensionBundle.Preview",
   "version": "[4.*, 5.0.0)"
 }
 ```

articles/storage/blobs/TOC.yml

@@ -513,12 +513,22 @@ items:
         href: map-rest-apis-transaction-categories.md
     - name: Estimate costs
       items:
-      - name: Estimate the cost of Azure Blob Storage
-        href: blob-storage-estimate-costs.md
-      - name: Estimate the cost of AzCopy transfers
-        href: azcopy-cost-estimation.md
-      - name: Estimate the cost to archive data
-        href: archive-cost-estimation.md
+      - name: Guides 
+        items:
+        - name: Estimate the cost of Azure Blob Storage
+          href: blob-storage-estimate-costs.md
+        - name: Estimate the cost of AzCopy transfers
+          href: azcopy-cost-estimation.md
+        - name: Estimate the cost to archive data
+          href: archive-cost-estimation.md
+      - name: Estimates
+        items:
+        - name: Rehydrate from archive by setting tiers
+          href: cost-estimate-archive-retrieval-set-tier.md
+        - name: Rehydrate from archive by copying blobs
+          href: cost-estimate-archive-retrieval-copy-blob.md
+        - name: Cross region data access
+          href: cost-estimate-multi-region-access.md
     - name: Optimize costs
       items:
       - name: Access tiers

articles/storage/blobs/archive-rehydrate-overview.md

@@ -106,9 +106,9 @@ For more information on handling events in Blob Storage, see [Reacting to Azure
 
 ## Pricing and billing
 
-A rehydration operation with [Set Blob Tier](/rest/api/storageservices/set-blob-tier) is billed for data read transactions and data retrieval size. A high-priority rehydration has higher operation and data retrieval costs compared to standard priority. High-priority rehydration shows up as a separate line item on your bill. If a high-priority request to return an archived blob that is less than 10 GB in size takes more than five hours, you won't be charged the high-priority retrieval rate. However, standard retrieval rates still apply.
+A rehydration operation with [Set Blob Tier](/rest/api/storageservices/set-blob-tier) is billed for data read transactions and data retrieval size. A high-priority rehydration has higher operation and data retrieval costs compared to standard priority. High-priority rehydration shows up as a separate line item on your bill. If a high-priority request to return an archived blob that is less than 10 GB in size takes more than five hours, you won't be charged the high-priority retrieval rate. However, standard retrieval rates still apply. For a sample cost estimate, see [Cost estimate: Move data out of archive storage](cost-estimate-archive-retrieval-set-tier.md).
 
-Copying an archived blob to an online tier with [Copy Blob](/rest/api/storageservices/copy-blob) is billed for data read transactions and data retrieval size. Creating the destination blob in an online tier is billed for data write transactions. Early deletion fees don't apply when you copy to an online blob because the source blob remains unmodified in the archive tier. High-priority retrieval charges do apply if selected.
+Copying an archived blob to an online tier with [Copy Blob](/rest/api/storageservices/copy-blob) is billed for data read transactions and data retrieval size. Creating the destination blob in an online tier is billed for data write transactions. Early deletion fees don't apply when you copy to an online blob because the source blob remains unmodified in the archive tier. High-priority retrieval charges do apply if selected. For a sample estimate, see [Cost estimate: Retrieve data from archive storage for analysis](cost-estimate-archive-retrieval-copy-blob.md).
 
 Blobs in the archive tier should be stored for a minimum of 180 days. Deleting or changing the tier of an archived blob before the 180-day period elapses incurs an early deletion fee. For example, if a blob is moved to the archive tier and then deleted or moved to the hot tier after 45 days, you'll be charged an early deletion fee equivalent to 135 (180 minus 45) days of storing that blob in the archive tier. For more information, see [Archive access tier](access-tiers-overview.md#archive-access-tier).
 

articles/storage/blobs/cost-estimate-archive-retrieval-copy-blob.md

@@ -0,0 +1,68 @@
+---
+title: 'Cost estimate: Analyze archived data (Azure Blob Storage)' 
+description: This article shows an example of what it costs to retrieve and analyze archived data in Azure Blob Storage.
+services: storage
+author: normesta
+
+ms.service: azure-blob-storage
+ms.date: 06/13/2025
+ms.topic: concept-article
+ms.author: normesta
+---
+
+# Cost estimate: Retrieve data from archive storage for analysis 
+
+This sample estimates the cost to retrieve a portion of data from the archive tier before the 180 day limit.
+
+> [!IMPORTANT]
+> This estimate is based on [these sample prices](blob-storage-estimate-costs.md#sample-prices). Sample prices shouldn't be used to calculate your production costs. To find official prices, see [Find the unit price for each meter](../common/storage-plan-manage-costs.md#find-the-unit-price-for-each-meter).
+
+## Scenario
+
+Your company stores 20 TB of data in the archive tier for long term retention. However, after only three months in archive storage, 20% of that data must be retrieved for analysis.  You're asked to estimate the cost to get that data from archive storage and then download that data to clients. 
+
+Because the data is needed only temporarily, you decide not to rehydrate blobs by changing their tier. That way, your company avoids the early deletion fee. You already estimated the cost of that approach by reviewing the [Cost estimate: Move data out of archive storage](cost-estimate-archive-retrieval-set-tier.md) article. Instead, you decide that it's more cost-effective to copy blobs into the hot tier for analysis. You know that data in the hot tier can be deleted at no charge when the analysis is complete. 
+
+The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and doesn't have hierarchical namespaces.
+
+## Costs
+
+The following table describes each cost.
+
+| Cost | Description |
+|----|----|
+| **Copy blobs to the hot tier** | First, blobs must be moved out of archive storage for analysis. All tools and SDKs use the [Copy Blob](/rest/api/storageservices/copy-blob) operation to accomplish this task. The [Copy Blob](/rest/api/storageservices/copy-blob) operation is billed as a read operation on the source account and a write operation on the destination account. |
+| **Data retrieval fee** | This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
+| **Read from the hot tier** | Once data is moved into the hot tier, clients need to download that data. Each download is billed as a read operation. |
+
+## Estimate
+
+Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), the following table shows how each cost component is calculated. This sample estimate doesn't include the [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB.
+
+| Cost                           | Cost factor                                | Calculation                           | Value       |
+|--------------------------------|--------------------------------------------|---------------------------------------|-------------|
+| **Copy blobs to the hot tier** | Number of Copy Blob operations             | 2000 blobs * 20%                      | 400         |
+|                                | Price of an archive read operation         |                                       | $0.00055    |
+|                                | Cost to read from the archive              | 400 operations * $0.00055             | $0.22       |
+|                                | Price of a hot tier write operation        |                                       | $0.0000055  |
+|                                | Cost to write to the hot tier              | 400 operations * $0.0000055           | $0.0022     |
+|                                | **Cost to copy blobs to hot tier**<br><br> | $0.22 + $0.0022                       | **$0.22**   |
+| **Data retrieval fee**         | Total file size                            |                                       | 20,000 GB   |
+|                                | Data retrieval size                        | 20,000 GB * 20%                       | 4,000       |
+|                                | Price of data retrieval (per GB)           |                                       | $0.0220     |
+|                                | **Cost to retrieve**<br></br>              | 4,000 blobs * $0.0220                 | **$88.00**  |
+| **Read from hot tier**         | Number of read operations on hot tier      | The number of blobs moved to hot tier | 400         |
+|                                | Price of a read operation on the hot tier  |                                       | $0.00000044 |
+|                                | **Cost to read from hot tier**<br></br>    | 400 operations * $0.00000044          | **$0.0002** |
+| **Total cost**                 |                                            | $0.22 + $88 + $24 + $0.0002           | **$88.22**  |
+
+> [!TIP]
+> This scenario doesn't model the amount of time that data exists in the storage, so the table doesn't include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
+
+## See also
+
+- [Cost estimate: Move data out of archive storage](cost-estimate-archive-retrieval-set-tier.md)
+- [Estimate the cost of archiving data](archive-cost-estimation.md)
+- [Estimate the cost of using Azure Blob Storage](blob-storage-estimate-costs.md)
+- [Estimate the cost of using AzCopy to transfer blobs](azcopy-cost-estimation.md)
+- [Plan and manage costs for Azure Blob Storage](../common/storage-plan-manage-costs.md)

articles/storage/blobs/cost-estimate-archive-retrieval-set-tier.md

@@ -0,0 +1,63 @@
+---
+title: 'Cost estimate: Move data from archive (Azure Blob Storage)' 
+description: This article shows an example of what it costs to move data out of archive storage.
+services: storage
+author: normesta
+
+ms.service: azure-blob-storage
+ms.date: 06/13/2025
+ms.topic: concept-article
+ms.author: normesta
+---
+
+# Cost estimate: Move data out of archive storage 
+
+This sample estimates the cost to move a portion of data from the archive tier to the hot tier before the 180 day limit.
+
+> [!IMPORTANT]
+> This estimate is based on [these sample prices](blob-storage-estimate-costs.md#sample-prices). Sample prices shouldn't be used to calculate your production costs. To find official prices, see [Find the unit price for each meter](../common/storage-plan-manage-costs.md#find-the-unit-price-for-each-meter).
+
+## Scenario
+
+Your company stores 20 TB of data in the archive tier for long term retention. However, after only three months in archive storage, 20% of that data must be moved back to the hot tier. You are asked to estimate the cost to get that data from archive storage.
+
+The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and doesn't have hierarchical namespaces.
+
+## Costs
+
+The following table describes each cost.
+
+| Cost | Description |
+|----|----|
+| **Change tier to hot** | First, blobs must be moved out of archive storage. To do this, administrators change the tier of each blob from `archive` to `hot`. All tools and SDKs use the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation to accomplish this task. That operation is billed as a read operation on the archive tier. |
+| **Data retrieval fee** | This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
+| **Early deletion fee** | If data is moved out of the archive tier before 180 days have transpired, a prorated early deletion fee is applied to the bill. |
+
+## Estimate
+
+Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), the following table shows how each cost component is calculated. 
+
+| Cost                   | Cost factor                                 | Calculation                    | Value       |
+|------------------------|---------------------------------------------|--------------------------------|-------------|
+| **Change tier to hot** | Number of Set Blob Tier operations          | 2000 blobs * 20%               | 400         |
+|                        | Price of an archive read operation          |                                | $0.00055    |
+|                        | **Cost to change tier to hot**<br></br>     | 400 operations * $0.00055      | **$0.22**   |
+| **Data retrieval fee** | Total file size                             |                                | 20,000 GB   |
+|                        | Data retrieval size                         | 20,000 GB * 20%                | 4,000       |
+|                        | Price of data retrieval (per GB)            |                                | $0.0220     |
+|                        | **Cost to retrieve**<br></br>               | 4,000 blobs * $0.0220          | **$88.00**  |
+| **Early deletion fee** | Rough number of months penalty              | (180 days - 90 days) / 30 days | 3           |
+|                        | Price per month of archive storage (per GB) |                                | $0.0020     |
+|                        | **Cost of early deletion**<br></br>         | (4,000 blobs * $0.0020) * 3     | **$24.00**  |
+| **Total cost**         |                                             | $0.22 + $88 + $24              | **$112.22** |
+
+> [!TIP]
+> This scenario doesn't model the amount of time that data exists in storage, so the table doesn't include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
+
+## See also
+
+- [Cost estimate: Retrieve data from archive storage for analysis](cost-estimate-archive-retrieval-copy-blob.md)
+- [Estimate the cost of archiving data](archive-cost-estimation.md)
+- [Estimate the cost of using Azure Blob Storage](blob-storage-estimate-costs.md)
+- [Estimate the cost of using AzCopy to transfer blobs](azcopy-cost-estimation.md)
+- [Plan and manage costs for Azure Blob Storage](../common/storage-plan-manage-costs.md)