# Allow for the hold between Azure Storage redundancy conversions

> Schedule multi-step redundancy changes around actual conversion completion and the documented waiting period.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:29:40+00:00
- Modified: 2026-09-10T00:52:39+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Schedule multi-step redundancy changes around actual conversion completion and the documented waiting period.

## Potentially affected

Azure storage accounts eligible for a zone-redundancy conversion.

## DSE recommendation

Approve a staged transition with completion evidence and the post-conversion waiting period before the next change.

## Article

## Source facts

Microsoft’s general Storage conversion guide specifies at least 24 hours after a zone-redundancy conversion before another redundancy-setting change. Its LRS-to-GZRS example first converts LRS to ZRS, waits, then adds geo-redundancy in a separate operation.

Microsoft does not guarantee when a conversion finishes. Account size, regional demand, and other factors affect timing, so a submitted conversion is not evidence that the new redundancy state is ready. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/common/redundancy-migration).

## Applicability

First confirm that the account type, enabled features, and requested transition support the documented conversion. This article does not set an Azure Files change window; use that service’s own conversion guidance. Record the starting state and desired end state, and confirm the applicable service-specific waiting period before scheduling the next operation.

## DSE recommendation

DSE recommends separating request submission, observed completion, the required waiting period, and the next approved operation in the change plan. Assign an owner to track progress and communicate delays. If a fixed completion deadline is essential, have the architecture owner evaluate alternatives rather than compressing the documented hold.

## Verification

Inspect the actual redundancy configuration and conversion progress after each approved step. Record completion time before calculating the next eligible change, then confirm the final state and workload access. Keep any eligibility warnings with the evidence. Do not substitute an accepted request or a changed portal selection for completed conversion.

## Official references

[Microsoft Learn: Change how a storage account is replicated](https://learn.microsoft.com/en-us/azure/storage/common/redundancy-migration). Source retrieved September 9, 2026.

## Primary reference

- Name: Change how a storage account is replicated - Azure Storage | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/storage/common/redundancy-migration
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Allow for the hold between Azure Storage redundancy conversions,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.