Azure Storage redundancy

The data in your Microsoft Azure storage account is always replicated to ensure durability and high availability. Azure Storage copies your data so that it is protected from planned and unplanned events, including transient hardware failures, network or power outages, and massive natural disasters. You can choose to replicate your data within the same data center, across zonal data centers within the same region, or across geographically separated regions.

Replication ensures that your storage account meets the Service-Level Agreement (SLA) for Storage even in the face of failures. See the SLA for information about Azure Storage guarantees for durability and availability.

Azure Storage regularly verifies the integrity of data stored using cyclic redundancy checks (CRCs). If data corruption is detected, it is repaired using redundant data. Azure Storage also calculates checksums on all network traffic to detect corruption of data packets when storing or retrieving data.

Choosing a redundancy option

When you create a storage account, you can select one of the following redundancy options:

The following table provides a quick overview of the scope of durability and availability that each replication strategy will provide you for a given type of event (or event of similar impact).

Scenario LRS ZRS GRS/RA-GRS GZRS/RA-GZRS (preview)
Node unavailability within a data center Yes Yes Yes Yes
An entire data center (zonal or non-zonal) becomes unavailable No Yes Yes Yes
A region-wide outage No No Yes Yes
Read access to your data (in a remote, geo-replicated region) in the event of region-wide unavailability No No Yes (with RA-GRS) Yes (with RA-GZRS)
Designed to provide __ durability of objects over a given year1 at least 99.999999999% (11 9's) at least 99.9999999999% (12 9's) at least 99.99999999999999% (16 9's) at least 99.99999999999999% (16 9's)
Supported storage account types2 GPv2, GPv1, BlockBlobStorage, BlobStorage, FileStorage GPv2, BlockBlobStorage, FileStorage GPv2, GPv1, BlobStorage GPv2
Availability SLA for read requests1 At least 99.9% (99% for cool access tier) At least 99.9% (99% for cool access tier) At least 99.9% (99% for cool access tier) for GRS

At least 99.99% (99.9% for cool access tier) for RA-GRS
At least 99.9% (99% for cool access tier) for GZRS

At least 99.99% (99.9% for cool access tier) for RA-GZRS
Availability SLA for write requests1 At least 99.9% (99% for cool access tier) At least 99.9% (99% for cool access tier) At least 99.9% (99% for cool access tier) At least 99.9% (99% for cool access tier)

1 For information about Azure Storage guarantees for durability and availability, see the Azure Storage SLA.

2 For information for storage account types, see Storage account overview.

All data for all types of storage accounts are replicated, including block blobs, append blobs, page blobs, queues, tables, and files.

For pricing information for each redundancy option, see Azure Storage Pricing.


Azure Premium Disk Storage currently supports only locally redundant storage (LRS). Azure Premium Block Blob Storage supports locally redundant storage (LRS) and zone redundant storage (ZRS) in certain regions.

Changing replication strategy

You can change your storage account's replication strategy by using the Azure portal, Azure Powershell, Azure CLI, or one of the Azure Storage client libraries. Changing the replication type of your storage account does not result in down time.


Currently, you cannot use the Azure portal or the Azure Storage client libraries to convert your account to ZRS, GZRS, or RA-GZRS. To migrate your account to ZRS, see Zone-redundant storage (ZRS) for building highly available Azure Storage applications for details. To migrate GZRS or RA-GZRS, see Geo-zone-redundant storage for highly availability and maximum durability (preview) for details.

Are there any costs to changing my account's replication strategy?

It depends on your conversion path. Ordering from least to the most expensive, Azure Storage redundancy offerings LRS, ZRS, GRS, RA-GRS, GZRS, and RA-GZRS. For example, going from LRS to any other type of replication will incur additional charges because you are moving to a more sophisticated redundancy level. Migrating to GRS or RA-GRS will incur an egress bandwidth charge because your data (in your primary region) is being replicated to your remote secondary region. This charge is a one-time cost at initial setup. After the data is copied, there are no further migration charges. You are only charged for replicating any new or updates to existing data. For details on bandwidth charges, see Azure Storage Pricing page.

If you migrate your storage account from GRS to LRS, there is no additional cost, but your replicated data is deleted from the secondary location.

If you migrate your storage account from RA-GRS to GRS or LRS, that account is billed as RA-GRS for an additional 30 days beyond the date that it was converted.

See also