updates to release branch

Author: mbender-ms

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/application-gateway/ingress-controller-annotations.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 9/17/2024
+ms.date: 5/23/2025
 ms.author: mbender
 ---
 
@@ -66,7 +66,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-bkprefix
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/backend-path-prefix: "/test/"
@@ -104,7 +103,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-timeout
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/backend-hostname: "internal.example.com"
@@ -152,7 +150,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/health-probe-hostname: "contoso.com"
@@ -192,7 +189,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-redirect
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/ssl-redirect: "true"
@@ -233,7 +229,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-drain
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/connection-draining: "true"
@@ -268,7 +263,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-affinity
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/cookie-based-affinity: "true"
@@ -302,7 +296,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-timeout
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/request-timeout: "20"
@@ -338,7 +331,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-privateip
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/use-private-ip: "true"
@@ -375,7 +367,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-overridefrontendport
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/override-frontend-port: "8080"
@@ -416,7 +407,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-timeout
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/backend-protocol: "https"
@@ -450,7 +440,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-multisite
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/hostname-extension: "hostname1, hostname2"
@@ -488,7 +477,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: ad-server-ingress
-  namespace: commerce
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/waf-policy-for-path: "/subscriptions/abcd/resourceGroups/rg/providers/Microsoft.Network/applicationGatewayWebApplicationFirewallPolicies/adserver"
@@ -532,7 +520,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-certificate
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/appgw-ssl-certificate: "name-of-appgw-installed-certificate"
@@ -567,7 +554,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-certificate
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/appgw-ssl-certificate: "name-of-appgw-installed-certificate"
@@ -602,7 +588,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-certificate
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/backend-protocol: "https"
@@ -636,7 +621,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-bkprefix
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/rewrite-rule-set: add-custom-response-header
@@ -727,7 +711,6 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: go-server-ingress-rulepriority
-  namespace: test-ag
   annotations:
     kubernetes.io/ingress.class: azure/application-gateway
     appgw.ingress.kubernetes.io/rule-priority: 10

articles/azure-app-configuration/configuration-provider-overview.md

@@ -55,15 +55,16 @@ Configuration Setting Mapping | [GA](./reference-dotnet-provider.md#configuratio
 Key Vault References | [GA](./reference-dotnet-provider.md#key-vault-reference) | GA | GA | GA | [GA](./reference-javascript-provider.md#key-vault-reference)
 Key Vault Secret Refresh | [GA](./reference-dotnet-provider.md#key-vault-secret-refresh) | WIP | GA | WIP | WIP
 Custom Key Vault Secret Resolution | [GA](./reference-dotnet-provider.md#key-vault-reference) | GA | GA | GA | [GA](./reference-javascript-provider.md#key-vault-reference)
+Parallel Secret Resolution | WIP | WIP | WIP | WIP | [GA](./reference-javascript-provider.md#parallel-secret-resolution)
 Feature Flags | [GA](./reference-dotnet-provider.md#feature-flag) | GA | GA | GA | [GA](./reference-javascript-provider.md#feature-flag)
 Variant Feature Flags | [GA](./reference-dotnet-provider.md#feature-flag) | GA | GA | GA | [GA](./reference-javascript-provider.md#feature-flag)
 Feature Flag Telemetry | GA | GA | WIP | GA | GA
 Key Prefix Trim | [GA](./reference-dotnet-provider.md#trim-prefix-from-keys) | GA | GA | GA | [GA](./reference-javascript-provider.md#trim-prefix-from-keys)
-Configurable Startup Time-out | [GA](./reference-dotnet-provider.md#startup-retry) | WIP | N/A | WIP | WIP
+Configurable Startup Time-out | [GA](./reference-dotnet-provider.md#startup-retry) | WIP | N/A | WIP | [GA](./reference-javascript-provider.md#startup-retry)
 Replica Auto Discovery | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | WIP | [GA](./reference-javascript-provider.md#geo-replication)
 Replica Failover | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | WIP | [GA](./reference-javascript-provider.md#geo-replication)
 Replica Load Balancing | [GA](./reference-dotnet-provider.md#geo-replication) | WIP | GA | WIP | [GA](./reference-javascript-provider.md#geo-replication)
-Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | WIP | WIP
+Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | WIP | [GA](./reference-javascript-provider.md#snapshot)
 Distributed tracing | [GA](./reference-dotnet-provider.md#distributed-tracing) | WIP | WIP | WIP | WIP
 Health Check | WIP | WIP | WIP | WIP | WIP
 

articles/azure-app-configuration/reference-javascript-provider.md

@@ -9,7 +9,7 @@ ms.service: azure-app-configuration
 ms.devlang: javascript
 ms.custom: devx-track-javascript
 ms.topic: tutorial
-ms.date: 02/02/2025
+ms.date: 05/22/2025
 #Customer intent: I want to learn how to use Azure App Configuration JavaScript client library.
 ---
 
@@ -355,6 +355,79 @@ const appConfig = await load(endpoint, credential, {
 });
 ```
 
+You can also set `clientOptions` property to configure `SecretClientOptions` used to connect to Azure Key Vault that has no registered `SecretClient`.
+
+```typescript
+const credential = new DefaultAzureCredential();
+const appConfig = await load(endpoint, credential, {
+    keyVaultOptions: {
+        credential: credential,
+        clientOptions: { // configure a custom SecretClientOptions
+            retryOptions: { 
+                maxRetries: 3, 
+                maxRetryDelayInMs: 1000 
+            }
+        }
+    }
+});
+```
+
+### Parallel secret resolution
+
+Azure Key Vault doesn't provide a batch API for retrieving multiple secrets in a single request. When your application needs to load numerous Key Vault references, you can improve performance by enabling parallel secret resolution using the `parallelSecretResolutionEnabled` property in `KeyVaultOptions`. This allows the provider to fetch multiple secrets in parallel rather than sequentially:
+
+
+```typescript
+const credential = new DefaultAzureCredential();
+const appConfig = await load(endpoint, credential, {
+    keyVaultOptions: {
+        credential: credential,
+        parallelSecretResolutionEnabled: true
+    }
+});
+```
+
+> [!NOTE]
+> When resolving secret in parallel, you may encounter the [service limit](/azure/key-vault/general/service-limits#secrets-managed-storage-account-keys-and-vault-transactions) of Azure Key Vault.
+> To handle throttling effectively, implement the [client-side throttling best practices](/azure/key-vault/general/overview-throttling#how-to-throttle-your-app-in-response-to-service-limits) by configuring appropriate retry options for the `SecretClient`. You can either register custom `SecretClient` instances or configure `clientOptions` via the `AzureAppConfigurationOptions.keyVaultOptions`.
+
+
+## Snapshot
+
+[Snapshot](./concept-snapshots.md) is a named, immutable subset of an App Configuration store's key-values. The key-values that make up a snapshot are chosen during creation time through the usage of key and label filters. Once a snapshot is created, the key-values within are guaranteed to remain unchanged.
+
+You can use snapshot selector to load key-values or feature flags from a snapshot:
+
+```typescript
+const appConfig = await load(endpoint, credential, {
+    selectors: [
+        { snapshotName: "MySnapshot" }, // load key-values from snapshot
+        { keyFilter: "test*", labelFilter: "test" }
+    ],
+    featureFlagOptions: {
+        enabled: true,
+        selectors: [
+            { snapshotName: "MySnapshot" }, // load feature flags from snapshot
+            { keyFilter: "*", labelFilter: "test" }
+        ]
+    }
+});
+```
+
+## Startup retry
+
+Configuration loading is a critical path operation during application startup. To ensure reliability, the Azure App Configuration provider implements a robust retry mechanism during the initial configuration load. This helps protect your application from transient network issues that might otherwise prevent successful startup.
+
+You can customize this behavior via the `AzureAppConfigurationOptions.startupOptions`:
+
+```typescript
+const appConfig = await load(endpoint, credential, { 
+    startupOptions: { 
+        timeoutInMs: 300_000
+    }
+});
+```
+
 ## Geo-replication
 
 For information about using geo-replication, go to [Enable geo-replication](./howto-geo-replication.md).

articles/azure-cache-for-redis/quickstart-create-redis.md

@@ -1,5 +1,5 @@
 ---
-title: 'Quickstart: Create an Azure Redis cache'
+title: 'Quickstart: Create an Azure Cache for Redis instance'
 description: Learn how to create an instance of Azure Cache for Redis in Basic, Standard, or Premium tiers.
 
 
@@ -11,7 +11,7 @@ appliesto:
   - ✅ Azure Cache for Redis
 
 ---
-# Quickstart: Create an Azure Redis cache
+# Quickstart: Create an Azure Cache for Redis instance
 
 Azure Cache for Redis provides a fully managed [open-source Redis](https://redis.io/) cache within Azure. You can start with a Basic, Standard, or Premium tier cache of any size, and scale it to meet your application's performance needs. This quickstart demonstrates how to use the Azure portal to create a new Azure Cache for Redis instance.
 

articles/azure-functions/configure-monitoring.md

@@ -3,7 +3,7 @@ title: Configure monitoring for Azure Functions
 description: Learn how to connect your function app to Application Insights for monitoring and how to configure data collection.
 ms.service: azure-functions
 ms.topic: how-to
-ms.date: 08/06/2024
+ms.date: 05/19/2025
 ms.custom: devdivchpfy22
 
 # Customer intent: As a developer, I want to understand how to configure monitoring for my functions correctly, so I can collect the data that I need.
@@ -297,7 +297,9 @@ When you create your function app in the [Azure portal](./functions-get-started.
 You can use the [`APPLICATIONINSIGHTS_AUTHENTICATION_STRING`](./functions-app-settings.md#applicationinsights_authentication_string) setting to enable connections to Application Insights using Microsoft Entra authentication. This creates a consistent authentication experience across all Application Insights pipelines, including Profiler and Snapshot Debugger, as well as from the Functions host and language-specific agents.  
 
 >[!NOTE]  
->There's no Entra authentication support for local development.
+>There's currently no Microsoft Entra ID authentication support for local development.
+>
+>When Ingesting data in a sovereign cloud, Microsoft Entra ID authentication isn't available when using the Application Insights SDK.  OpenTelemetry-based data collection supports Microsoft Entra ID authentication across all cloud environments, including sovereign clouds.
 
 The value contains either `Authorization=AAD` for a system-assigned managed identity or `ClientId=<YOUR_CLIENT_ID>;Authorization=AAD` for a user-assigned managed identity. The managed identity must already be available to the function app, with an assigned role equivalent to [Monitoring Metrics Publisher](/azure/role-based-access-control/built-in-roles/monitor#monitoring-metrics-publisher). For more information, see [Microsoft Entra authentication for Application Insights](/azure/azure-monitor/app/azure-ad-authentication).
 

articles/azure-functions/dotnet-isolated-process-guide.md

@@ -3,7 +3,7 @@ title: Guide for running C# Azure Functions in an isolated worker process
 description: Learn how to use the .NET isolated worker model to run your C# functions in Azure, which lets you run your functions on currently supported versions of .NET and .NET Framework.
 ms.service: azure-functions
 ms.topic: conceptual
-ms.date: 09/05/2024
+ms.date: 05/19/2025
 ms.custom:
   - template-concept
   - devx-track-dotnet
@@ -128,8 +128,7 @@ var builder = FunctionsApplication.CreateBuilder(args);
 
 builder.Services
     .AddApplicationInsightsTelemetryWorkerService()
-    .ConfigureFunctionsApplicationInsights()
-    .AddSingleton<IHttpResponderService, DefaultHttpResponderService>();
+    .ConfigureFunctionsApplicationInsights();
 
 builder.Logging.Services.Configure<LoggerFilterOptions>(options =>
     {

articles/azure-functions/functions-bindings-http-webhook-trigger.md

@@ -2,7 +2,7 @@
 title: Azure Functions HTTP trigger
 description: Learn how to call an Azure Function via HTTP.
 ms.topic: reference
-ms.date: 07/16/2024
+ms.date: 05/02/2025
 ms.devlang: csharp
 # ms.devlang: csharp, java, javascript, powershell, python
 ms.custom: devx-track-csharp, devx-track-python, devx-track-extended-java, devx-track-js, devx-track-ts
@@ -286,7 +286,7 @@ public HttpResponseMessage run(
 
 # [Model v4](#tab/nodejs-v4)
 
-The following example shows an HTTP trigger [TypeScript function](functions-reference-node.md?tabs=typescript). The function looks for a `name` parameter either in the query string or the body of the HTTP request.
+The following example shows an HTTP trigger [TypeScript function](functions-reference-node.md?tabs=typescript). The function looks for a `name` parameter either in the query string or the body of the [HTTP request](functions-reference-node.md?tabs=typescript&pivots=nodejs-model-v4#http-request). 
 
 :::code language="typescript" source="~/azure-functions-nodejs-v4/ts/src/functions/httpTrigger1.ts" :::
 
@@ -301,13 +301,13 @@ TypeScript samples aren't documented for model v3.
 
 # [Model v4](#tab/nodejs-v4)
 
-The following example shows an HTTP trigger [JavaScript function](functions-reference-node.md). The function looks for a `name` parameter either in the query string or the body of the HTTP request.
+The following example shows an HTTP trigger [JavaScript function](functions-reference-node.md). The function looks for a `name` parameter either in the query string or the body of the [HTTP request](functions-reference-node.md?tabs=javascript&pivots=nodejs-model-v4#http-request). 
 
 :::code language="javascript" source="~/azure-functions-nodejs-v4/js/src/functions/httpTrigger1.js" :::
 
 # [Model v3](#tab/nodejs-v3)
 
-The following example shows a trigger binding in a *function.json* file and a [JavaScript function](functions-reference-node.md) that uses the binding. The function looks for a `name` parameter either in the query string or the body of the HTTP request.
+The following example shows a trigger binding in a *function.json* file and a [JavaScript function](functions-reference-node.md) that uses the binding. The function looks for a `name` parameter either in the query string or the body of the [HTTP request](functions-reference-node.md?tabs=javascript&pivots=nodejs-model-v3#http-request). 
 
 Here's the *function.json* file:
 

articles/azure-functions/functions-how-to-use-azure-function-app-settings.md

@@ -3,7 +3,7 @@ title: Configure function app settings in Azure Functions
 description: Learn how to configure function app settings in Azure Functions.
 ms.service: azure-functions
 ms.topic: how-to
-ms.date: 11/11/2024
+ms.date: 05/21/2025
 ms.custom: cc996988-fb4f-47, devx-track-azurecli, devx-track-azurepowershell, ignite-2024
 ms.assetid: 81eb04f8-9a27-45bb-bf24-9ab6c30d205c
 ---
@@ -211,17 +211,21 @@ Choose the direction of the migration for your app on Windows.
 
 ### [Consumption-to-Premium](#tab/to-premium/azure-portal)
 
-1. In the Azure portal, navigate to your Consumption plan app and choose **Change App Service plan** under **App Service plan**.
+1. In the Azure portal, navigate to your Consumption plan app, and in the left pane expand **App Service plan** and select **App Service plan**.
 
-1. Select **Premium** under **Plan type**, create a new Premium plan, and select **OK**.
+1. In the **App Service plan** page, select **Change plan** under **Current App Service plan**. 
+
+1. In **Change App Service plan**, select **Premium** for **Plan type**, create a new Premium plan, and select **OK**.
 
 For more information, see [Move an app to another App Service plan](../app-service/app-service-plan-manage.md#move-an-app-to-another-app-service-plan).
 
 ### [Premium-to-Consumption](#tab/to-consumption/azure-portal)
 
-1. In the Azure portal, navigate to your Premium plan app and choose **Change App Service plan** under **App Service plan**.
+1. In the Azure portal, navigate to your Elastic Premium plan app, and in the left pane expand **App Service plan** and select **App Service plan**.
+
+1. In the **App Service plan** page, select **Change plan** under **Current App Service plan**. 
 
-1. Select **Consumption** under **Plan type**, create a new Consumption plan, and select **OK**.
+1. In **Change App Service plan**, select **Consumption** under **Plan type**, create a new Consumption plan, and select **OK**.
 
 For more information, see [Move an app to another App Service plan](../app-service/app-service-plan-manage.md#move-an-app-to-another-app-service-plan).