{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/", "slug": "dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted", "url": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/" }, "title": "Treat per-disk resiliency as application-visible I/O failure, not uninterrupted disk access", "summary": "What must an application tolerate when Azure's per-disk resiliency preview keeps its VM running?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "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:31:00+00:00", "modified_at": "2026-09-10T00:35:07+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 246, "potentially_affected": "Eligible Azure VMs created on or after August 15, 2026 in a documented preview region, using data disks without Write Accelerator.", "dse_recommendation": "Require an application-specific response to disk disappearance before evaluating this preview.", "primary_source": { "name": "Improve workload availability with per-disk resiliency (preview) - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-per-disk-resiliency", "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

With the per-disk resiliency preview enabled, Azure can detach a delayed data disk while leaving its VM running, then reattach it after the platform issue resolves. I/O fails while the guest cannot access the disk. The VM reports Degraded, while the portal can still show the disk attached. The feature excludes OS disks, Write Accelerator VMs, and VMs created before August 15, 2026; it is region-limited. Restore points, Azure Backup, and Site Recovery do not preserve its setting. Microsoft Learn.

\n

Applicability

\n

Confirm preview eligibility and authorization first. Enablement must occur while the VM is deallocated or before disk attachment, not during VM or scale-set creation. Identify the affected application’s behavior when a required disk temporarily disappears.

\n

DSE recommendation

\n

Require an application-specific response to disk disappearance before evaluating this preview. Ask the workload owner to distinguish the benefit of keeping unrelated work running from the recovery needs of the disk-dependent component. Document error handling, operator escalation, and the decision to resume disk-dependent work. Add the setting to post-restore configuration checks rather than assuming recovery preserves it.

\n

Verification

\n

Use an approved nonproduction validation plan to compare platform health, guest disk visibility, and application behavior. Preserve observed I/O errors and recovery results without claiming the platform threshold can be chosen or that reattachment proves application consistency. After any restore rehearsal, inspect the actual disk setting before treating the original resiliency design as restored.

\n

Official references

\n

Microsoft Learn: Improve workload availability with per-disk resiliency preview. Source reviewed September 9, 2026.

", "content_text": "Source facts\nWith the per-disk resiliency preview enabled, Azure can detach a delayed data disk while leaving its VM running, then reattach it after the platform issue resolves. I/O fails while the guest cannot access the disk. The VM reports Degraded, while the portal can still show the disk attached. The feature excludes OS disks, Write Accelerator VMs, and VMs created before August 15, 2026; it is region-limited. Restore points, Azure Backup, and Site Recovery do not preserve its setting. Microsoft Learn.\nApplicability\nConfirm preview eligibility and authorization first. Enablement must occur while the VM is deallocated or before disk attachment, not during VM or scale-set creation. Identify the affected application’s behavior when a required disk temporarily disappears.\nDSE recommendation\nRequire an application-specific response to disk disappearance before evaluating this preview. Ask the workload owner to distinguish the benefit of keeping unrelated work running from the recovery needs of the disk-dependent component. Document error handling, operator escalation, and the decision to resume disk-dependent work. Add the setting to post-restore configuration checks rather than assuming recovery preserves it.\nVerification\nUse an approved nonproduction validation plan to compare platform health, guest disk visibility, and application behavior. Preserve observed I/O errors and recovery results without claiming the platform threshold can be chosen or that reattachment proves application consistency. After any restore rehearsal, inspect the actual disk setting before treating the original resiliency design as restored.\nOfficial references\nMicrosoft Learn: Improve workload availability with per-disk resiliency preview. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nWith the per-disk resiliency preview enabled, Azure can detach a delayed data disk while leaving its VM running, then reattach it after the platform issue resolves. I/O fails while the guest cannot access the disk. The VM reports Degraded, while the portal can still show the disk attached. The feature excludes OS disks, Write Accelerator VMs, and VMs created before August 15, 2026; it is region-limited. Restore points, Azure Backup, and Site Recovery do not preserve its setting. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-per-disk-resiliency).\n\n## Applicability\n\nConfirm preview eligibility and authorization first. Enablement must occur while the VM is deallocated or before disk attachment, not during VM or scale-set creation. Identify the affected application’s behavior when a required disk temporarily disappears.\n\n## DSE recommendation\n\nRequire an application-specific response to disk disappearance before evaluating this preview. Ask the workload owner to distinguish the benefit of keeping unrelated work running from the recovery needs of the disk-dependent component. Document error handling, operator escalation, and the decision to resume disk-dependent work. Add the setting to post-restore configuration checks rather than assuming recovery preserves it.\n\n## Verification\n\nUse an approved nonproduction validation plan to compare platform health, guest disk visibility, and application behavior. Preserve observed I/O errors and recovery results without claiming the platform threshold can be chosen or that reattachment proves application consistency. After any restore rehearsal, inspect the actual disk setting before treating the original resiliency design as restored.\n\n## Official references\n\n[Microsoft Learn: Improve workload availability with per-disk resiliency preview](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-per-disk-resiliency). Source reviewed 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-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/", "url": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Treat per-disk resiliency as application-visible I/O failure, not uninterrupted disk access", "item": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/", "url": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/", "headline": "Treat per-disk resiliency as application-visible I/O failure, not uninterrupted disk access", "description": "What must an application tolerate when Azure's per-disk resiliency preview keeps its VM running?", "abstract": "What must an application tolerate when Azure's per-disk resiliency preview keeps its VM running?", "articleBody": "Source facts\nWith the per-disk resiliency preview enabled, Azure can detach a delayed data disk while leaving its VM running, then reattach it after the platform issue resolves. I/O fails while the guest cannot access the disk. The VM reports Degraded, while the portal can still show the disk attached. The feature excludes OS disks, Write Accelerator VMs, and VMs created before August 15, 2026; it is region-limited. Restore points, Azure Backup, and Site Recovery do not preserve its setting. Microsoft Learn.\nApplicability\nConfirm preview eligibility and authorization first. Enablement must occur while the VM is deallocated or before disk attachment, not during VM or scale-set creation. Identify the affected application’s behavior when a required disk temporarily disappears.\nDSE recommendation\nRequire an application-specific response to disk disappearance before evaluating this preview. Ask the workload owner to distinguish the benefit of keeping unrelated work running from the recovery needs of the disk-dependent component. Document error handling, operator escalation, and the decision to resume disk-dependent work. Add the setting to post-restore configuration checks rather than assuming recovery preserves it.\nVerification\nUse an approved nonproduction validation plan to compare platform health, guest disk visibility, and application behavior. Preserve observed I/O errors and recovery results without claiming the platform threshold can be chosen or that reattachment proves application consistency. After any restore rehearsal, inspect the actual disk setting before treating the original resiliency design as restored.\nOfficial references\nMicrosoft Learn: Improve workload availability with per-disk resiliency preview. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:31:00+00:00", "dateModified": "2026-09-10T00:35:07+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/" }, "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-056-treat-per-disk-resiliency-as-application-visible-i-o-failure-not-uninterrupted/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Treat per-disk resiliency as application-visible I/O failure, not uninterrupted disk access" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 246, "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": "Improve workload availability with per-disk resiliency (preview) - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-per-disk-resiliency" } } ] } }