Retirement: Azure Load Balancer Inbound NAT rule version 1 for Azure VMSS (aka Inbound NAT Pools)
Ce que dit la source
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.
Qui est concerné : 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
Pourquoi c'est important : 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
Urgence : Surveiller
Prochaine action : Review affected accounts with the customer using the official announcement.
Opportunités commerciales
Use the verified change to open a scoped customer conversation.
Actions techniques
Assess whether the documented change intersects the customer's current stack.
Questions à poser au client
Does this documented change affect a product or workload in scope?
Risques et objections
The official source does not establish facts beyond the quoted material.
Points à confirmer
The affected customer scope is unknown and must be confirmed before action.
Lecture pour it_manager_dsi
Qui est concerné : 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
Pourquoi c'est important : 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
Urgence : Surveiller
Prochaine action : Assess technical dependencies and ownership against the official update.
Opportunités commerciales
Offer a scoped technical-readiness assessment if the customer confirms impact.
Actions techniques
Assess whether the documented change intersects the customer's current stack.
Questions à poser au client
Does this documented change affect a product or workload in scope?
Risques et objections
The official source does not establish facts beyond the quoted material.
Points à confirmer
The affected customer scope is unknown and must be confirmed before action.
Lecture pour partner_channel
Qui est concerné : 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
Pourquoi c'est important : 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
Urgence : Surveiller
Prochaine action : Prepare a source-backed customer conversation and confirm the affected estate.
Opportunités commerciales
Qualify a partner-led assessment only after customer scope is confirmed.
Actions techniques
Assess whether the documented change intersects the customer's current stack.
Questions à poser au client
Does this documented change affect a product or workload in scope?
Risques et objections
The official source does not establish facts beyond the quoted material.
Points à confirmer
The affected customer scope is unknown and must be confirmed before action.
Lecture pour sales_manager
Qui est concerné : 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
Pourquoi c'est important : 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
Urgence : Surveiller
Prochaine action : Review portfolio exposure with account owners using the official source.
Opportunités commerciales
Prioritize accounts that confirm affected products or workloads.
Actions techniques
Assess whether the documented change intersects the customer's current stack.
Questions à poser au client
Does this documented change affect a product or workload in scope?
Risques et objections
The official source does not establish facts beyond the quoted material.
Points à confirmer
The affected customer scope is unknown and must be confirmed before action.
Preuves et traçabilité
Chaque extrait est relié à la source primaire. Version brute courante : 478.
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