Question 1

What's the difference between Read-Access Geo-Redundant Storage (RA-GRS) and Geo-Redundant Storage (GRS)?

Accepted Answer

Both replicate your data to a secondary Azure region. With GRS, the secondary copy isn’t available for you to read unless Microsoft initiates a failover. With RA-GRS, Azure also provides a read-only endpoint in the secondary region so your application can read from the secondary copy (for example, during a primary-region outage or for read-only workloads).

Question 2

When should I use Read-Access Geo-Redundant Storage (RA-GRS)?

Accepted Answer

Use RA-GRS when you need cross-region disaster recovery plus the ability to keep serving read requests if the primary region is unavailable. It’s a good fit for read-heavy, mostly static data (images, documents, backups, software downloads) where read-only access is acceptable during an incident. If you need low-latency reads in multiple regions all the time, consider designs that actively route users to the nearest region (often with a CDN or multi-region architecture) rather than relying only on the secondary read endpoint.

Question 3

How much does Read-Access Geo-Redundant Storage cost?

Accepted Answer

RA-GRS typically costs more than LRS or GRS because it stores additional copies in a secondary region and enables read access to that secondary copy. Your total cost depends on stored data size, write operations (replication increases the amount of data written), read operations (including reads from the secondary endpoint), and data transfer/egress (especially if clients read from a different region). Pricing varies by region and storage tier, so you should estimate using the Azure Pricing Calculator and compare LRS vs GRS vs RA-GRS for your workload.

Read-Access Geo-Redundant Storage

Definition

Real-World Example

Related Terms

Cloud Provider Equivalencies

Explore More Cloud Computing Terms