Update geo-redundancy and zone-redundancy charge details#128476
Update geo-redundancy and zone-redundancy charge details#128476thiruma0203 wants to merge 1 commit into
Conversation
Clarified charges related to geo-redundancy and zone-redundancy removal.
|
@thiruma0203 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 485ee51: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Clarifies billing behavior when removing geo-redundancy and/or zone-redundancy for Azure Storage redundancy conversions.
Changes:
- Expands the “no charges when you remove…” statement to include zone-redundancy removal.
- Adds additional redundancy conversion examples (including ZRS → LRS and GZRS → GRS) to the “no charges” statement.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| You incur no charges when you **remove** geo-redundancy or zone-redundancy, such as converting **GRS** → **LRS**, **GZRS** → **ZRS**, **ZRS** → **LRS** or **GZRS** → **GRS**. | ||
|
|
|
Hi @thiruma0203 - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you! Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
|
@v-dirichards Thank you for checking, and my apologies for putting PR on wrong path. Should I cancel this PR and work on private repo? |
Yes, for a faster review we would certainly encourage you to move these changes to the private repository and close this PR. |
Clarified charges related to geo-redundancy and zone-redundancy removal.