From 485ee51c76d2c90368f2233c14623be4cd3520e9 Mon Sep 17 00:00:00 2001 From: thiruma0203 Date: Fri, 8 May 2026 17:03:58 +0900 Subject: [PATCH] Update geo-redundancy and zone-redundancy charge details Clarified charges related to geo-redundancy and zone-redundancy removal. --- articles/storage/common/storage-redundancy-change-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/storage/common/storage-redundancy-change-faq.md b/articles/storage/common/storage-redundancy-change-faq.md index ffbd5bfe19472..49d03ced26dda 100644 --- a/articles/storage/common/storage-redundancy-change-faq.md +++ b/articles/storage/common/storage-redundancy-change-faq.md @@ -84,7 +84,7 @@ There are no initial costs for making zonal conversions. However, after an accou When you **add** geo-redundancy, the resulting geo conversion incurs a [geo-replication data transfer charge](https://azure.microsoft.com/pricing/details/storage/blobs/) at the time of the change. This transfer charge applies because your entire storage account is being replicated to a secondary region. Because all subsequent write operations are also replicated to the secondary region, they too are subject to the data transfer charge. -You incur no charges when you **remove** geo-redundancy, such as converting **GRS** → **LRS** or **GZRS** → **ZRS**. +You incur no charges when you **remove** geo-redundancy or zone-redundancy, such as converting **GRS** → **LRS**, **GZRS** → **ZRS**, **ZRS** → **LRS** or **GZRS** → **GRS**. When you remove read access from a storage account, it continues to incur charges as *RA-GRS* or *RA-GZRS* for 30 days beyond the date on which it was converted. This policy applies to **RA-GRS → GRS** or **RA-GZRS → GZRS**.