Merge pull request #314228 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-03 17:00 UTC

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

articles/app-service/manage-backup.md

@@ -120,6 +120,9 @@ There are two types of backups in App Service. If your app is in a supported pri
 1. At the top of the **Backups** page, select **Configure custom backups**.
 
 1. In **Storage account**, select an existing storage account in the same subscription or select **Create new**. Repeat in **Container**.
+    > [!NOTE]
+    > Custom backups for Azure App Service require an Azure Storage account that supports Shared Access Signature (SAS)–based authorization. Managed Identity–based authentication to the storage account isn't supported for App Service backup and restore operations.
+   
 
     To back up the linked databases, select **Next: Advanced** > **Include database**, and select the databases to backup.
 

articles/azure-resource-manager/management/request-limits-and-throttling.md

@@ -18,7 +18,7 @@ The token bucket represents the maximum number of requests that you can send for
 
 These updated limits make it easier for you to refresh and manage your quota.
 
-The updated limits are:
+The updated limits for public and sovereign clouds are:
 
 | Scope | Operations | Bucket size | Refill rate per sec |
 | ----- | ---------- | ----------- | ------------------- |
@@ -37,8 +37,6 @@ For example, suppose you have a bucket size of 250 tokens for read requests and
 
 Reading metrics using the `*/providers/microsoft.insights/metrics` API contributes significantly to overall Azure Resource Manager traffic and is a common cause of subscription throttling events. If you use this API heavily, we recommend that you switch to the `getBatch` API. You can query multiple resources in a single REST request, which improves performance and reduces throttling. For more information about converting your operations, see [How to migrate from the metrics API to the getBatch API](/azure/azure-monitor/essentials/migrate-to-batch-api).
 
-These limits and architecture will also apply to all sovereign clouds by the end of 2026.
-
 ### How can I view my throttled requests?
 
 To view your throttled requests and other Resource Manager metrics, see [Accessing Azure Resource Manager metrics](/azure/azure-resource-manager/management/monitor-resource-manager#accessing-azure-resource-manager-metrics).
@@ -63,39 +61,6 @@ The request for subscription '{0}' could not be processed due to an excessive vo
 
 Customers might experience throttling due to excessive background jobs, which can be triggered by high-frequency operations or system-wide activities. While customers do not have direct control over the creation or execution of these jobs, awareness of potential throttling is important.
 
-## Throttling for sovereign clouds
-
-Throttling happens at two levels. Azure Resource Manager throttles requests for the subscription and tenant. If the request is under the throttling limits for the subscription and tenant, Resource Manager routes the request to the resource provider. The resource provider applies throttling limits that are tailored to its operations.
-
-Requests are initially throttled per principal ID and per Azure Resource Manager instance in the region of the user sending the request. Requests to the Azure Resource Manager instance in the region are also throttled per principal user ID and per hour. When the request is forwarded to the resource provider, requests are throttled per region of the resource rather than per Azure Resource Manager instance in region of the user. 
-
-> [!NOTE]
-> The limits of a resource provider can differ from the limits of the Azure Resource Manager instance in the region of the user.
-
-The following image shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider. 
-
-:::image type="content" source="./media/request-limits-and-throttling/request-throttling.svg" alt-text="Diagram that shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider.":::
-
-## Subscription and tenant limits
-
-Every subscription-level and tenant-level operation is subject to throttling limits. Subscription requests are ones that involve passing your subscription ID, such as retrieving the resource groups in your subscription. For example, sending a request to `https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups?api-version=2022-01-01` is a subscription-level operation. Tenant requests don't include your subscription ID, such as retrieving valid Azure locations. For example, sending a request to `https://management.azure.com/tenants?api-version=2022-01-01` is a tenant-level operation.
-
-The default throttling limits per hour are shown in the following table.
-
-| Scope | Operations | Limit |
-| ----- | ---------- | ------- |
-| Subscription | reads | 12,000 |
-| Subscription | deletes | 15,000 |
-| Subscription | writes | 1,200 |
-| Tenant | reads | 12,000 |
-| Tenant | writes | 1,200 |
-
-These limits are scoped to the security principal (user or application) making the requests and the subscription ID or tenant ID. If your requests come from more than one security principal, your limit across the subscription or tenant is greater than 12,000 and 1,200 per hour.
-
-These limits apply to each Azure Resource Manager instance. There are multiple instances in every Azure region, and Azure Resource Manager is deployed to all Azure regions. So, in practice, the limits are higher than these limits. Different instances of Azure Resource Manager usually handle the user's requests.
-
-The remaining requests are returned in the [response header values](#remaining-requests).
-
 ## Resource provider limits
 
 Resource providers apply their own throttling limits. Within each subscription, the resource provider throttles per region of the resource in the request. Because Resource Manager throttles by instance of Resource Manager, and there are several instances of Resource Manager in each region, the resource provider might receive more requests than the default limits in the previous section.

articles/container-apps/TOC.yml

@@ -271,36 +271,42 @@ items:
     - name: Overview
       href: observability.md
       displayName: Observability overview
-    - name: Troubleshoot and resolve issues with an agent
+    - name: Develop and debug with real-time logs
+      items:
+        - name: Log streaming
+          href: log-streaming.md
+        - name: Container console
+          href: container-console.md
+        - name: Container debug console
+          href: container-debug-console.md
+    - name: Monitor production workloads
+      items:
+        - name: Application logging
+          href: logging.md
+        - name: Logging options
+          href: log-options.md
+        - name: Log monitoring
+          href: log-monitoring.md
+        - name: Metrics
+          href: metrics.md
+        - name: Alerts
+          href: alerts.md
+    - name: End-to-end tracing and dashboards
+      items:
+        - name: Aspire Dashboard
+          href: aspire-dashboard.md
+        - name: OpenTelemetry agents
+          href: opentelemetry-agents.md
+        - name: Grafana dashboards
+          href: grafana-dashboards.md
+    - name: Troubleshoot and resolve issues with SRE agent
       items:
         - name: Overview
           href: ../sre-agent/overview.md
         - name: Use an SRE agent
           href: ../sre-agent/usage.md
         - name: Fix app issues with an SRE agent
           href: ../sre-agent/troubleshoot-azure-container-apps.md
-    - name: Application logging
-      href: logging.md
-    - name: Real time data
-      href: aspire-dashboard.md
-    - name: Logging options
-      href: log-options.md
-    - name: Log streaming
-      href: log-streaming.md
-    - name: Container console
-      href: container-console.md
-    - name: Container debug console
-      href: container-debug-console.md
-    - name: Metrics
-      href: metrics.md
-    - name: Log monitoring
-      href: log-monitoring.md
-    - name: Alerts
-      href: alerts.md
-    - name: OpenTelemetry agents
-      href: opentelemetry-agents.md
-    - name: Grafana dashboards
-      href: grafana-dashboards.md
 - name: Scaling & performance
   items:
     - name: Overview

articles/container-apps/compose-agent.md

@@ -2,15 +2,15 @@
 title: Deploy Docker Compose for agents to Azure Container Apps Preview
 description: Learn how to use Docker Compose for Agents on Azure Container Apps Preview.
 ms.topic: how-to
-ms.date: 11/18/2025
+ms.date: 03/31/2026
 ms.service: azure-container-apps
 ms.author: cshoe
 author: craigshoemaker
 ---
 
 # Deploy Docker Compose for agents to Azure Container Apps Preview
 
-This article shows you how to deploy applications to Azure Container Apps by using Docker’s Compose for Agents. This feature keeps the compose file you already use locally and allows you to deploy it onto Container Apps. The `az-cli` container app extension then translates the compose file into Azure Container App applications and manages identities, scaling, and model lifecycle for you.
+This article shows you how to deploy applications to Azure Container Apps by using Docker's Compose for Agents. This feature keeps the compose file you already use locally and allows you to deploy it onto Container Apps. The `az-cli` container app extension then translates the compose file into Azure Container App applications and manages identities, scaling, and model lifecycle for you.
 
 In this article, you learn to:
 
@@ -37,7 +37,7 @@ When you run `az containerapp compose create`, the CLI translates agent-focused
 
 ### Model context protocol (MCP) tooling
 
-Azure Container Apps runs a variant of [Docker’s MCP gateway](https://github.com/docker/mcp-gateway) as its own container app. It uses system-assigned managed identity to add or remove MCP tool containers within the environment dynamically. This setup appears as separate containers under the mcp-gateway application. Gateway to MCP tooling communication is limited to the network. Stdio MCP servers are wrapped to run as SSE based MCP servers on Azure Container Apps. Docker for Agents on Azure Container Apps currently supports the following Stdio MCP servers: AppSignal, BigQuery, Confluence, DuckDuckGo, Fetch, Filesystem, Git, Google Drive, Jira, MongoDB, MySQL, Notion, Playwright, PostgreSQL, SequentialThinking, Slack, SQLite, Supabase, Time, Twist.
+Azure Container Apps runs a variant of [Docker's MCP gateway](https://github.com/docker/mcp-gateway) as its own container app. It uses system-assigned managed identity to add or remove MCP tool containers within the environment dynamically. This setup appears as separate containers under the mcp-gateway application. Gateway to MCP tooling communication is limited to the network. Stdio MCP servers are wrapped to run as SSE based MCP servers on Azure Container Apps. Docker for Agents on Azure Container Apps currently supports the following Stdio MCP servers: AppSignal, BigQuery, Confluence, DuckDuckGo, Fetch, Filesystem, Git, Google Drive, Jira, MongoDB, MySQL, Notion, Playwright, PostgreSQL, SequentialThinking, Slack, SQLite, Supabase, Time, Twist.
 
 ### Models
 
@@ -138,6 +138,15 @@ az containerapp compose create \
 			--environment $ENV_NAME
 ```
 
+### Agent settings defaults
+
+Applications created without explicit agent settings receive the following defaults:
+
+* `DiscoveryMode` = `Auto`, which automatically detects agent capabilities and dependencies.
+* `IsAgent` = `false`, indicating that the app doesn't act as an agent unless explicitly configured.
+
+These defaults ensure consistent behavior for all container apps in your environment.
+
 ### Uninstalling and switching back
 
 To switch back to the stable release of the container app extension:

articles/container-apps/environment-variables.md

@@ -6,7 +6,7 @@ author: fred-cardoso
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 02/03/2025
+ms.date: 03/31/2026
 ms.author: fredcardoso
 ---
 
@@ -167,6 +167,7 @@ The following variables are available to container apps:
 | `CONTAINER_APP_ENV_DNS_SUFFIX` | The DNS suffix for the Container Apps environment. To obtain the fully qualified domain name (FQDN) of the app, append the app name to the DNS suffix in the format `$CONTAINER_APP_NAME.$CONTAINER_APP_ENV_DNS_SUFFIX`. | `<DEFAULT_HOSTNAME>.<REGION>.azurecontainerapps.io` |
 | `CONTAINER_APP_PORT` | The target port of the container app. | `8080` |
 | `CONTAINER_APP_REPLICA_NAME` | The name of the container app replica. | `my-containerapp--20mh1s9-86c8c4b497-zx9bq` |
+| `CONTAINER_NAME` | The name of the replica. Available for managed function apps and logic apps. | `my-containerapp--20mh1s9-86c8c4b497-zx9bq` |
 
 ### Jobs