{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/", "slug": "dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions", "url": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/" }, "title": "Allow for the hold between Azure Storage redundancy conversions", "summary": "Schedule multi-step redundancy changes around actual conversion completion and the documented waiting period.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:29:40+00:00", "modified_at": "2026-09-10T00:52:39+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 235, "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.", "primary_source": { "name": "Change how a storage account is replicated - Azure Storage | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/common/redundancy-migration", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Change how a storage account is replicated. Source retrieved September 9, 2026.

", "content_text": "Source facts\nMicrosoft’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.\nMicrosoft 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.\nApplicability\nFirst 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.\nDSE recommendation\nDSE 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.\nVerification\nInspect 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.\nOfficial references\nMicrosoft Learn: Change how a storage account is replicated. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nMicrosoft’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.\n\nMicrosoft 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).\n\n## Applicability\n\nFirst 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nInspect 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.\n\n## Official references\n\n[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." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/", "url": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Allow for the hold between Azure Storage redundancy conversions", "item": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/", "url": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/", "headline": "Allow for the hold between Azure Storage redundancy conversions", "description": "Schedule multi-step redundancy changes around actual conversion completion and the documented waiting period.", "abstract": "Schedule multi-step redundancy changes around actual conversion completion and the documented waiting period.", "articleBody": "Source facts\nMicrosoft’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.\nMicrosoft 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.\nApplicability\nFirst 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.\nDSE recommendation\nDSE 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.\nVerification\nInspect 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.\nOfficial references\nMicrosoft Learn: Change how a storage account is replicated. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:29:40+00:00", "dateModified": "2026-09-10T00:52:39+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-136-allow-for-the-hold-between-azure-storage-redundancy-conversions/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Allow for the hold between Azure Storage redundancy conversions" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 235, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Change how a storage account is replicated - Azure Storage | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/common/redundancy-migration" } } ] } }