{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/", "slug": "dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm", "url": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/" }, "title": "Keep all NIC subnets in one virtual network when designing a Windows Azure VM", "summary": "DSE recommends drawing each NIC-to-subnet relationship and recording the common virtual network before selecting the VM size.", "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/" } ], "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-17T16:32:10+00:00", "modified_at": "2026-09-17T16:46:29+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 211, "potentially_affected": "Use this review when a Windows Azure VM design calls for separate front-end and back-end subnets or an additional network interface on an existing machine.", "dse_recommendation": "DSE recommends drawing each NIC-to-subnet relationship and recording the common virtual network before selecting the VM size.", "primary_source": { "name": "Create and manage Windows VMs in Azure that use multiple NICs - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/windows/multiple-nics", "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 multi-NIC Windows VM guide requires all attached NIC subnets to belong to the same virtual network. The supported number of NICs depends on the VM size. Adding a NIC to an existing VM requires deallocating it before attachment and starting it afterward. Microsoft Learn

\n

Applicability

\n

Use this review when a Windows Azure VM design calls for separate front-end and back-end subnets or an additional network interface on an existing machine.

\n

DSE recommendation

\n

DSE recommends drawing each NIC-to-subnet relationship and recording the common virtual network before selecting the VM size. Verify the intended interface count and decide which NIC is primary. For an existing VM, have the workload owner approve the deallocation window and recovery approach. Include the required guest routing review in the implementation plan, and avoid treating a NIC attachment as proof that the intended application traffic path is ready.

\n

Verification

\n

Inspect the deployed NICs, subnet identifiers, VM size, and primary-interface designation against the approved diagram. After the authorized restart, check the guest routes and test each intended application path. Record any unexpected path or connectivity result and resolve it before declaring the additional interface operational.

\n

Official references

\n", "content_text": "Source facts\nMicrosoft’s multi-NIC Windows VM guide requires all attached NIC subnets to belong to the same virtual network. The supported number of NICs depends on the VM size. Adding a NIC to an existing VM requires deallocating it before attachment and starting it afterward. Microsoft Learn\nApplicability\nUse this review when a Windows Azure VM design calls for separate front-end and back-end subnets or an additional network interface on an existing machine.\nDSE recommendation\nDSE recommends drawing each NIC-to-subnet relationship and recording the common virtual network before selecting the VM size. Verify the intended interface count and decide which NIC is primary. For an existing VM, have the workload owner approve the deallocation window and recovery approach. Include the required guest routing review in the implementation plan, and avoid treating a NIC attachment as proof that the intended application traffic path is ready.\nVerification\nInspect the deployed NICs, subnet identifiers, VM size, and primary-interface designation against the approved diagram. After the authorized restart, check the guest routes and test each intended application path. Record any unexpected path or connectivity result and resolve it before declaring the additional interface operational.\nOfficial references\n\nMicrosoft: Create and manage Windows VMs in Azure that use multiple NICs – Azure Virtual Machines | Microsoft Learn", "content_markdown": "## Source facts\n\nMicrosoft’s multi-NIC Windows VM guide requires all attached NIC subnets to belong to the same virtual network. The supported number of NICs depends on the VM size. Adding a NIC to an existing VM requires deallocating it before attachment and starting it afterward. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/windows/multiple-nics)\n\n## Applicability\n\nUse this review when a Windows Azure VM design calls for separate front-end and back-end subnets or an additional network interface on an existing machine.\n\n## DSE recommendation\n\nDSE recommends drawing each NIC-to-subnet relationship and recording the common virtual network before selecting the VM size. Verify the intended interface count and decide which NIC is primary. For an existing VM, have the workload owner approve the deallocation window and recovery approach. Include the required guest routing review in the implementation plan, and avoid treating a NIC attachment as proof that the intended application traffic path is ready.\n\n## Verification\n\nInspect the deployed NICs, subnet identifiers, VM size, and primary-interface designation against the approved diagram. After the authorized restart, check the guest routes and test each intended application path. Record any unexpected path or connectivity result and resolve it before declaring the additional interface operational.\n\n## Official references\n\n- [Microsoft: Create and manage Windows VMs in Azure that use multiple NICs – Azure Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/windows/multiple-nics)" }, "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-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/", "url": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Keep all NIC subnets in one virtual network when designing a Windows Azure VM", "item": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/", "url": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/", "headline": "Keep all NIC subnets in one virtual network when designing a Windows Azure VM", "description": "DSE recommends drawing each NIC-to-subnet relationship and recording the common virtual network before selecting the VM size.", "abstract": "DSE recommends drawing each NIC-to-subnet relationship and recording the common virtual network before selecting the VM size.", "articleBody": "Source facts\nMicrosoft’s multi-NIC Windows VM guide requires all attached NIC subnets to belong to the same virtual network. The supported number of NICs depends on the VM size. Adding a NIC to an existing VM requires deallocating it before attachment and starting it afterward. Microsoft Learn\nApplicability\nUse this review when a Windows Azure VM design calls for separate front-end and back-end subnets or an additional network interface on an existing machine.\nDSE recommendation\nDSE recommends drawing each NIC-to-subnet relationship and recording the common virtual network before selecting the VM size. Verify the intended interface count and decide which NIC is primary. For an existing VM, have the workload owner approve the deallocation window and recovery approach. Include the required guest routing review in the implementation plan, and avoid treating a NIC attachment as proof that the intended application traffic path is ready.\nVerification\nInspect the deployed NICs, subnet identifiers, VM size, and primary-interface designation against the approved diagram. After the authorized restart, check the guest routes and test each intended application path. Record any unexpected path or connectivity result and resolve it before declaring the additional interface operational.\nOfficial references\n\nMicrosoft: Create and manage Windows VMs in Azure that use multiple NICs – Azure Virtual Machines | Microsoft Learn", "datePublished": "2026-09-17T16:32:10+00:00", "dateModified": "2026-09-17T16:46:29+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/" }, "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-20260917-170-keep-all-nic-subnets-in-one-virtual-network-when-designing-a-windows-azure-vm/#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": "Keep all NIC subnets in one virtual network when designing a Windows Azure VM" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 211, "timeRequired": "PT1M", "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": "Create and manage Windows VMs in Azure that use multiple NICs - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/windows/multiple-nics" } } ] } }