{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/",
        "slug": "dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/"
        },
        "title": "Keep Azure public addresses out of guest IP configuration",
        "summary": "Distinguish Azure's public-address translation from private addresses that need matching guest configuration.",
        "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": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "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:28:48+00:00",
        "modified_at": "2026-09-10T00:55:36+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 1,
        "word_count": 218,
        "potentially_affected": "Azure VMs with public or multiple private NIC IP configurations.",
        "dse_recommendation": "Reconcile private address assignments across Azure and the guest, while leaving public-address configuration at the Azure resource layer.",
        "primary_source": {
            "name": "Configure IP addresses for an Azure network interface | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-network-interface-addresses",
            "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>Azure translates a VM&#8217;s private address to its assigned public address. Microsoft says the guest is unaware of that public address and it should not be manually entered in the operating system&#8217;s IP configuration.</p>\n<p>Private multi-address configuration has different requirements. Microsoft&#8217;s guidance calls for manually setting primary and secondary addresses in Windows when adding multiple IPs; for Linux, it calls for configuring the secondary addresses. <a href=\"https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-network-interface-addresses\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Inventory each Azure NIC IP configuration, its private address, any associated public-address resource, and the guest operating system. Review the current OS-specific procedure before editing the adapter, especially for an existing multi-address deployment.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends an address mapping that clearly separates Azure public resources from guest private addresses. Have the network owner approve the mapping and retain an alternate management path before changing a live adapter. Do not copy a portal&#8217;s public address into the guest to troubleshoot an unrelated connectivity failure.</p>\n<h2>Verification</h2>\n<p>After an approved test change, compare Azure&#8217;s private IP assignments with the guest configuration and exercise each intended application binding. Check inbound and outbound behavior through the expected Azure path separately. Preserve the mapping and observed results, and investigate any discrepancy before applying the procedure to additional machines.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-network-interface-addresses\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Configure IP addresses for an Azure network interface</a>. Source retrieved September 9, 2026.</p>",
        "content_text": "Source facts\nAzure translates a VM’s private address to its assigned public address. Microsoft says the guest is unaware of that public address and it should not be manually entered in the operating system’s IP configuration.\nPrivate multi-address configuration has different requirements. Microsoft’s guidance calls for manually setting primary and secondary addresses in Windows when adding multiple IPs; for Linux, it calls for configuring the secondary addresses. Microsoft Learn.\nApplicability\nInventory each Azure NIC IP configuration, its private address, any associated public-address resource, and the guest operating system. Review the current OS-specific procedure before editing the adapter, especially for an existing multi-address deployment.\nDSE recommendation\nDSE recommends an address mapping that clearly separates Azure public resources from guest private addresses. Have the network owner approve the mapping and retain an alternate management path before changing a live adapter. Do not copy a portal’s public address into the guest to troubleshoot an unrelated connectivity failure.\nVerification\nAfter an approved test change, compare Azure’s private IP assignments with the guest configuration and exercise each intended application binding. Check inbound and outbound behavior through the expected Azure path separately. Preserve the mapping and observed results, and investigate any discrepancy before applying the procedure to additional machines.\nOfficial references\nMicrosoft Learn: Configure IP addresses for an Azure network interface. Source retrieved September 9, 2026.",
        "content_markdown": "## Source facts\n\nAzure translates a VM’s private address to its assigned public address. Microsoft says the guest is unaware of that public address and it should not be manually entered in the operating system’s IP configuration.\n\nPrivate multi-address configuration has different requirements. Microsoft’s guidance calls for manually setting primary and secondary addresses in Windows when adding multiple IPs; for Linux, it calls for configuring the secondary addresses. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-network-interface-addresses).\n\n## Applicability\n\nInventory each Azure NIC IP configuration, its private address, any associated public-address resource, and the guest operating system. Review the current OS-specific procedure before editing the adapter, especially for an existing multi-address deployment.\n\n## DSE recommendation\n\nDSE recommends an address mapping that clearly separates Azure public resources from guest private addresses. Have the network owner approve the mapping and retain an alternate management path before changing a live adapter. Do not copy a portal’s public address into the guest to troubleshoot an unrelated connectivity failure.\n\n## Verification\n\nAfter an approved test change, compare Azure’s private IP assignments with the guest configuration and exercise each intended application binding. Check inbound and outbound behavior through the expected Azure path separately. Preserve the mapping and observed results, and investigate any discrepancy before applying the procedure to additional machines.\n\n## Official references\n\n[Microsoft Learn: Configure IP addresses for an Azure network interface](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-network-interface-addresses). Source retrieved 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-188-keep-azure-public-addresses-out-of-guest-ip-configuration/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Keep Azure public addresses out of guest IP configuration",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/",
                "headline": "Keep Azure public addresses out of guest IP configuration",
                "description": "Distinguish Azure's public-address translation from private addresses that need matching guest configuration.",
                "abstract": "Distinguish Azure's public-address translation from private addresses that need matching guest configuration.",
                "articleBody": "Source facts\nAzure translates a VM’s private address to its assigned public address. Microsoft says the guest is unaware of that public address and it should not be manually entered in the operating system’s IP configuration.\nPrivate multi-address configuration has different requirements. Microsoft’s guidance calls for manually setting primary and secondary addresses in Windows when adding multiple IPs; for Linux, it calls for configuring the secondary addresses. Microsoft Learn.\nApplicability\nInventory each Azure NIC IP configuration, its private address, any associated public-address resource, and the guest operating system. Review the current OS-specific procedure before editing the adapter, especially for an existing multi-address deployment.\nDSE recommendation\nDSE recommends an address mapping that clearly separates Azure public resources from guest private addresses. Have the network owner approve the mapping and retain an alternate management path before changing a live adapter. Do not copy a portal’s public address into the guest to troubleshoot an unrelated connectivity failure.\nVerification\nAfter an approved test change, compare Azure’s private IP assignments with the guest configuration and exercise each intended application binding. Check inbound and outbound behavior through the expected Azure path separately. Preserve the mapping and observed results, and investigate any discrepancy before applying the procedure to additional machines.\nOfficial references\nMicrosoft Learn: Configure IP addresses for an Azure network interface. Source retrieved September 9, 2026.",
                "datePublished": "2026-09-10T00:28:48+00:00",
                "dateModified": "2026-09-10T00:55:36+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-188-keep-azure-public-addresses-out-of-guest-ip-configuration/"
                },
                "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-188-keep-azure-public-addresses-out-of-guest-ip-configuration/#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 Azure public addresses out of guest IP configuration"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 218,
                "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": "Configure IP addresses for an Azure network interface | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-network-interface-addresses"
                }
            }
        ]
    }
}