Skip to content

Commit 3386401

Browse files
authored
Merge pull request #203255 from SnehaSudhirG/29June-AZforAutomation
Added a new article on AZ and updated TOC
2 parents 3b4e93e + e2679d0 commit 3386401

File tree

2 files changed

+77
-0
lines changed

2 files changed

+77
-0
lines changed

articles/automation/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,10 @@
5858
href: automation-secure-asset-encryption.md
5959
- name: Management of Azure Automation data
6060
href: automation-managing-data.md
61+
- name: High availability
62+
items:
63+
- name: Availability zones
64+
href: automation-availability-zones.md
6165
- name: How-to guides
6266
items:
6367
- name: Automation Account
Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
---
2+
title: Availability zones support for Azure Automation
3+
description: This article provides an overview of Azure availability zones and regions for Azure Automation
4+
keywords: automation availability zones.
5+
services: automation
6+
ms.subservice: process-automation
7+
ms.date: 06/29/2022
8+
ms.topic: conceptual
9+
ms.custom: references_regions
10+
---
11+
12+
# Availability zones support for Azure Automation
13+
14+
Azure Automation uses [Azure availability zones](../availability-zones/az-overview.md#availability-zones) to provide improved resiliency and high availability to a service instance in a specific Azure region.
15+
16+
[Azure availability zones](../availability-zones/az-overview.md#availability-zones) is a
17+
high-availability offering that protects your applications and data from data center failures.
18+
Availability zones are unique physical locations within an Azure region and each region comprises of one or more data center(s) equipped with independent power, cooling, and networking. To ensure resiliency, there needs to be a minimum of three separate zones in all enabled regions.
19+
20+
A zone redundant Automation account automatically distributes traffic to the Automation account through various management operations and runbook jobs amongst the availability zones in the supported region. The replication is handled at the service level to these physically separate zones, making the service resilient to a zone failure with no impact on the availability of the Automation accounts in the same region.
21+
22+
In the event when a zone is down, there's no action required by you to recover from a zone failure and the service would be accessible through the other available zones. The service detects that the zone is down and automatically distributes the traffic to the available zones as needed.
23+
24+
## Availability zone considerations
25+
26+
- In all Availability zone supported regions, the zone redundancy for Automation accounts is enabled by default and it can't be disabled. It requires no action from your end as it's enabled and managed by the service.
27+
- All new Automation accounts with basic SKU are created with zone redundancy natively.
28+
- All existing Automation accounts would become zone redundant automatically. It requires no action from your end.
29+
- In a zone-down scenario, you might expect a brief performance degradation until the service self-healing rebalances the underlying capacity to adjust to healthy zones. This isn't dependent on zone restoration; the service self-healing state will compensate for a lost zone, using the capacity from other zones.
30+
- In a zone-wide failure scenario, you must follow the guidance provided to set up a disaster recovery for Automation accounts in a secondary region.
31+
- Availability zone support for Automation accounts supports only [Process Automation](/azure/automation/overview#process-automation) feature to provide an improved resiliency for runbook automation.
32+
33+
## Supported regions with availability zones
34+
35+
See [Regions and Availability Zones in Azure](/global-infrastructure/geographies/#geographies) for the Azure regions that have availability zones.
36+
Automation accounts currently support the following regions in preview:
37+
38+
- China North 3
39+
- Qatar Central
40+
- West US 2
41+
- East US 2
42+
- East US
43+
- North Europe
44+
- West Europe
45+
- France Central
46+
- Japan East
47+
- UK South
48+
- Southeast Asia
49+
- Australia East
50+
- Central US
51+
- Brazil South
52+
- Germany West Central
53+
- West US 3
54+
55+
## Create a zone redundant Automation account
56+
You can create a zone redundant Automation account using:
57+
- [Azure portal](/azure/automation/automation-create-standalone-account?tabs=azureportal)
58+
- [Azure Resource Manager (ARM) template](/azure/automation/quickstart-create-automation-account-template)
59+
60+
> [!Note]
61+
> There is no option to select or see Availability zone in the creation flow of the Automation Accounts. It’s a default setting enabled and managed at the service level.
62+
63+
## Pricing
64+
65+
There's no additional cost associated to enable the zone redundancy feature in Automation account.
66+
67+
## Service Level Agreement
68+
69+
There is no change to the [Service Level Agreement](https://azure.microsoft.com/support/legal/sla/automation/v1_1/) with the support of Availability zones in Automation Account. The SLA depends on job start time with a guarantee that at least 99.9% of runbook jobs will start within 30 minutes of their planned start times.
70+
71+
## Next steps
72+
73+
- Learn more about [regions that support availability zones](/azure/availability-zones/az-region.md).

0 commit comments

Comments
 (0)