Skip to content

Commit e0a5423

Browse files
Update control plane resiliency documentation
Update public documentation with details about the Azure control plane's resiliency impact
1 parent e83d3c8 commit e0a5423

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Azure Resource Manager handles all control plane requests. It automatically appl
4141
* [Management Locks](lock-resources.md)
4242
* [Activity Logs](../../azure-monitor/essentials/activity-log.md)
4343

44-
After authenticating the request, Azure Resource Manager sends it to the resource provider, which completes the operation.
44+
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.
4545

4646
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.
4747

0 commit comments

Comments
 (0)