Merge pull request #247220 from jennyhunter-msft/jennyhunter-msft-patch-08022023

Update control plane resiliency documentation

Author: prmerger-automator[bot]

articles/azure-resource-manager/management/control-plane-and-data-plane.md

@@ -41,7 +41,7 @@ Azure Resource Manager handles all control plane requests. It automatically appl
 * [Management Locks](lock-resources.md)
 * [Activity Logs](../../azure-monitor/essentials/activity-log.md)
 
-After authenticating the request, Azure Resource Manager sends it to the resource provider, which completes the operation.
+After authenticating the request, Azure Resource Manager sends it to the resource provider, which completes the operation. Even during periods of unavailability for the control plane, you can still access the data plane of your Azure resources. For instance, you can continue to access and operate on data in your storage account resource via its separate storage URI `https://myaccount.blob.core.windows.net` even when `https://management.azure.com` is not available.
 
 The control plane includes two scenarios for handling requests - "green field" and "brown field". Green field refers to new resources. Brown field refers to existing resources. As you deploy resources, Azure Resource Manager understands when to create new resources and when to update existing resources. You don't have to worry that identical resources will be created.
 

articles/azure-resource-manager/management/overview.md

@@ -111,9 +111,9 @@ There are some important factors to consider when defining your resource group:
 
 The Azure Resource Manager service is designed for resiliency and continuous availability. Resource Manager and control plane operations (requests sent to `management.azure.com`) in the REST API are:
 
-* Distributed across regions. Although Azure Resource Manager is distributed across regions, some services are regional. This distinction means that while the initial handling of the control plane operation is resilient, the request may be susceptible to regional outages when forwarded to the service.
+* Distributed across regions. Azure Resource Manager has a separate instance in each region of Azure, meaning that a failure of the Azure Resource Manager instance in one region won't impact the availability of Azure Resource Manager or other Azure services in another region. Although Azure Resource Manager is distributed across regions, some services are regional. This distinction means that while the initial handling of the control plane operation is resilient, the request may be susceptible to regional outages when forwarded to the service.
 
-* Distributed across Availability Zones (and regions) in locations that have multiple Availability Zones.
+* Distributed across Availability Zones (and regions) in locations that have multiple Availability Zones. This distribution ensures that when a region loses one or more zones, Azure Resource Manager can either fail over to another zone or to another region to continue to provide control plane capability for the resources.
 
 * Not dependent on a single logical data center.