{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/",
        "slug": "dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/"
        },
        "title": "Account for fault-domain alignment when reattaching Premium SSD v2 disks",
        "summary": "Why can repeated disk moves fail while Azure is aligning Premium SSD v2 storage with an availability-set VM?",
        "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": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            },
            {
                "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:30:20+00:00",
        "modified_at": "2026-09-10T00:35:08+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 242,
        "potentially_affected": "Premium SSD v2 availability-set deployments in the supported regions without availability zones, with the required feature registered.",
        "dse_recommendation": "Review fault-domain copy status before repeated reattachment, expansion, or customer-managed-key changes.",
        "primary_source": {
            "name": "Use Premium SSD v2 with VMs in availability set - Azure Virtual Machines | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/use-premium-ssd-v2-with-availability-set",
            "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": "<h2>Source facts</h2>\n<p>In supported nonzonal regions, attaching a Premium SSD v2 disk across fault domains can trigger a background move to align storage with the VM. Only one copy can run per disk; reattachment, expansion, and customer-managed-key changes face documented restrictions during alignment. OptimizedForFrequentAttach skips alignment copies on future attachments. Changing that property on an attached disk first requires detaching it. <a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/use-premium-ssd-v2-with-availability-set\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Confirm regional eligibility and required subscription registration before reviewing this behavior. Identify the disk, destination VM, availability set, and any copy already underway. Distinguish a fault-domain alignment copy from background creation from a snapshot; check the applicable restriction before retrying an operation.</p>\n<h2>DSE recommendation</h2>\n<p>Review fault-domain copy status before repeated reattachment, expansion, or customer-managed-key changes. For workloads that frequently move disks, have the storage and availability owners decide whether skipping future alignment is acceptable. Document that decision as a change in alignment behavior, not a switch that merely makes the same placement finish faster. Schedule any necessary detachment with the application owner.</p>\n<h2>Verification</h2>\n<p>Observe a controlled attachment and reconcile the resulting copy state with the requested follow-up operation. For an approved frequent-attach design, verify the disk property and actual subsequent behavior on a test workload. Preserve disk and VM identifiers, fault-domain context, and measured outcomes. Avoid repeated detach/attach attempts while the documented copy restriction remains unresolved, and confirm application recovery after the authorized move.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/use-premium-ssd-v2-with-availability-set\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Premium SSD v2 with availability-set VMs</a>. Source reviewed September 9, 2026.</p>",
        "content_text": "Source facts\nIn supported nonzonal regions, attaching a Premium SSD v2 disk across fault domains can trigger a background move to align storage with the VM. Only one copy can run per disk; reattachment, expansion, and customer-managed-key changes face documented restrictions during alignment. OptimizedForFrequentAttach skips alignment copies on future attachments. Changing that property on an attached disk first requires detaching it. Microsoft Learn.\nApplicability\nConfirm regional eligibility and required subscription registration before reviewing this behavior. Identify the disk, destination VM, availability set, and any copy already underway. Distinguish a fault-domain alignment copy from background creation from a snapshot; check the applicable restriction before retrying an operation.\nDSE recommendation\nReview fault-domain copy status before repeated reattachment, expansion, or customer-managed-key changes. For workloads that frequently move disks, have the storage and availability owners decide whether skipping future alignment is acceptable. Document that decision as a change in alignment behavior, not a switch that merely makes the same placement finish faster. Schedule any necessary detachment with the application owner.\nVerification\nObserve a controlled attachment and reconcile the resulting copy state with the requested follow-up operation. For an approved frequent-attach design, verify the disk property and actual subsequent behavior on a test workload. Preserve disk and VM identifiers, fault-domain context, and measured outcomes. Avoid repeated detach/attach attempts while the documented copy restriction remains unresolved, and confirm application recovery after the authorized move.\nOfficial references\nMicrosoft Learn: Premium SSD v2 with availability-set VMs. Source reviewed September 9, 2026.",
        "content_markdown": "## Source facts\n\nIn supported nonzonal regions, attaching a Premium SSD v2 disk across fault domains can trigger a background move to align storage with the VM. Only one copy can run per disk; reattachment, expansion, and customer-managed-key changes face documented restrictions during alignment. OptimizedForFrequentAttach skips alignment copies on future attachments. Changing that property on an attached disk first requires detaching it. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/use-premium-ssd-v2-with-availability-set).\n\n## Applicability\n\nConfirm regional eligibility and required subscription registration before reviewing this behavior. Identify the disk, destination VM, availability set, and any copy already underway. Distinguish a fault-domain alignment copy from background creation from a snapshot; check the applicable restriction before retrying an operation.\n\n## DSE recommendation\n\nReview fault-domain copy status before repeated reattachment, expansion, or customer-managed-key changes. For workloads that frequently move disks, have the storage and availability owners decide whether skipping future alignment is acceptable. Document that decision as a change in alignment behavior, not a switch that merely makes the same placement finish faster. Schedule any necessary detachment with the application owner.\n\n## Verification\n\nObserve a controlled attachment and reconcile the resulting copy state with the requested follow-up operation. For an approved frequent-attach design, verify the disk property and actual subsequent behavior on a test workload. Preserve disk and VM identifiers, fault-domain context, and measured outcomes. Avoid repeated detach/attach attempts while the documented copy restriction remains unresolved, and confirm application recovery after the authorized move.\n\n## Official references\n\n[Microsoft Learn: Premium SSD v2 with availability-set VMs](https://learn.microsoft.com/en-us/azure/virtual-machines/use-premium-ssd-v2-with-availability-set). 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-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Account for fault-domain alignment when reattaching Premium SSD v2 disks",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/",
                "headline": "Account for fault-domain alignment when reattaching Premium SSD v2 disks",
                "description": "Why can repeated disk moves fail while Azure is aligning Premium SSD v2 storage with an availability-set VM?",
                "abstract": "Why can repeated disk moves fail while Azure is aligning Premium SSD v2 storage with an availability-set VM?",
                "articleBody": "Source facts\nIn supported nonzonal regions, attaching a Premium SSD v2 disk across fault domains can trigger a background move to align storage with the VM. Only one copy can run per disk; reattachment, expansion, and customer-managed-key changes face documented restrictions during alignment. OptimizedForFrequentAttach skips alignment copies on future attachments. Changing that property on an attached disk first requires detaching it. Microsoft Learn.\nApplicability\nConfirm regional eligibility and required subscription registration before reviewing this behavior. Identify the disk, destination VM, availability set, and any copy already underway. Distinguish a fault-domain alignment copy from background creation from a snapshot; check the applicable restriction before retrying an operation.\nDSE recommendation\nReview fault-domain copy status before repeated reattachment, expansion, or customer-managed-key changes. For workloads that frequently move disks, have the storage and availability owners decide whether skipping future alignment is acceptable. Document that decision as a change in alignment behavior, not a switch that merely makes the same placement finish faster. Schedule any necessary detachment with the application owner.\nVerification\nObserve a controlled attachment and reconcile the resulting copy state with the requested follow-up operation. For an approved frequent-attach design, verify the disk property and actual subsequent behavior on a test workload. Preserve disk and VM identifiers, fault-domain context, and measured outcomes. Avoid repeated detach/attach attempts while the documented copy restriction remains unresolved, and confirm application recovery after the authorized move.\nOfficial references\nMicrosoft Learn: Premium SSD v2 with availability-set VMs. Source reviewed September 9, 2026.",
                "datePublished": "2026-09-10T00:30:20+00:00",
                "dateModified": "2026-09-10T00:35:08+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/"
                },
                "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-096-account-for-fault-domain-alignment-when-reattaching-premium-ssd-v2-disks/#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": "Account for fault-domain alignment when reattaching Premium SSD v2 disks"
                },
                "articleSection": [
                    "IT",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "IT",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 242,
                "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": "Use Premium SSD v2 with VMs in availability set - Azure Virtual Machines | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/use-premium-ssd-v2-with-availability-set"
                }
            }
        ]
    }
}