Skip to main content

Azure Storage Account Failover is now in public preview

Published date: February 05, 2019

Azure Storage Account Failover for customers using geo-redundant storage (GRS) and read-access geo-redundant storage (RA-GRS) accounts is now in public preview. Customers can take advantage of this functionality to control when to failover from the primary to the secondary region of their storage accounts.

If the primary region for your geo-redundant storage account becomes unavailable for an extended period of time, you can force an account failover. When you perform a failover, all data in the storage account is failed over to the secondary region, and the secondary region becomes the new primary region. The DNS records for all storage service endpoints – blob, file, queue, table and Azure Data Lake Storage Gen2 – are updated to point to the new primary region. Once the failover is complete, clients can automatically begin writing data to the storage account using the service endpoints in the new primary region, without any code changes.

Post failover, the storage account is configured to be locally redundant (LRS). To resume replication to the new secondary region, configure the account to use geo-redundant storage again (either RA-GRS or GRS). Keep in mind that converting a locally-redundant (LRS) account to RA-GRS or GRS incurs a cost.

Account failover is supported in preview for new and existing Azure Resource Manager storage accounts that are configured for RA-GRS and GRS. Storage accounts may be general-purpose v1 (GPv1), general-purpose v2 (GPv2), or Blob Storage accounts. Account failover is currently supported in US West 2 and US West Central.

You can initiate account failover using the Azure PortalAzure PowerShellAzure CLI, or the Azure Storage Resource Provider API.

Learn more

  • Storage Accounts
  • Azure Resource Manager
  • Features
  • Management