Edit

Availability zones support for Azure Automation

  • Article

Azure availability zones provides an improved resiliency and high availability to a service instance in a specific Azure region. Azure Automation now supports Availability zones to provide improved resiliency and reliability high availability to the service, runbooks, and other automation assets.

Azure availability zones is a high-availability offering that protects your applications and data from data center failures. 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.

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.

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.

Availability zone considerations

  • 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.
  • All new Automation accounts with basic SKU are created with zone redundancy natively.
  • All existing Automation accounts would become zone redundant automatically. It requires no action from your end.
  • 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.
  • 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.
  • Availability zone support for Automation accounts supports only Process Automation feature to provide an improved resiliency for runbook automation.

Supported regions with availability zones

See Regions and Availability Zones in Azure for the Azure regions that have availability zones. Automation accounts currently support the following regions:

  • Australia East
  • Brazil South
  • Canada Central
  • Central India
  • Central US
  • China North 3
  • East Asia
  • East US
  • East US 2
  • France Central
  • Germany West Central
  • Israel Central
  • Italy North
  • Japan East
  • Korea Central
  • North Europe
  • Norway East
  • Poland Central
  • Qatar Central
  • South Africa North
  • South Central US
  • South East Asia
  • Sweden Central
  • USGov Virginia (Fairfax Private Cloud)
  • UK South
  • West Europe
  • West US 2
  • West US 3

Create a zone redundant Automation account

You can create a zone redundant Automation account using:

Note

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.

Pricing

There's no additional cost associated to enable the zone redundancy feature in Automation account.

Service Level Agreement

There is no change to the Service Level Agreement 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.

Next steps