You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/includes/logs-availability-zones.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,4 +10,4 @@ Each Azure region that supports availability zones has a set of datacenters equi
10
10
11
11
Azure Monitor Logs availability zones are [zone-redundant](../../reliability/availability-zones-overview.md#zonal-and-zone-redundant-services), which means that Microsoft manages spreading service requests and replicating data across different zones in supported regions. If one zone is affected by an incident, Microsoft manages failover to a different availability zone in the region automatically. You don't need to take any action because switching between zones is seamless.
12
12
13
-
In most regions, Azure Monitor Logs availability zones support **data resilience**, which means your stored data is protected against zonal failures, but service operations might be impacted by regional incidents. A subset of the availability zones that support data resilience currently also support service **service resilience**, which means that Azure Monitor Logs service operations - for example, log ingestion, queries, and alerts - can continue in the event of a zone failure.
13
+
In most regions, Azure Monitor Logs availability zones support **data resilience**, which means your stored data is protected against zonal failures, but service operations might be impacted by regional incidents. A subset of the availability zones that support data resilience currently also support **service resilience**, which means that Azure Monitor Logs service operations - for example, log ingestion, queries, and alerts - can continue in the event of a zone failure.
0 commit comments