edit include files

jmart1428 · jmart1428 · commit c3aa01eb2275 · 2025-07-25T13:44:20.000-04:00
diff --git a/articles/reliability/TOC.yml b/articles/reliability/TOC.yml
@@ -43,7 +43,7 @@
     items:
     - name: Azure App Service
       href: reliability-app-service.md
-    - name: Azure App Service Environment
+    - name: App Service Environment
       href: reliability-app-service-environment.md
     - name: Azure Batch
       href: reliability-batch.md
diff --git a/articles/reliability/includes/app-service/reliability-app-service-service-level-agreement-include.md b/articles/reliability/includes/app-service/reliability-app-service-service-level-agreement-include.md
@@ -1,6 +1,4 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
diff --git a/articles/reliability/includes/app-service/reliability-architecture-overview.md b/articles/reliability/includes/app-service/reliability-architecture-overview.md
@@ -1,6 +1,4 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
@@ -9,14 +7,14 @@
  ms.custom: include file
 ---
 
-App Service offers the following redundancy features:
+App Service provides the following redundancy features:
 
-- **Distribution across fault domains:** At the platform level - without any configuration from you - Azure automatically distributes your App Service plan’s VM instances across [fault domains](/azure/virtual-machines/availability-set-overview#fault-domains) within the Azure region. This distribution minimizes the risk of localized hardware failures by grouping virtual machines that share a common power source and network switch. 
+- **Distribution across fault domains:** At the platform level, Azure automatically distributes your App Service plan's VM instances across [fault domains](/azure/virtual-machines/availability-set-overview#fault-domains) within the Azure region. This distribution minimizes the risk of localized hardware failures by grouping VMs that share a common power source and network switch. 
 
-- **Distribution across availability zones:** If you enable zone redundancy on a supported App Service plan, Azure also distributes your instances across availability zones within the region, offering higher resiliency in the event of a zone outage. To learn more about zone redundancy, see [Availability zone support](#availability-zone-support).
+- **Distribution across availability zones:** If you enable zone redundancy on a supported App Service plan, Azure distributes your instances across availability zones within the region. This configuration provides higher resiliency if a zone outage occurs. For more information about zone redundancy, see [Availability zone support](#availability-zone-support).
 
-- **Scaling apps:** When you configure your App Service plan to run multiple VM instances, then all apps in the plan run on all instances by default. If you configure your plan for autoscaling, then all apps in the plan scale out together, based on the autoscale settings. However, you can customize how many plan instances run a specific app by using [per-app scaling](/azure/app-service/manage-scale-per-app).
+- **App scaling:** When you configure your App Service plan to run multiple VM instances, all apps in the plan run on all instances by default. If you configure your plan for autoscaling, all apps scale out together based on the autoscale settings. However, you can customize how many plan instances run a specific app by using [per-app scaling](/azure/app-service/manage-scale-per-app).
 
-- **Scale units:** Behind the scenes - without any configuration from you - Azure App Service runs on a platform infrastructure called *scale units* (also known as *stamps*). A scale unit includes all the components needed to host and run App Service, including compute, storage, networking, and load balancing. Azure manages scale units to ensure balanced workload distribution, perform routine maintenance, and maintain overall platform reliability.
+- **Scale units:** App Service runs on a platform infrastructure called *scale units*, also known as *stamps*. A scale unit includes all components needed to host and run App Service, including compute, storage, networking, and load balancing. Azure manages scale units to ensure balanced workload distribution, perform routine maintenance, and maintain overall platform reliability.
 
-    Certain capabilities might be applied to some scale units and not others. For example, zone redundancy might be supported by some App Service scale units but not by other scale units in the same region.
+    Some capabilities might only be applied on specific scale units. For example, some App Service scale units might support zone redundancy, while other scale units in the same region don't support it.
diff --git a/articles/reliability/includes/app-service/reliability-architecture-plans.md b/articles/reliability/includes/app-service/reliability-architecture-plans.md
@@ -1,6 +1,4 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
@@ -9,4 +7,4 @@
  ms.custom: include file
 ---
 
-An App Service plan defines a set of compute resources that run your web apps. All web apps must run inside an App Service plan. You can scale an App Service plan to run on multiple virtual machine *instances* (workers). These instances are the compute resources that run your app code. A single App Service plan can host multiple apps, all running on the same shared set of VM instances.
+An App Service plan defines a set of compute resources that run your web apps. All web apps must run inside an App Service plan. You can scale an App Service plan to run on multiple VM *instances*, also called *workers*. These instances provide the compute resources that run your app code. A single App Service plan can host multiple apps. All apps run on the same shared set of VM instances.
diff --git a/articles/reliability/includes/app-service/reliability-backups-include.md b/articles/reliability/includes/app-service/reliability-backups-include.md
@@ -1,6 +1,4 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
@@ -9,4 +7,4 @@
  ms.custom: include file
 ---
 
-This feature is useful if it's hard to redeploy your code, or if you store state on disk. For most solutions, you shouldn't rely exclusively on backups. Instead, use the other capabilities described in this guide to support your resiliency requirements. However, backups protect against some risks that other approaches don't. For more information, see [Back up and restore your app in App Service](/azure/app-service/manage-backup).
+These capabilities help when redeploying code is difficult or when you store state on disk. Most solutions shouldn't rely exclusively on backups. Instead, use the other capabilities in this guide to support your resiliency requirements. However, backups protect against some risks that other approaches don't. For more information, see [Back up and restore your app in App Service](/azure/app-service/manage-backup).
diff --git a/articles/reliability/includes/app-service/reliability-capacity-planning-management-include.md b/articles/reliability/includes/app-service/reliability-capacity-planning-management-include.md
@@ -1,11 +1,9 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
  ms.date: 07/17/2025
  ms.author: anaharris
  ms.custom: include file
 ---
-To prepare for availability zone failure, consider *over-provisioning* the capacity of your App Service plan. Over-provisioning allows the solution to tolerate some degree of capacity loss and continue to function without degraded performance. For more information, see [Manage capacity with over-provisioning](/azure/reliability/concept-redundancy-replication-backup#manage-capacity-with-over-provisioning).
+To prepare for availability zone failure, consider *over-provisioning* the capacity of your App Service plan. This approach allows the solution to tolerate some capacity loss and continue to function without degraded performance. For more information, see [Manage capacity by using over-provisioning](/azure/reliability/concept-redundancy-replication-backup#manage-capacity-with-over-provisioning).
diff --git a/articles/reliability/includes/app-service/reliability-failback-include.md b/articles/reliability/includes/app-service/reliability-failback-include.md
@@ -1,6 +1,4 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
diff --git a/articles/reliability/includes/app-service/reliability-instance-distribution-across-zones-include.md b/articles/reliability/includes/app-service/reliability-instance-distribution-across-zones-include.md
@@ -1,6 +1,4 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
@@ -9,18 +7,19 @@
  ms.custom: include file
 ---
 
-When you create a zone-redundant App Service plan, the instances of your App Service plan are distributed across the availability zones in the region. The distribution is done automatically by Azure to ensure that your apps remain available even if one zone experiences an outage.
+When you create a zone-redundant App Service plan, Azure distributes the plan's instances across availability zones in the region. This distribution ensures that your apps remain available even if one zone experiences an outage.
 
-Instance distribution in a zone-redundant deployment follows specific rules. These rules remain applicable as the app scales in and scales out:
+Instance distribution in a zone-redundant deployment follows specific rules. These rules apply as the app scales in and out:
 
 - **Minimum instances:** Your App Service plan must have a minimum of two instances for zone redundancy.
 
-- **Maximum availability zones supported by your plan:** Azure determines the number of availability zones that your plan can use, which is referred to as *maximumNumberOfZones*. To view the number of availability zones that your specific plan is able to use, see [Check zone redundancy support for an App Service plan](../../../app-service/configure-zone-redundancy.md#check-for-zone-redundancy-support-on-an-app-service-plan).
+- **Maximum availability zones supported by your plan:** Azure determines the number of availability zones that your plan can use, which is referred to as *maximumNumberOfZones*. To view the number of availability zones that your specific plan can use, see [Check zone redundancy support for an App Service plan](../../../app-service/configure-zone-redundancy.md#check-for-zone-redundancy-support-on-an-app-service-plan).
 
-- **Instance distribution:** When zone redundancy is enabled, plan instances are distributed across multiple availability zones automatically. The distribution is based on the following rules:
+- **Instance distribution:** When zone redundancy is enabled, Azure distributes plan instances across multiple availability zones automatically. The distribution is based on the following rules:
 
-    - The instances distribute evenly if you specify a capacity (number of instances) greater than *maximumNumberOfZones* and the number of instances is divisible by *maximumNumberOfZones*.
-    - Any remaining instances are distributed across the remaining zones.
-    - When the App Service platform allocates instances for a zone-redundant App Service plan, it uses best-effort zone balancing that the underlying Azure virtual machine scale sets provide. An App Service plan is balanced if each zone has the same number of VMs or differs by plus one VM or minus one VM from all other zones. For more information, see [Zone balancing](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones#zone-balancing).
+    - If the number of instances exceeds *maximumNumberOfZones* and divides evenly, Azure distributes the instances evenly across zones.
 
-- **Physical zone placement:** You can view the [physical availability zone](/azure/reliability/availability-zones-overview#physical-and-logical-availability-zones) that's used for each of your App Service plan instances. For more information, see [View physical zones for an App Service plan](../../../app-service/configure-zone-redundancy.md#check-for-zone-redundancy-support-on-an-app-service-plan).
+    - If the number of instances doesn't divide evenly, Azure distributes the remaining instances across the remaining zones.
+    - When the App Service platform allocates instances for a zone-redundant App Service plan, it uses best-effort zone balancing that the underlying Azure virtual machine scale sets provide. A plan is balanced if each zone has the same number of VMs or differs by one instance from all other zones. For more information, see [Zone balancing](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones#zone-balancing).
+
+- **Physical zone placement:** You can view the [physical availability zone](/azure/reliability/availability-zones-overview#physical-and-logical-availability-zones) used for each of your App Service plan instances. For more information, see [View physical zones for an App Service plan](../../../app-service/configure-zone-redundancy.md#check-for-zone-redundancy-support-on-an-app-service-plan).
diff --git a/articles/reliability/includes/app-service/reliability-maintenance-include.md b/articles/reliability/includes/app-service/reliability-maintenance-include.md
@@ -1,13 +1,11 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
  ms.date: 07/17/2025
  ms.author: anaharris
  ms.custom: include file
 ---
-Azure App Service performs regular service upgrades, as well as other forms of maintenance. To ensure that your expected capacity is available during an upgrade, the platform automatically adds extra instances of the App Service plan during the upgrade process.
+App Service performs regular service upgrades and other maintenance tasks. To maintain your expected capacity during an upgrade, the platform automatically adds extra instances of the App Service plan during the upgrade process.
 
-**Enable zone redundancy.** When you enable zone redundancy on your App Service plan, you also improve your resiliency to updates that the App Service platform rolls out. *Update domains* consist of collections of virtual machines (VMs) that are taken offline at the time of an update. Update domains are tied to availability zones. Deploying multiple instances in your App Service plan and enabling zone redundancy for your plan adds an extra layer of resiliency during upgrades if an instance or zone becomes unhealthy.
+**Enable zone redundancy.** When you enable zone redundancy on your App Service plan, you also improve resiliency during platform updates. *Update domains* consist of collections of VMs that go offline during an update, and they map to availability zones. Deploying multiple instances in your App Service plan and enabling zone redundancy for your plan adds an extra layer of resiliency if an instance or zone becomes unhealthy during an upgrade.
diff --git a/articles/reliability/includes/app-service/reliability-normal-operations-include.md b/articles/reliability/includes/app-service/reliability-normal-operations-include.md
@@ -1,15 +1,13 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
  ms.date: 07/17/2025
  ms.author: anaharris
  ms.custom: include file
 ---
-The following section describes what to expect when App Service plans are configured for zone redundancy and all availability zones are operational:
+The following section describes what to expect when you configure App Service plans for zone redundancy and all availability zones are operational:
 
-- **Traffic routing between zones:** During normal operations, traffic is routed between all of your available App Service plan instances across all availability zones.
+- **Traffic routing between zones:** During normal operations, traffic is routed between all available App Service plan instances across all availability zones.
 
 - **Data replication between zones:** During normal operations, any state stored in your application's file system is stored in zone-redundant storage and synchronously replicated between availability zones.
diff --git a/articles/reliability/includes/app-service/reliability-testing-for-zone-failures-include.md b/articles/reliability/includes/app-service/reliability-testing-for-zone-failures-include.md
@@ -1,11 +1,9 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
  ms.date: 07/17/2025
  ms.author: anaharris
  ms.custom: include file
 ---
-The App Service platform manages traffic routing, failover, and failback for zone-redundant App Service plans. Because this feature is fully managed, you don't need to initiate or validate availability zone failure processes.
+The App Service platform manages traffic routing, failover, and failback for zone-redundant App Service plans. This feature is fully managed, so you don't need to initiate or validate availability zone failure processes.
diff --git a/articles/reliability/includes/app-service/reliability-transient-fault-handling-include.md b/articles/reliability/includes/app-service/reliability-transient-fault-handling-include.md
@@ -1,6 +1,4 @@
 ---
- title: include file
- description: include file
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
@@ -9,10 +7,10 @@
  ms.custom: include file
 ---
 
-Microsoft-provided SDKs usually handle transient faults. Because you host your own applications on App Service, consider how to avoid causing transient faults:
+Microsoft-provided SDKs usually handle transient faults. Because you host your own applications on App Service, take steps to reduce the chance of transient faults:
 
-- **Deploy multiple instances in your plan.** App Service performs automated updates and other forms of maintenance on instances in your plan. If an instance becomes unhealthy, the service can automatically replace that instance with a new healthy instance. During the replacement process, there can be a short period when the previous instance is unavailable and a new instance isn't ready to serve traffic. You can mitigate these effects by deploying multiple instances of your App Service plan.
+- **Deploy multiple instances in your plan.** App Service performs automated updates and other forms of maintenance on instances in your plan. If an instance becomes unhealthy, the service can automatically replace that instance with a new healthy instance. During the replacement process, there can be a short period when the previous instance is unavailable and a new instance isn't ready to serve traffic. To mitigate these effects, deploy multiple instances of your App Service plan.
 
 - **Use deployment slots.** App Service [deployment slots](/azure/app-service/deploy-staging-slots) enable zero-downtime deployments of your applications. Use deployment slots to minimize the effect of deployments and configuration changes for your users. Deployment slots also reduce the likelihood that your application restarts. Restarting the application causes a transient fault.
 
-- **Avoid scaling up or scaling down.** Scaling up and down require involve changing the CPU, memory, and other resources that are allocated to each instance. Scale-up and scale-down operations can trigger an application restart. Instead of scaling up or scaling down, select a tier and instance size that meet your performance requirements under typical load. You can scale out and scale in by dynamically adding and removing instances to handle changes in traffic volume.
+- **Avoid scaling up or scaling down.** These operations change the CPU, memory, and other resources assigned to each instance, and they can trigger an application restart. Instead, select a tier and instance size that meet your performance requirements under typical load. To scale out and scale in, dynamically add and remove instances to handle changes in traffic volume.
diff --git a/articles/reliability/includes/app-service/reliability-zone-down-experience-include.md b/articles/reliability/includes/app-service/reliability-zone-down-experience-include.md
diff --git a/articles/reliability/includes/reliability-service-level-agreement-include.md b/articles/reliability/includes/reliability-service-level-agreement-include.md
diff --git a/articles/reliability/reliability-app-service-environment.md b/articles/reliability/reliability-app-service-environment.md
