Allow for the hold between Azure Storage redundancy conversions

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.

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. Source retrieved September 9, 2026.