Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools)
What the source says
Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved performance and is the recommended option for Virtual Machine Scale Sets (VMSS). Understanding the difference: Inbound NAT rules version 1 includes two resource types: Inbound NAT rules version 1: Port forwarding to a single virtual machine. This feature is not affected. Inbound NAT pools: Port forwarding to Virtual Machine Scale Set instances. This feature is retiring. On September 30, 2027, Inbound NAT pools in Azure Load Balancer will be retired. Starting November 15, 2026, you will no longer be able to create new Inbound NAT pools. Existing configuration will continue to function until September 30, 2027. Recommended action: To avoid potential service disruptions, we recommend that you migrate to Inbound NAT rules version 2 in Azure Load Balancer by September 30, 2027.
Who is affected: The audience described by the Microsoft update is represented by: Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved pe
Why it matters: The change matters because the official source describes: Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved pe
Urgency: Monitor
Next action: Review affected accounts with the customer using the official announcement.
Commercial opportunities
Use the verified change to open a scoped customer conversation.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The affected customer scope is unknown and must be confirmed before action.
Reading for it_manager_dsi
Who is affected: The audience described by the Microsoft update is represented by: Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved pe
Why it matters: The change matters because the official source describes: Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved pe
Urgency: Monitor
Next action: Assess technical dependencies and ownership against the official update.
Commercial opportunities
Offer a scoped technical-readiness assessment if the customer confirms impact.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The affected customer scope is unknown and must be confirmed before action.
Reading for partner_channel
Who is affected: The audience described by the Microsoft update is represented by: Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved pe
Why it matters: The change matters because the official source describes: Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved pe
Urgency: Monitor
Next action: Prepare a source-backed customer conversation and confirm the affected estate.
Commercial opportunities
Qualify a partner-led assessment only after customer scope is confirmed.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The affected customer scope is unknown and must be confirmed before action.
Reading for sales_manager
Who is affected: The audience described by the Microsoft update is represented by: Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved pe
Why it matters: The change matters because the official source describes: Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved pe
Urgency: Monitor
Next action: Review portfolio exposure with account owners using the official source.
Commercial opportunities
Prioritize accounts that confirm affected products or workloads.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The affected customer scope is unknown and must be confirmed before action.
Evidence and traceability
Each excerpt is linked to the primary source. Current raw version: 478.
Raw capture : 2026-08-26T14:18:57.653130+00:00 — hash f9996381eefe673f…
Event
Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved performance and is the recommended option for Virtual Machine Scale Sets (VMSS). Understanding the difference: Inbound NAT rules version 1 includes two resource types: Inbound NAT rules version 1: Port forwarding to a single virtual machine. This feature is not affected. Inbound NAT pools: Port forwarding to Virtual Machine Scale Set instances. This feature is retiring. On September 30, 2027, Inbound NAT pools in Azure Load Balancer will be retired. Starting November 15, 2026, you will no longer be able to create new Inbound NAT pools. Existing configuration will continue to function until September 30, 2027. Recommended action: To avoid potential service disruptions, we recommend that you migrate to Inbound NAT rules version 2 in Azure Load Balancer by September 30, 2027.
Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved performance and is the recommended option for Virtual Machine Scale Sets (VMSS). Understanding the difference: Inbound NAT rules version 1 includes two resource types: Inbound NAT rules version 1: Port forwarding to a single virtual machine. This feature is not affected. Inbound NAT pools: Port forwarding to Virtual Machine Scale Set instances. This feature is retiring. On September 30, 2027, Inbound NAT pools in Azure Load Balancer will be retired. Starting November 15, 2026, you will no longer be able to create new Inbound NAT pools. Existing configuration will continue to function until September 30, 2027. Recommended action: To avoid potential service disruptions, we recommend that you migrate to Inbound NAT rules version 2 in Azure Load Balancer by September 30, 2027.
Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved performance and is the recommended option for Virtual Machine Scale Sets (VMSS). Understanding the difference: Inbound NAT rules version 1 includes two resource types: Inbound NAT rules version 1: Port forwarding to a single virtual machine. This feature is not affected. Inbound NAT pools: Port forwarding to Virtual Machine Scale Set instances. This feature is retiring. On September 30, 2027, Inbound NAT pools in Azure Load Balancer will be retired. Starting November 15, 2026, you will no longer be able to create new Inbound NAT pools. Existing configuration will continue to function until September 30, 2027. Recommended action: To avoid potential service disruptions, we recommend that you mig
Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved performance and is the recommended option for Virtual Machine Scale Sets (VMSS). Understanding the difference: Inbound NAT rules version 1 includes two resource types: Inbound NAT rules version 1: Port forwarding to a single virtual machine. This feature is not affected. Inbound NAT pools: Port forwarding to Virtual Machine Scale Set instances. This feature is retiring. On September 30, 2027, Inbound NAT pools in Azure Load Balancer will be retired. Starting November 15, 2026, you will no longer be able to create new Inbound NAT pools. Existing configuration will continue to function until September 30, 2027. Recommended action: To avoid potential service disruptions, we recommend that you mig
Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved performance and is the recommended option for Virtual Machine Scale Sets (VMSS). Understanding the difference: Inbound NAT rules version 1 includes two resource types: Inbound NAT rules version 1: Port forwarding to a single virtual machine. This feature is not affected. Inbound NAT pools: Port forwarding to Virtual Machine Scale Set instances. This feature is retiring. On September 30, 2027, Inbound NAT pools in Azure Load Balancer will be retired. Starting November 15, 2026, you will no longer be able to create new Inbound NAT pools. Existing configuration will continue to function until September 30, 2027. Recommended action: To avoid potential service disruptions, we recommend that you mig
Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools) Update to our previous communication: We previously announced the retirement of all Inbound NAT rules version 1 resources, which included both single-VM NAT rules and NAT pools for Virtual Machine Scale Sets. We have narrowed the scope of this retirement to Inbound NAT pools only. NAT pools are being retired because they provide the same functionality as Inbound NAT rules v2, which offer improved performance and is the recommended option for Virtual Machine Scale Sets (VMSS). Understanding the difference: Inbound NAT rules version 1 includes two resource types: Inbound NAT rules version 1: Port forwarding to a single virtual machine. This feature is not affected. Inbound NAT pools: Port forwarding to Virtual Machine Scale Set instances. This feature is retiring. On September 30, 2027, Inbound NAT pools in Azure Load Balancer will be retired. Starting November 15, 2026, you will no longer be able to create new Inbound NAT pools. Existing configuration will continue to function until September 30, 2027. Recommended action: To avoid potential service disruptions, we recommend that you mig