{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/", "slug": "dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved", "url": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/" }, "title": "Choose the correct allocation path when associating an existing VM with reserved capacity", "summary": "How does associating an existing regional Azure VM differ from the preview path for an existing zonal VM?", "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:25+00:00", "modified_at": "2026-09-10T00:32:00+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 251, "potentially_affected": "Operators associating existing Azure Windows or Linux VMs with capacity reservation groups.", "dse_recommendation": "Classify the existing VM as regional or zonal before approving its reservation-association procedure.", "primary_source": { "name": "Associate a virtual machine to a capacity reservation group - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-associate-vm", "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

An Azure VM references its capacity reservation group through a VM property. Microsoft requires an existing regional VM to be deallocated, associated, and restarted. The documented alternative for associating an existing zonal VM without deallocation is preview. After association and allocation, the reservation’s instance view identifies the VM through virtualMachinesAllocated. Microsoft Learn.

\n

Applicability

\n

Use this check for an existing VM and a specifically identified reservation group in the same subscription. Record the VM’s regional or zonal placement and the intended matching reservation. Do not apply the preview procedure merely because the VM happens to reside in a region that offers zones.

\n

DSE recommendation

\n

Classify the existing VM as regional or zonal before approving its reservation-association procedure. For the regional path, include the interruption and restart in the workload owner’s change plan. If evaluating the zonal preview, obtain an explicit preview-use decision and retain the source conditions with the trial. Separate the request to change the association property from the evidence showing where capacity was actually allocated.

\n

Verification

\n

Inspect the VM’s resulting group reference and the reservation’s instance view. Match the allocated VM identifier to the intended resource rather than relying on a similar display name. For a regional move, also verify the guest and application after restart. If the association exists but the expected allocation evidence is absent, leave the change open and investigate the mismatch before extending the procedure to additional machines.

\n

Official references

\n

Microsoft Learn: Associate a virtual machine to a capacity reservation group. Source reviewed September 9, 2026.

", "content_text": "Source facts\nAn Azure VM references its capacity reservation group through a VM property. Microsoft requires an existing regional VM to be deallocated, associated, and restarted. The documented alternative for associating an existing zonal VM without deallocation is preview. After association and allocation, the reservation’s instance view identifies the VM through virtualMachinesAllocated. Microsoft Learn.\nApplicability\nUse this check for an existing VM and a specifically identified reservation group in the same subscription. Record the VM’s regional or zonal placement and the intended matching reservation. Do not apply the preview procedure merely because the VM happens to reside in a region that offers zones.\nDSE recommendation\nClassify the existing VM as regional or zonal before approving its reservation-association procedure. For the regional path, include the interruption and restart in the workload owner’s change plan. If evaluating the zonal preview, obtain an explicit preview-use decision and retain the source conditions with the trial. Separate the request to change the association property from the evidence showing where capacity was actually allocated.\nVerification\nInspect the VM’s resulting group reference and the reservation’s instance view. Match the allocated VM identifier to the intended resource rather than relying on a similar display name. For a regional move, also verify the guest and application after restart. If the association exists but the expected allocation evidence is absent, leave the change open and investigate the mismatch before extending the procedure to additional machines.\nOfficial references\nMicrosoft Learn: Associate a virtual machine to a capacity reservation group. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nAn Azure VM references its capacity reservation group through a VM property. Microsoft requires an existing regional VM to be deallocated, associated, and restarted. The documented alternative for associating an existing zonal VM without deallocation is preview. After association and allocation, the reservation’s instance view identifies the VM through virtualMachinesAllocated. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-associate-vm).\n\n## Applicability\n\nUse this check for an existing VM and a specifically identified reservation group in the same subscription. Record the VM’s regional or zonal placement and the intended matching reservation. Do not apply the preview procedure merely because the VM happens to reside in a region that offers zones.\n\n## DSE recommendation\n\nClassify the existing VM as regional or zonal before approving its reservation-association procedure. For the regional path, include the interruption and restart in the workload owner’s change plan. If evaluating the zonal preview, obtain an explicit preview-use decision and retain the source conditions with the trial. Separate the request to change the association property from the evidence showing where capacity was actually allocated.\n\n## Verification\n\nInspect the VM’s resulting group reference and the reservation’s instance view. Match the allocated VM identifier to the intended resource rather than relying on a similar display name. For a regional move, also verify the guest and application after restart. If the association exists but the expected allocation evidence is absent, leave the change open and investigate the mismatch before extending the procedure to additional machines.\n\n## Official references\n\n[Microsoft Learn: Associate a virtual machine to a capacity reservation group](https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-associate-vm). 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-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/", "url": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose the correct allocation path when associating an existing VM with reserved capacity", "item": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/", "url": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/", "headline": "Choose the correct allocation path when associating an existing VM with reserved capacity", "description": "How does associating an existing regional Azure VM differ from the preview path for an existing zonal VM?", "abstract": "How does associating an existing regional Azure VM differ from the preview path for an existing zonal VM?", "articleBody": "Source facts\nAn Azure VM references its capacity reservation group through a VM property. Microsoft requires an existing regional VM to be deallocated, associated, and restarted. The documented alternative for associating an existing zonal VM without deallocation is preview. After association and allocation, the reservation’s instance view identifies the VM through virtualMachinesAllocated. Microsoft Learn.\nApplicability\nUse this check for an existing VM and a specifically identified reservation group in the same subscription. Record the VM’s regional or zonal placement and the intended matching reservation. Do not apply the preview procedure merely because the VM happens to reside in a region that offers zones.\nDSE recommendation\nClassify the existing VM as regional or zonal before approving its reservation-association procedure. For the regional path, include the interruption and restart in the workload owner’s change plan. If evaluating the zonal preview, obtain an explicit preview-use decision and retain the source conditions with the trial. Separate the request to change the association property from the evidence showing where capacity was actually allocated.\nVerification\nInspect the VM’s resulting group reference and the reservation’s instance view. Match the allocated VM identifier to the intended resource rather than relying on a similar display name. For a regional move, also verify the guest and application after restart. If the association exists but the expected allocation evidence is absent, leave the change open and investigate the mismatch before extending the procedure to additional machines.\nOfficial references\nMicrosoft Learn: Associate a virtual machine to a capacity reservation group. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:31:25+00:00", "dateModified": "2026-09-10T00:32:00+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/" }, "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-031-choose-the-correct-allocation-path-when-associating-an-existing-vm-with-reserved/#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": "Choose the correct allocation path when associating an existing VM with reserved capacity" }, "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": 251, "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": "Associate a virtual machine to a capacity reservation group - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-associate-vm" } } ] } }