Merge pull request #304094 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-11 22:00 UTC

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

.openpublishing.redirection.json

@@ -6998,11 +6998,15 @@
       "source_path": "articles/reliability/migrate-sql-database.md",
       "redirect_url": "/azure/azure-sql/database/enable-zone-redundancy",
       "redirect_document_id": false
-    },
+    },    
     {
       "source_path": "articles/reliability/migrate-app-gateway-v2.md",
       "redirect_url": "/azure/reliability/reliability-application-gateway-v2",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/reliability/migrate-storage.md",
+      "redirect_url": "/azure/storage/common/redundancy-migration",
     }
   ]
 }

articles/api-center/enable-api-analysis-linting.md

@@ -119,7 +119,7 @@ To deploy the Azure Functions app that runs the linting function on API definiti
 1. Clone the [GitHub repository](https://github.com/Azure/APICenter-Analyzer/) and open it in Visual Studio Code.
 1. In the `resources/rulesets` folder, you can find an `oas.yaml` file. This file reflects your current API style guide and can be modified based on your organizational needs and requirements.
 1. Optionally, run the function app locally to test it. For details, see the [README](https://github.com/Azure/APICenter-Analyzer/tree/preview#-configure--run-your-function-locally) file in the repository.
-1. Deploy the function app to Azure. For steps, see [Quickstart: Create a function in Azure with TypeScript using Visual Studio Code](../azure-functions/create-first-function-vs-code-typescript.md#sign-in-to-azure).
+1. Deploy the function app to Azure. For steps, see [Quickstart: Create a function in Azure with TypeScript using Visual Studio Code](../azure-functions/how-to-create-function-vs-code.md?pivot=programming-language-typescript#sign-in-to-azure).
 
     > [!NOTE]
     > Deploying the function app might take a few minutes.

articles/api-management/api-management-role-based-access-control.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 07/10/2024
+ms.date: 08/08/2025
 ms.author: danlep 
 ms.custom: devx-track-azurepowershell
 
@@ -15,13 +15,13 @@ ms.custom: devx-track-azurepowershell
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-Azure API Management relies on Azure role-based access control (Azure RBAC) to enable fine-grained access management for API Management services and entities (for example, APIs and policies). This article gives you an overview of the built-in and custom roles in API Management. For more information on access management in the Azure portal, see [Get started with access management in the Azure portal](../role-based-access-control/overview.md).
+Azure API Management relies on Azure role-based access control (Azure RBAC) to enable fine-grained access management for API Management services and entities including workspaces. This article gives you an overview of the built-in and custom roles in API Management. For more information on access management in the Azure portal, see [Get started with access management in the Azure portal](../role-based-access-control/overview.md).
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
 ## Built-in service roles
 
-API Management currently provides three built-in roles and will add two more roles in the near future. These roles can be assigned at different scopes, including subscription, resource group, and individual API Management instance. For instance, if you assign the "API Management Service Reader" role to a user at the resource-group level, then the user has read access to all API Management instances inside the resource group. 
+API Management currently provides three built-in service roles. These roles can be assigned at different scopes, including subscription, resource group, and individual API Management instance. For instance, if you assign the "API Management Service Reader" role to a user at the resource-group level, then the user has read access to all API Management instances inside the resource group. 
 
 The following table provides brief descriptions of the built-in roles. You can assign these roles by using the Azure portal or other tools, including Azure [PowerShell](../role-based-access-control/role-assignments-powershell.md), [Azure CLI](../role-based-access-control/role-assignments-cli.md), and [REST API](../role-based-access-control/role-assignments-rest.md). For details about how to assign built-in roles, see [Assign Azure roles to manage access to your Azure subscription resources](../role-based-access-control/role-assignments-portal.yml).
 

articles/app-service/configure-zone-redundancy.md

@@ -1,6 +1,6 @@
 ---
-title: Configure App Service plans for zone redundancy
-description: Learn how to configure your App Service plan for zone redundancy. Understand how your App Service plan instances are distributed across availability zones and how to check for zone redundancy support.
+title: Configure App Service Plans for Zone Redundancy
+description: Learn how to configure an App Service plan for zone redundancy, see how plan instances spread across availability zones, and check for zone redundancy support.
 ms.topic: conceptual
 ms.service: azure-app-service
 ms.date: 07/15/2025
@@ -10,21 +10,22 @@ ms.author: anaharris
 ---
 # Configure App Service plans for zone redundancy
 
-Azure App Service provides built-in reliability features to help ensure your applications are available and resilient. This article describes how to create your App Service plan with zone redundancy. It also covers how to disable and enable zone redundancy on existing plans, and how to check for zone redundancy support. To learn more about how App Service supports zone redundancy, see [Reliability in Azure App Service](../reliability/reliability-app-service.md).
+Azure App Service provides built-in reliability features to help ensure that your applications remain available and resilient. This article describes how to create an App Service plan that includes zone redundancy. It also covers how to disable and enable zone redundancy on existing plans and how to check for zone redundancy support. For more information about zone redundancy, see [Reliability in App Service](../reliability/reliability-app-service.md).
 
-## Create a new App Service plan with zone redundancy
+## Create a new zone-redundant App Service plan
 
-To create a new App Service plan with zone redundancy:
+To create a new App Service plan that includes zone redundancy, follow the appropriate steps.
 
 # [Azure portal](#tab/portal)
 
-Follow the guidance in [Create an App Service plan](../app-service/app-service-plan-manage.md#create-an-app-service-plan). Make sure to select *Enabled* for **Zone redundancy**.
+Follow the guidance to [create an App Service plan](../app-service/app-service-plan-manage.md#create-an-app-service-plan). Make sure to select **Enabled** for **Zone redundancy**.
 
 :::image type="content" source="./media/configure-zone-redundancy/app-service-create-zr-plan.png" alt-text="Screenshot of zone redundancy enablement during App Service plan creation in the Azure portal.":::
 
 # [Azure CLI](#tab/azurecli)
 
-Set the `--zone-redundant` argument. You must also specify the `--number-of-workers` argument, which is the number of instances, and set a value greater than or equal to 2.
+- Set the `--zone-redundant` argument.
+- Set the `--number-of-workers` argument, which is the number of instances, to a value of 2 or more.
 
 ```azurecli
 az appservice plan create \
@@ -37,7 +38,8 @@ az appservice plan create \
 
 # [Bicep](#tab/bicep)
 
-Set the `zoneRedundant` property to `true`. You must also define the `sku.capacity` property to a value of 2 or greater. If you don't define the `sku.capacity` property, the value defaults to 1.
+- Set the `zoneRedundant` property to `true`.
+- Set the `sku.capacity` property to a value of 2 or more. If you don't define the `sku.capacity` property, the value defaults to 1.
 
 ```bicep
 resource appServicePlan 'Microsoft.Web/serverfarms@2024-11-01' = {
@@ -59,45 +61,47 @@ resource appServicePlan 'Microsoft.Web/serverfarms@2024-11-01' = {
 
 ## Set zone redundancy for an existing App Service plan
 
-1. If you want to enable zone redundancy on an existing App Service plan, [check for zone redundancy support for your App Service plan](#check-for-zone-redundancy-support-on-an-app-service-plan).
-1. If your App Service plan supports zone redundancy, you can enable or disable it by using the Azure portal, Azure CLI, or Bicep/Resource Manager.
+1. To enable zone redundancy on an existing App Service plan, [check for zone redundancy support](#check-for-zone-redundancy-support-on-an-app-service-plan).
+1. If your App Service plan supports zone redundancy, use the Azure portal, the Azure CLI, or Bicep and Azure Resource Manager to enable or disable it.
 
     # [Azure portal](#tab/portal)
 
-    1. In the [Azure portal](https://portal.azure.com), navigate to  your App Service plan.
-    1. Select **Settings > Scale out (App Service plan)** in the left navigation pane.
-    1. Select **Zone redundancy** if you wish to enable zone redundancy. Deselect if you wish to disable it. 
+    1. In the [Azure portal](https://portal.azure.com), go to your App Service plan.
+    1. Select **Settings** > **Scale out (App Service plan)** in the left navigation pane.
+    1. Select **Zone Redundancy** to enable zone redundancy. Deselect it to disable it. 
 
-        Changing the zone redundancy status of an App Service plan is almost instantaneous. You don't experience downtime or performance problems during the process. 
+        The zone redundancy status of an App Service plan changes almost instantaneously. No downtime or performance problems occur during the process. 
 
         :::image type="content" source="./media/configure-zone-redundancy/app-service-plan-zone-redundancy-portal.png" alt-text="Screenshot of zone redundancy property for an App Service plan in the Azure portal.":::
 
     > [!IMPORTANT]
-    > If you have *Rules Based* scaling enabled, you can't use the Azure portal to enable zone redundancy. You must use the Azure CLI or Bicep/Resource Manager instead.
+    > If you have *Rules Based* scaling enabled, you can't use the Azure portal to enable zone redundancy. You must use the Azure CLI or Bicep and Resource Manager instead.
     
      # [Azure CLI](#tab/azurecli)
 
-    - To *enable zone redundancy*, set the `zoneRedundant` property to `true`. You must also specify the `sku.capacity` argument, which is the number of instances, and set a value greater than or equal to 2.
+    - To *enable zone redundancy*, set the `zoneRedundant` property to `true`.
+    - Set the `sku.capacity` argument, which is the number of instances, to a value of 2 or more.
 
-        ```azurecli
-        az appservice plan update \
-            -n <app-service-plan-name> \
-            -g <resource-group-name> \
-            --set zoneRedundant=true sku.capacity=2
-        ```
+       ```azurecli
+      az appservice plan update \
+          -n <app-service-plan-name> \
+          -g <resource-group-name> \
+          --set zoneRedundant=true sku.capacity=2
+      ```
     
     - To *disable zone redundancy*, set the `zoneRedundant` property to `false`.
     
-        ```azurecli
-        az appservice plan update \
-            -n <app-service-plan-name> \
-            -g <resource-group-name> \
-            --set zoneRedundant=false
-        ```
+       ```azurecli
+      az appservice plan update \
+          -n <app-service-plan-name> \
+          -g <resource-group-name> \
+          --set zoneRedundant=false
+       ```
     
     # [Bicep](#tab/bicep)
     
-    - To *enable zone redundancy*, set the `zoneRedundant` property to `true`. You must also define the `sku.capacity` property to a value of 2 or greater. If you don't define the `sku.capacity` property, the value defaults to 1.
+    - To *enable zone redundancy*, set the `zoneRedundant` property to `true`.
+    - Set the `sku.capacity` property to a value of 2 or more. If you don't define the `sku.capacity` property, the value defaults to 1.
     
         ```bicep
         resource appServicePlan 'Microsoft.Web/serverfarms@2024-11-01' = {
@@ -121,23 +125,23 @@ resource appServicePlan 'Microsoft.Web/serverfarms@2024-11-01' = {
 
 ## Check for zone redundancy support on an App Service plan
 
-To see whether an existing App Service plan supports zone redundancy:
+To check whether an existing App Service plan supports zone redundancy, do the following steps:
 
-1. Get the maximum number of availability zones that the App Service plan can use by using the Azure portal, Azure CLI, or Bicep/Resource Manager:
+1. Determine the maximum number of availability zones that the App Service plan supports by using the Azure portal, the Azure CLI, or Bicep and Resource Manager.
 
     # [Azure portal](#tab/portal)
     
-    1. In the [Azure portal](https://portal.azure.com), navigate to your App Service plan.
+    1. In the [Azure portal](https://portal.azure.com), go to your App Service plan.
     
     1. Select **Scale out (App Service plan)**. 
     
-        The maximum number of zones that your App Service plan can use is shown in **Maximum available zones**. 
+        **Maximum available zones** shows the maximum number of zones that your App Service plan can use.
     
-        :::image type="content" source="./media/configure-zone-redundancy/app-service-plan-max-zones-portal.png" alt-text="Screenshot of maximum available zones property in the Scale out blade in the Azure portal for an App Service plan.":::
+        :::image type="content" source="./media/configure-zone-redundancy/app-service-plan-max-zones-portal.png" alt-text="Screenshot of the maximum available zones property in the scale-out section in the Azure portal for an App Service plan.":::
     
     # [Azure CLI](#tab/azurecli)
     
-    Query the plan's `maximumNumberOfZones` property:
+    Query the plan's `maximumNumberOfZones` property.
     
     ```azurecli
     az appservice plan show \
@@ -148,7 +152,7 @@ To see whether an existing App Service plan supports zone redundancy:
     
     # [Bicep](#tab/bicep)
     
-    Query the plan's `maximumNumberOfZones` property:
+    Query the plan's `maximumNumberOfZones` property.
     
     ```bicep
     resource appServicePlan 'Microsoft.Web/serverfarms@2024-11-01' existing = {
@@ -161,43 +165,43 @@ To see whether an existing App Service plan supports zone redundancy:
     
     ---
     
-1. Compare the number with the following table to determine whether your plan supports zone redundancy:
+1. Compare the number with the following table to determine whether your plan supports zone redundancy.
     
-    | Maximum Number of Zones  | Zone redundancy support |
+    | Maximum number of zones  | Zone redundancy support |
     | ------------------------ | ----------------------- |
-    | Greater than 1           | Supported               |
+    | More than 1           | Supported               |
     | Equal to 1               | Not supported*          |
 
-    \* If you're on a plan or a stamp that doesn't support availability zones, you must create a new App Service plan in a new resource group so that you land on the App Service footprint that supports zones.
+    \* If you use a plan or a stamp that doesn't support availability zones, you must create a new App Service plan in a new resource group. This setup ensures that your deployment lands on App Service infrastructure that supports availability zones.
 
 ## View physical zones for an App Service plan
 
-When you have a zone-redundant App Service plan, the platform automatically places the instances across [physical availability zone](../reliability/availability-zones-overview.md#physical-and-logical-availability-zones). If you want to verify that your instances are spread across zones, you can check which physical availability zones your plan's instances use by using the Azure portal or Azure CLI:
+When you have a zone-redundant App Service plan, the platform automatically places the instances across [physical availability zones](../reliability/availability-zones-overview.md#physical-and-logical-availability-zones). To verify that your instances are spread across zones, use the Azure portal or the Azure CLI to check which physical availability zones your plan's instances use.
 
 # [Azure portal](#tab/portal)
 
 1. In the [Azure portal](https://portal.azure.com), go to your App Service app. If you have multiple apps in a plan, you can select any app.
  
-1. Select the **Health check** blade.
+1. Select **Health check**.
 
-1. Select the **Instances** tab to view the physical zone placement for each of your instances.
+1. Select **Instances** to view the physical zone placement for each of your instances.
     
-    :::image type="content" source="./media/configure-zone-redundancy/app-service-physical-zones.png" alt-text="Screenshot of the Instances tab in the Health Check blade with the physical zone information in the Azure portal for an App Service app.":::
+    :::image type="content" source="./media/configure-zone-redundancy/app-service-physical-zones.png" alt-text="Screenshot of the Instances tab in the Health Check section with the physical zone information in the Azure portal for an App Service app.":::
 
 # [Azure CLI](#tab/azurecli)
 
-Use the [REST API](/rest/api/appservice/web-apps/get-instance-info), which returns the `physicalZone` value for each instance in the App Service plan:
+Use the [REST API](/rest/api/appservice/web-apps/get-instance-info), which returns the `physicalZone` value for each instance in the App Service plan.
 
 ```azurecli
 az rest --method get --url https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Web/sites/{appName}/instances?api-version=2024-04-01
 ```
 
 # [Bicep](#tab/bicep)
 
-This operation is not supported in Bicep. Use the Azure CLI or Azure portal instead.
+Bicep doesn't support this operation. Use the Azure CLI or the Azure portal instead.
 
 ---
 
 ## Related content
-- [Reliability in Azure App Service](../reliability/reliability-app-service.md)
-- [Configure App Service Environment for zone redundancy](../app-service/environment/configure-zone-redundancy-environment.md)
+- [Reliability in App Service](../reliability/reliability-app-service.md)
+- [Configure an App Service Environment for zone redundancy](../app-service/environment/configure-zone-redundancy-environment.md)