AzureRetirement
Azure Load Balancer: Inbound NAT pools retirement
Retirement date for Inbound NAT pools in Azure Load Balancer (port forwarding to Virtual Machine Scale Set instances): 30 Sep 2027. New Inbound NAT pools cannot be created from November 15, 2026. Single-VM Inbound NAT rules version 1 are not affected.
Retires , 30 Sep 2027
What breaks
Inbound NAT pools in Azure Load Balancer, which forward ports to Virtual Machine Scale Set instances, are retired on 30 Sep 2027. Existing configuration continues to function until that date. Starting November 15, 2026, new Inbound NAT pools cannot be created. Inbound NAT rules version 1 that forward ports to a single virtual machine are not affected.
What to do
Microsoft recommends that you migrate to Inbound NAT rules version 2 in Azure Load Balancer by the retirement date.
Replacement
Inbound NAT rules version 2
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourcelearn.microsoft.comOfficial
Last checked against the first source in this list on .
Related
- , 1 Sep 2027Azure Load Balancer: numberOfProbes property end of supportSource
- , 18 Aug 2026Microsoft Defender for Cloud: retirement in Azure operated by 21VianetSource
- , 14 Sep 2026Azure Functions: runtime version 1.x end of supportSource
- , 14 Sep 2026Azure Monitor: AKS-Engine monitoring retirementSource
- , 15 Sep 2026Azure Maps: Gen1 price tier (Standard S0 and S1) retirementSource
- , 15 Sep 2026Azure Monitor: Activity Logs legacy solution retirementSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item