Merge pull request #300316 from MicrosoftDocs/main

5/23/2025 AM Publish

Author: Taojunshen

articles/api-management/export-rest-mcp-server.md

@@ -18,7 +18,7 @@ In API Management, you can expose a REST API managed in API Management as a remo
 Using API Management to expose remote MCP servers provides centralized control over authentication, authorization, and monitoring. It simplifies the process of exposing APIs as MCP servers while helping to mitigate common security risks and ensuring scalability.
 
 > [!NOTE]
-> This feature is currently in preview. It's being released first to the **AI Gateway Early** [update group](configure-service-update-settings.md).
+> This feature is currently in preview. It's being released first to the **AI Gateway Early** [update group](configure-service-update-settings.md). After joining the group, it can take 2 hours to access MCP server features.
 
 In this article, you learn how to:
 

articles/azure-vmware/azure-vmware-solution-platform-updates.md

@@ -4,7 +4,7 @@ description: Learn about the platform updates to Azure VMware Solution.
 ms.topic: reference
 ms.custom: "references_regions, engagement-fy23"
 ms.service: azure-vmware
-ms.date: 5/7/2025
+ms.date: 5/23/2025
 ---
 
 # What's new in Azure VMware Solution
@@ -24,7 +24,7 @@ Azure VMware Solution AV48 node size is now available in the Japan East region.
 
 **Azure Native Pure Storage Cloud (preview)**
 
-Azure Native Pure Storage Cloud for Azure VMware Solution is now in public preview. You can now use Azure Native Pure Storage Cloud from Pure Storage to deploy vVols-based block storage for AVS, enabling you to scale storage independently for your virtual workloads. [Learn more](configure-azure-native-pure-storage-cloud.md)
+Azure Native Pure Storage Cloud for Azure VMware Solution is now in public preview. You can now use Azure Native Pure Storage Cloud from Pure Storage to deploy vVols-based block storage for Azure VMware Solution, enabling you to scale storage independently for your virtual workloads. [Learn more](configure-azure-native-pure-storage-cloud.md)
 
 **Azure VMware Solution Generation 2 Private Clouds (preview)**
 

articles/communication-services/concepts/analytics/insights/voice-and-video-insights.md

@@ -135,6 +135,12 @@ And can also be filtered by endpoint types (**Endpoint Type** parameter), for ex
 
 <!-- :::image type="content" source="..\media\workbooks\voice-and-video-params-2.png" alt-text="Screenshot voice and video quality endpoint type parameter."::: -->
 
+## Performance
+
+The Performance tab provides a summary of decile-level performance for key Calling SDK APIs, helping you identify areas with the highest latency. By default, the dashboard displays a P95 latency trend, offering a high-level view of latency over time.
+
+To explore further, you can select a specific API scenario. When a scenario is selected, the dashboard updates to show a detailed breakdown of that API’s performance, enabling deeper analysis and troubleshooting.
+
 ## More information about workbooks
 
 For an in-depth description of workbooks, refer to the [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview) documentation.

articles/container-apps/dapr-overview.md

@@ -6,13 +6,16 @@ author: hhunter-ms
 ms.service: azure-container-apps
 ms.custom: build-2023
 ms.topic: conceptual
-ms.date: 04/09/2025
+ms.date: 05/21/2025
 ---
 
 # Microservice APIs powered by Dapr
 
 Azure Container Apps provides APIs powered by [Distributed Application Runtime (Dapr)][dapr-concepts] that help you write and implement simple, portable, resilient, and secured microservices. Dapr works together with Azure Container Apps as an abstraction layer to provide a low-maintenance and scalable platform. Azure Container Apps offers a selection of fully managed Dapr APIs, components, and features, catered specifically to microservice scenarios. Simply [enable and configure Dapr][dapr-enable] as usual in your container app environment.
 
+> [!NOTE]
+> Find updates and release announcements for Dapr in Azure Container Apps [in GitHub](https://aka.ms/dapr-aca-updates). 
+
 ## How the microservices APIs work with your container app
 
 Configure microservices APIs for your container apps environment with a [Dapr-enabled container app][dapr-enable], a [Dapr component configured for your solution][dapr-components], and a Dapr sidecar invoking communication between them. The following diagram demonstrates these core concepts, using the pub/sub API as an example.

articles/container-apps/faq.yml

@@ -117,6 +117,8 @@ sections:
 
           Since Dapr version updates are applied automatically, you always benefit from the most secure version. However, Dapr in Azure Container Apps doesn't follow a fixed release schedule for new features. Instead, the release of new Dapr versions for new functionality depends on the prioritization and stability of the Dapr binaries.
 
+          Find updates and release announcments for Dapr in Azure Container Apps in [GitHub](https://aka.ms/dapr-aca-updates).
+
       - question: |
           Can I use a specific Dapr version for my environment?
         answer:

articles/container-apps/whats-new.md

@@ -8,7 +8,7 @@ ms.service: azure-container-apps
 ms.custom:
   - ignite-2023
 ms.topic: conceptual
-ms.date: 08/30/2023
+ms.date: 05/22/2025
 # Customer Intent: As an Azure Container Apps user, I'd like to know about new and improved features in Azure Container Apps.
 ---
 
@@ -18,7 +18,7 @@ This article lists significant updates and new features available in Azure Conta
 
 ## November 2024 and beyond
 
-Azure Container Apps updates can be found in [GitHub](https://aka.ms/aca/updates) now.
+You can now find updates and release announcements for [Azure Container Apps](https://aka.ms/aca/updates) and [Dapr in Azure Container Apps](https://aka.ms/dapr-aca-updates) in GitHub.
 
 ## May 2024 
 

articles/iot-hub-device-update/support.md

@@ -46,25 +46,27 @@ The systems listed in the following tables are supported by Microsoft, either ge
 
 Device Update for IoT Hub release assets and release notes are available on the [Device Update Release](https://github.com/Azure/iot-hub-device-update/releases) page. Support for the APIs, PnP Models, and device update reference agents is covered in the table. 
 
-Device Update for IoT Hub 1.0 is the first major release and will continue to receive security fixes and fixes to regressions.  
+Device Update for IoT Hub 1.0 is the first major release and continues to receive security fixes and fixes to regressions.  
 
 Device Update (DU) agents use IoT Plug and Play models to send and receive properties and messages from the DU service. Each DU agent requires specific models to be used. Learn more about how device update uses these models and how they can be extended.  
 
 Newer REST Service API versions support older agents unless specified. Device Update for IoT Hub portal experience uses the latest APIs and have the same support as the API version. 
 
 | Release notes and assets | deviceupdate-agent | Upgrade Supported from agent version | DU PnP Models supported | API Versions|
 | ------------------------ | ------------------ | ------------------------------------ | ----------------------- |-------------|
-| 1.0.0 | 1.0.0 <br /> 1.0.1 <br /> 1.0.2 | 0.8.x | dtmi:azure:iot:deviceUpdateContractModel;2 <br /> dtmi:azure:iot:deviceUpdateModel;2  | 2022-10-01 |
-|0.0.8 (Preview)(Deprecated) | 0.8.0 <br /> 0.8.1 <br /> 0.8.2 |  | dtmi:azure:iot:deviceUpdateContractModel;1 <br /> dtmi:azure:iot:deviceUpdateModel;1 | 2022-10-01 <br /> 2021-06-01-preview (Deprecated)|
+| 1.2.0 | 1.2.0 <br /> | 1.1.0 | dtmi:azure:iot:deviceUpdateContractModel; 3 <br /> dtmi:azure:iot:deviceUpdateModel; 3  | 2022-10-01 |
+| 1.1.0 | 1.1.0|1.0.x | dtmi:azure:iot:deviceUpdateContractModel; 3 <br /> dtmi:azure:iot:deviceUpdateModel; 3| 2022-10-01 |
+| 1.0.0 | 1.0.0 <br /> 1.0.1 <br /> 1.0.2 | 0.8.x | dtmi:azure:iot:deviceUpdateContractModel; 2 <br /> dtmi:azure:iot:deviceUpdateModel; 2  | 2022-10-01 |
+|0.0.8 (Preview)(Deprecated) | 0.8.0 <br /> 0.8.1 <br /> 0.8.2 |  | dtmi:azure:iot:deviceUpdateContractModel; 1 <br /> dtmi:azure:iot:deviceUpdateModel; 1 | 2022-10-01 <br /> 2021-06-01-preview (Deprecated)|
 
-The latest API version, 2022-10-01 will be supported until the next stable release and the latest agent version, 1.0.x, will receive bug fixes and security fixes until the next stable release. 
+The latest API version, 2022-10-01 will be supported until the next stable release and the latest agent version, 1.x.x, will receive bug fixes and security fixes until the next stable release. 
 
 > [!NOTE]
-> Users, that have extended from the reference agent and customized the agent, are responsible for ensuring the bug fixes and security fixes are incorporated. You will also need to ensure the agent is built and configured correctly as defined by the service to connect service, perform updates, and manage devices from the IoT hub. 
+> Users that have extended from the reference agent and customized the agent are responsible for ensuring the bug fixes and security fixes are incorporated. You will also need to ensure the agent is built and configured correctly as defined by the service to connect service, perform updates, and manage devices from the IoT hub. 
 
 > [!IMPORTANT]
 > Every Microsoft product has a lifecycle. The lifecycle begins when a product is released and ends when it's no longer supported. Knowing key dates in this lifecycle helps you make informed decisions about when to upgrade or make other changes to your software.  
-> For Device Update for IoT Hub, no stable API or agent version will be deprecated without a replacing version. Deprecated stable versions will be available for no less than 3 years after deprecation is announced to allow users to migrate to in-support agent and API versions. 
-> Preview releases (Pre-releases) agents and APIs are not serviced after the release of the stable version. Preview versions are released to test new functionality, gather feedback, and discover and fix issues. Previews are available under Supplemental Terms of Use, and aren't recommended for production workloads. 
-> 0.7.0 (Pre-release) is not supported by the latest service and API versions.  
+> For Device Update for IoT Hub, no stable API or agent version will be deprecated without a replacing version. Deprecated stable versions will be available for no less than three years after deprecation is announced to allow users to migrate to in-support agent and API versions. 
+> Preview releases (Prereleases) agents and APIs are not serviced after the release of the stable version. Preview versions are released to test new functionality, gather feedback, and discover and fix issues. Previews are available under Supplemental Terms of Use, and aren't recommended for production workloads. 
+> 0.7.0 (Prerelease) is not supported by the latest service and API versions.  
 > With the latest stable release, we recommend that all current customers running 0.x.x upgrade their devices to 1.0.x to receive ongoing support. 

articles/planetary-computer/api-tutorial.md

@@ -440,8 +440,8 @@ for item in items:
         params={"api-version": api_version}
     )
 
-    operation_ids.append(response.json()["operationId"])
-    print(f"Ingesting item {item_json['id']} with operation id {response.json()['operationId']}")
+    operation_ids.append(response.json()['id'])
+    print(f"Ingesting item {item_json['id']} with operation id {response.json()['id']}")
 
 ```
 

articles/storage/files/understanding-billing.md

@@ -166,6 +166,8 @@ Currently, these SKUs are generally available in a limited subset of regions:
 - Norway East
 - Norway West
 - Israel Central
+- Qatar Central
+- Mexico Central
 
 ### Provisioned v2 provisioning detail
 When you create a provisioned v2 file share, you specify the provisioned capacity for the file share in terms of storage, IOPS, and throughput. File shares are limited based on the following attributes:

articles/virtual-desktop/session-host-update-configure.md

@@ -219,7 +219,7 @@ You can update the session host management policy before you schedule an update,
    Get-AzWvdSessionHostConfiguration @parameters | FL *
    ```
 
-3. *Optional*: If you want to update the session host management policy before scheduling an update, run the following command, using the `Update-AzWvdSessionHostManagement` cmdlet. Alternatively, you can override specific values when scheduling an update, which are used for that update only. For valid time zone values, see [Get-TimeZone PowerShell reference](/powershell/module/microsoft.powershell.management/get-timezone) and use the value from the `StandardName` property.
+3. *Optional*: If you want to update the session host management policy before scheduling an update, run the following command, using the `Update-AzWvdSessionHostManagement` cmdlet. Alternatively, you can override specific values when scheduling an update, which are used for that update only. For valid time zone values, see [Get-TimeZone PowerShell reference](/powershell/module/microsoft.powershell.management/get-timezone) and use the value from the `StandardName` property. We recommend setting `UpdateDeleteOriginalVM = $true` so that you don't need to clean up session host resources after an update.
 
    ```azurepowershell
    $parameters = @{