Azure Dev/Test Storage Using GRS Replication
Geo-redundant storage costs more than locally-redundant precisely because it keeps a second regional copy, a copy a dev/test account will never fail over to.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Change storage account replication to LRS. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight applies a lifecycle policy, then checks the change took.
- Applies to
- Storage Accounts on Azure
- The fix, by hand
- Confirm the resource is genuinely non-production. GRS provides cross-region durability that prod usually wants to keep.
- Storage account → Settings → Configuration.
- Change Replication from GRS (or RA-GRS / GZRS) to LRS.
- Save; the change is online and starts the replication-type transition asynchronously.
- Update your DR / RPO documentation to reflect the lower redundancy level.
- If you only need zonal redundancy, ZRS is a middle ground worth considering before going all the way to LRS.
ZopNight does this for you after a guided review.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1324- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.