Skip to content

Commit 02bb14b

Browse files
Merge pull request #227997 from guywi-ms/az-revamp
AZ article revamp
2 parents e4b3b49 + 79d1254 commit 02bb14b

File tree

3 files changed

+79
-88
lines changed

3 files changed

+79
-88
lines changed
Lines changed: 36 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -1,59 +1,58 @@
11
---
22
title: Availability zones in Azure Monitor
3-
description: Availability zones in Azure Monitor
3+
description: Learn about the data and service resilience benefits Azure Monitor availability zones provide to protect against datacenter failure.
44
ms.subservice: logs
55
ms.topic: conceptual
66
author: guywi-ms
77
ms.author: guywild
8-
ms.date: 08/18/2021
8+
ms.date: 02/21/2023
99
ms.custom: references_regions
10-
---
11-
12-
# Availability zones in Azure Monitor
13-
14-
[Azure availability zones](../../availability-zones/az-overview.md) protect your applications and data from datacenter failures and can provide resilience for Azure Monitor features that rely on a Log Analytics workspace. When a workspace is linked to an availability-zone-enabled dedicated cluster, it remains active and operational even if a specific datacenter is malfunctioning or even down, by relying on the availability of other zones in the region. You don’t need to do anything in order to switch to an alternative zone, or even be aware of the incident.
15-
16-
17-
## Regions
18-
Azure Monitor currently supports the following regions:
19-
- East US 2
20-
- West US 2
21-
- Canada Central
22-
- France Central
23-
- Japan East
24-
25-
## Dedicated clusters
26-
Azure Monitor support for availability zones requires a Log Analytics workspace linked to an [Azure Monitor dedicated cluster](logs-dedicated-clusters.md). Dedicated Clusters are a deployment option that enables advanced capabilities for Azure Monitor Logs including availability zones.
27-
28-
Not all dedicated clusters can use availability zones. Dedicated clusters created after mid-October 2020 can be set to support availability zones when they're created. New clusters created after that date default to be enabled for availability zones in regions where Azure Monitor supports them.
2910

11+
#customer-intent: As an IT manager, I want to understand the data and service resilience benefits Azure Monitor availability zones provide so that can ensure my data and services are sufficiently protected in the event of datacenter failure.
12+
---
13+
# Enhance data and service resilience in Azure Monitor Logs with availability zones
3014

31-
> [!NOTE]
32-
> Application Insights resources can use availability zones only if they're workspace-based and the workspace uses a dedicated cluster. Classic Application Insights resources can't use availability zones.
15+
[Azure availability zones](../../availability-zones/az-overview.md) protect applications and data from datacenter failures and can enhance the resilience of Azure Monitor features that rely on a Log Analytics workspace. This article describes the data and service resilience benefits Azure Monitor availability zones provide by default to [dedicated clusters](logs-dedicated-clusters.md) in supported regions.
3316

17+
## Prerequisites
3418

35-
## Determine current cluster for your workspace
36-
To determine the current workspace link status for your workspace, use [CLI, PowerShell or REST](logs-dedicated-clusters.md#check-workspace-link-status) to retrieve the [cluster details](logs-dedicated-clusters.md#check-cluster-provisioning-status). If the cluster uses an availability zone, then it will have a property called `isAvailabilityZonesEnabled` with a value of `true`. Once a cluster is created, this property can't be altered.
19+
- A Log Analytics workspace linked to a [dedicated cluster](logs-dedicated-clusters.md).
3720

38-
## Create dedicated cluster with availability zone
39-
Move your workspace to an availability zone by [creating a new dedicated cluster](logs-dedicated-clusters.md#create-a-dedicated-cluster) in a region that supports availability zones. The cluster will automatically be enabled for availability zones. Then [link your workspace to the new cluster](logs-dedicated-clusters.md#link-a-workspace-to-a-cluster).
21+
> [!NOTE]
22+
> Application Insights resources can use availability zones only if they're workspace-based and the workspace uses a dedicated cluster. Classic Application Insights resources can't use availability zones.
23+
24+
## Data resilience - supported regions
4025

41-
> [!IMPORTANT]
42-
> Availability zone is defined on the cluster at creation time and can’t be modified.
26+
Availability zones protect your data from datacenter failures by relying on datacenters in different physical locations, equipped with independent power, cooling, and networking.
4327

44-
Transitioning to a new cluster can be a gradual process. Don't remove the previous cluster until it has been purged of any data. For example, if your workspace retention is set 60 days, you may want to keep your old cluster running for that period before removing it. To learn more, see [Migrate Log Analytics workspaces to availability zone support](../../availability-zones/migrate-monitor-log-analytics.md).
28+
Azure Monitor currently supports data resilience for availability-zone-enabled dedicated clusters in these regions:
4529

46-
Any queries against your workspace will query both clusters to provide you with a single, unified result set. This allows Azure Monitor experiences, such as workbooks and dashboards, to keep getting the full result set, based on data from both clusters.
30+
| Americas | Europe | Middle East | Africa | Asia Pacific |
31+
|---|---|---|---|---|
32+
| Brazil South | France Central | UAE North | South Africa North | Australia East |
33+
| Canada Central | Germany West Central | | | Central India |
34+
| Central US | North Europe | | | Japan East |
35+
| East US | Norway East | | | Korea Central |
36+
| East US 2 | UK South | | | Southeast Asia |
37+
| South Central US | West Europe | | | East Asia |
38+
| US Gov Virginia | Sweden Central | | | China North 3 |
39+
| West US 2 | Switzerland North | | | |
40+
| West US 3 | | | | |
4741

48-
## Billing
49-
There's a [cost for using a dedicated cluster](logs-dedicated-clusters.md#create-a-dedicated-cluster). It requires a daily capacity reservation of 500 GB.
42+
## Service resilience - supported regions
5043

51-
If you already have a dedicated cluster and choose to retain it to access its data, you’ll be charged for both dedicated clusters. Starting August 4, 2021, the minimum required capacity reservation for dedicated clusters is reduced from 1000 GB/Daily to 500 GB/Daily, so we’d recommend applying that minimum to your old cluster to reduce charges.
44+
When available in your region, Azure Monitor availability zones enhance your Azure Monitor service resilience automatically. Physical separation and independent infrastructure makes interruption of service availability in your Log Analytics workspace far less likely because the Log Analytics workspace can rely on resources from a different zone.
5245

53-
The new cluster isn’t billed during its first day to avoid double billing during configuration. On the date of migration, you'll be billed only for logs ingested before the migration completes.
46+
Azure Monitor currently supports service resilience for availability-zone-enabled dedicated clusters in these regions:
5447

48+
- East US 2
49+
- West US 2
50+
- Canada Central
51+
- France Central
52+
- Japan East
5553

5654
## Next steps
5755

58-
- See [Using queries in Azure Monitor Log Analytics](queries.md) to see how users interact with query packs in Log Analytics.
59-
- See [Migrate Log Analytics workspaces to availability zone support](../../availability-zones/migrate-monitor-log-analytics.md).
56+
Learn more about how to:
57+
- [Set up a dedicated cluster](logs-dedicated-clusters.md).
58+
- [Migrate Log Analytics workspaces to availability zone support](../../availability-zones/migrate-monitor-log-analytics.md).

0 commit comments

Comments
 (0)