{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/",
        "slug": "dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/"
        },
        "title": "Reconcile guest disk mappings before converting an Azure VM from SCSI to NVMe",
        "summary": "What guest assumptions must be checked when a VM changes its storage-controller interface?",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "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:30:41+00:00",
        "modified_at": "2026-09-10T00:35:08+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 256,
        "potentially_affected": "Teams preparing supported Linux or Windows Azure VMs for the documented SCSI-to-NVMe conversion.",
        "dse_recommendation": "Record persistent disk identities and boot prerequisites before approving the controller conversion and VM deallocation.",
        "primary_source": {
            "name": "Convert SCSI to NVMe for Linux and Windows VMs - Azure Virtual Machines | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/nvme-linux",
            "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>Changing an Azure VM from SCSI to NVMe changes how the guest uses its disks, not the remote OS or data storage. Device enumeration changes, and Windows data-disk assignments can shift without persistent identifiers. The conversion script stops and deallocates the VM. Microsoft excludes customized VMs whose third-party software can alter boot behavior, storage or filter drivers, or disk enumeration. On v6 sizes, temporary disks start RAW rather than preformatted NTFS. <a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/nvme-linux\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Confirm that the target size, OS, and installed software fit the supported conversion path. Inventory boot configuration, persistent mounts or drive assignments, and temporary-disk initialization. Check the additional preview registration requirement if the selected sizes differ in temporary-disk support.</p>\n<h2>DSE recommendation</h2>\n<p>Record persistent disk identities and boot prerequisites before approving the controller conversion and VM deallocation. Have the application owner identify every path that depends on a disk&#8217;s current enumeration. Review the conversion script and the guest-readiness changes in a representative nonproduction VM. Treat temporary-disk formatting as a separately scoped operation with exact device identification; never apply a blanket formatting step to all newly enumerated disks.</p>\n<h2>Verification</h2>\n<p>After the authorized conversion, inspect both the Azure controller setting and the controller visible inside the guest. Reconcile OS, data, and temporary disks with the original map and test application access. Preserve the documented return command and original size in the change record. Stop on an unexpected disk identity or boot problem before attempting broad automated repairs.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/nvme-linux\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Convert Linux and Windows VMs from SCSI to NVMe</a>. Source reviewed September 9, 2026.</p>",
        "content_text": "Source facts\nChanging an Azure VM from SCSI to NVMe changes how the guest uses its disks, not the remote OS or data storage. Device enumeration changes, and Windows data-disk assignments can shift without persistent identifiers. The conversion script stops and deallocates the VM. Microsoft excludes customized VMs whose third-party software can alter boot behavior, storage or filter drivers, or disk enumeration. On v6 sizes, temporary disks start RAW rather than preformatted NTFS. Microsoft Learn.\nApplicability\nConfirm that the target size, OS, and installed software fit the supported conversion path. Inventory boot configuration, persistent mounts or drive assignments, and temporary-disk initialization. Check the additional preview registration requirement if the selected sizes differ in temporary-disk support.\nDSE recommendation\nRecord persistent disk identities and boot prerequisites before approving the controller conversion and VM deallocation. Have the application owner identify every path that depends on a disk’s current enumeration. Review the conversion script and the guest-readiness changes in a representative nonproduction VM. Treat temporary-disk formatting as a separately scoped operation with exact device identification; never apply a blanket formatting step to all newly enumerated disks.\nVerification\nAfter the authorized conversion, inspect both the Azure controller setting and the controller visible inside the guest. Reconcile OS, data, and temporary disks with the original map and test application access. Preserve the documented return command and original size in the change record. Stop on an unexpected disk identity or boot problem before attempting broad automated repairs.\nOfficial references\nMicrosoft Learn: Convert Linux and Windows VMs from SCSI to NVMe. Source reviewed September 9, 2026.",
        "content_markdown": "## Source facts\n\nChanging an Azure VM from SCSI to NVMe changes how the guest uses its disks, not the remote OS or data storage. Device enumeration changes, and Windows data-disk assignments can shift without persistent identifiers. The conversion script stops and deallocates the VM. Microsoft excludes customized VMs whose third-party software can alter boot behavior, storage or filter drivers, or disk enumeration. On v6 sizes, temporary disks start RAW rather than preformatted NTFS. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/nvme-linux).\n\n## Applicability\n\nConfirm that the target size, OS, and installed software fit the supported conversion path. Inventory boot configuration, persistent mounts or drive assignments, and temporary-disk initialization. Check the additional preview registration requirement if the selected sizes differ in temporary-disk support.\n\n## DSE recommendation\n\nRecord persistent disk identities and boot prerequisites before approving the controller conversion and VM deallocation. Have the application owner identify every path that depends on a disk’s current enumeration. Review the conversion script and the guest-readiness changes in a representative nonproduction VM. Treat temporary-disk formatting as a separately scoped operation with exact device identification; never apply a blanket formatting step to all newly enumerated disks.\n\n## Verification\n\nAfter the authorized conversion, inspect both the Azure controller setting and the controller visible inside the guest. Reconcile OS, data, and temporary disks with the original map and test application access. Preserve the documented return command and original size in the change record. Stop on an unexpected disk identity or boot problem before attempting broad automated repairs.\n\n## Official references\n\n[Microsoft Learn: Convert Linux and Windows VMs from SCSI to NVMe](https://learn.microsoft.com/en-us/azure/virtual-machines/nvme-linux). 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-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Reconcile guest disk mappings before converting an Azure VM from SCSI to NVMe",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/",
                "headline": "Reconcile guest disk mappings before converting an Azure VM from SCSI to NVMe",
                "description": "What guest assumptions must be checked when a VM changes its storage-controller interface?",
                "abstract": "What guest assumptions must be checked when a VM changes its storage-controller interface?",
                "articleBody": "Source facts\nChanging an Azure VM from SCSI to NVMe changes how the guest uses its disks, not the remote OS or data storage. Device enumeration changes, and Windows data-disk assignments can shift without persistent identifiers. The conversion script stops and deallocates the VM. Microsoft excludes customized VMs whose third-party software can alter boot behavior, storage or filter drivers, or disk enumeration. On v6 sizes, temporary disks start RAW rather than preformatted NTFS. Microsoft Learn.\nApplicability\nConfirm that the target size, OS, and installed software fit the supported conversion path. Inventory boot configuration, persistent mounts or drive assignments, and temporary-disk initialization. Check the additional preview registration requirement if the selected sizes differ in temporary-disk support.\nDSE recommendation\nRecord persistent disk identities and boot prerequisites before approving the controller conversion and VM deallocation. Have the application owner identify every path that depends on a disk’s current enumeration. Review the conversion script and the guest-readiness changes in a representative nonproduction VM. Treat temporary-disk formatting as a separately scoped operation with exact device identification; never apply a blanket formatting step to all newly enumerated disks.\nVerification\nAfter the authorized conversion, inspect both the Azure controller setting and the controller visible inside the guest. Reconcile OS, data, and temporary disks with the original map and test application access. Preserve the documented return command and original size in the change record. Stop on an unexpected disk identity or boot problem before attempting broad automated repairs.\nOfficial references\nMicrosoft Learn: Convert Linux and Windows VMs from SCSI to NVMe. Source reviewed September 9, 2026.",
                "datePublished": "2026-09-10T00:30:41+00:00",
                "dateModified": "2026-09-10T00:35:08+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/"
                },
                "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-075-reconcile-guest-disk-mappings-before-converting-an-azure-vm-from-scsi-to-nvme/#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": "Reconcile guest disk mappings before converting an Azure VM from SCSI to NVMe"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Checklist",
                    "Information priority"
                ],
                "genre": "Checklist",
                "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": 256,
                "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": "Convert SCSI to NVMe for Linux and Windows VMs - Azure Virtual Machines | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/nvme-linux"
                }
            }
        ]
    }
}