Skip to content

Commit 1835f05

Browse files
Update overview with tone and clarification fixes
Update the Azure Resource Manager overview page with some of the suggested tone and clarification fixes.
1 parent c7c550c commit 1835f05

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,9 +111,9 @@ There are some important factors to consider when defining your resource group:
111111

112112
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:
113113

114-
* 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 will not 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.
114+
* 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.
115115

116-
* Distributed across Availability Zones (and regions) in locations that have multiple Availability Zones. This ensures that when a region loses a single zone, Azure Resource Manager can either failover to another zone or to another region to continue to operate. In the case of multi-zone loss, Azure Resource Manager can failover to another region to continue to provide control plane capability for resources in the unavailable region.
116+
* Distributed across Availability Zones (and regions) in locations that have multiple Availability Zones. This distribution ensures that when a region loses a single zone, Azure Resource Manager can either fail over to another zone or to another region to continue to operate. If there is a multi-zone loss, Azure Resource Manager can fail over to another region to continue to provide control plane capability for resources in the unavailable region.
117117

118118
* Not dependent on a single logical data center.
119119

0 commit comments

Comments
 (0)