Azure-docs: Azure VNET Max IP

[markgar]

Azure ARM VNET Max IP is now ~16000. You mention multiple times that it is ~4000. Still true for Classic VNETs, but not ARM. https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#networking-limits

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 22ad4873-c73d-4b90-2063-927a1060d2a2
• Version Independent ID: 8e6643ad-7333-a786-8712-3d17291e12a7
• Content: Network configuration in Azure Kubernetes Service (AKS)
• Content Source: articles/aks/networking-overview.md
• Service: container-service
• Product: unspecified
• GitHub Login: @mmacy
• Microsoft Alias: marsma

[mimckitt]

@markgar I am still seeing it at 4096 in the subscription quota and limits doc

https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#networking-limits

@mmacy are you able to confirm this new limit? I can update both docs if that is the case.

[mmacy]

I believe this is an AKS-specific limit, but adding @slack and @aanandr for confirmation or correction.

[aanandr]

The VNet limit has indeed gone up to 16k but need to find out if AKS has any checks to retrict to 4096. I am checking.

[mimckitt]

@aanandr any update on this?

[aanandr]

Hi - I checked with the AKS team and learnt that there arent any checks to restrict the no. of IPs to 4096. So you should be able to use the entire range of 16K. However, a few things to keep in mind

1. 16K is default, so new VNets will automatically get it. Existing ones should also get it but customers whose quote was bumped to 8K will have to move to new default.
2. The max pods you can have in a node is 256. So please keep this in mind when designing the cluster.
3. As you probably know, the pods/node and nodes per cluster are configurable through templates only, today.

I will be updating the documentation to reflect the 16K limit.

[mimckitt]

thanks @aanandr !

[mmacy]

Hey @MicahMcKittrick-MSFT, this was fixed along with some other items in azure-docs-pr 46699--this issue can be closed. Thanks! -MM

please-close