Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/storage/common/storage-redundancy-change-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -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**.

Comment on lines +87 to 88
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**.

Expand Down