> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Switch Non-Production Storage Accounts to Locally Redundant Storage

> Change non-production Azure storage accounts from geo-redundant to locally redundant storage (LRS).

Geo-redundant storage (GRS, RA-GRS, GZRS and RA-GZRS) keeps a second copy of your data in a paired region and costs more per GB than locally redundant storage (LRS). Development and test data rarely needs a copy in another region. nOps finds non-production storage accounts on geo-redundant storage and estimates the saving from switching them to LRS.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Storage |
| **Service** | Azure Storage |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

Storage accounts are often created with the geo-redundant default, or copied from production templates, and keep paying for a second region nobody needs.

## How nOps finds it

nOps reads your pay-as-you-go storage billing for geo-redundant capacity, across blob tiers, files, tables, queues and page blobs. An account is flagged when that capacity was billed on at least 7 of the last 14 complete days and the account is non-production. An account counts as non-production when a word in its resource ID (resource group or resource name) marks it as non-production, such as dev, test, qa, staging, uat, sandbox, demo or poc, and no word marks it as production (prod, production, prd, live, main or master). Databricks workspace storage is left out. The saving is the geo-redundant capacity cost over the last 7 days, scaled to a month, times the difference between the LRS and current list prices for the same region, product and tier. Geo write charges and replication transfer also stop but are not counted. It must be at least \$5 a month.

## Before you start

Confirmation that the account is non-production and that its data can be recreated or restored without a second region. Permission to change the storage account.

## How to implement

1. Confirm the account is non-production and does not need a copy in another region.
2. For GRS or RA-GRS, open the storage account in the Azure portal, go to **Redundancy** and choose **Locally-redundant storage (LRS)**, or run `az storage account update --resource-group MY_RG --name MYACCOUNT --sku Standard_LRS`.
3. For GZRS or RA-GZRS, request a conversion (**Redundancy** page) or move to ZRS first, because the switch cannot be made directly.
4. Update Terraform, Bicep or ARM templates so a later deployment does not change it back.

## Risks and considerations

* You lose the copy in the paired region, read access to it and account failover.
* nOps decides an account is non-production from its name. Check the classification before changing anything.
* You can switch back to geo-redundant storage later. Azure then copies the data to the paired region again, which takes time.

## FAQs

> [accordion] How does nOps know an account is non-production?
>
> From words in its resource group or account name, such as dev, test or staging. A production word such as prod always wins.

## Related

* [Use Locally Redundant Storage for Non-Production Backup Vaults](https://help.nops.io/inform/supported-recommendations/use-locally-redundant-storage-for-non-production-backup-vaults)
* [Use Zone-Redundant Backup Storage for Azure SQL](https://help.nops.io/inform/supported-recommendations/use-zone-redundant-backup-storage-for-azure-sql)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.