Public Preview: Increased VNet limits for Private Endpoints

Public Preview: Increased VNet limits for Private Endpoints

With High Scale Private Endpoints, you are now able to increase Azure Private Endpoint’s default limits for local and peered virtual networks. Today you are only able to deploy 1,000 private endpoints within a singular Virtual Network. Any attempts to create additional endpoints will result in an error that can only be resolved by either deleting existing private endpoints or raising a support request to increase the current limit.

Additionally, it is recommended that you only deploy up to 4,000 Private Endpoints in total across your peered virtual networks. Infringing on this recommendation may result in connectivity issues with your private endpoint traffic.
If you would like higher limits, it is recommended to upgrade to High Scale Private Endpoints. This will raise private endpoint default limits to 5,000 in a singular VNet and 20,000 across your peered virtual networks.

Regions of Availability:
This feature is available in the following regions:
West Central US, UK South, East Asia, US East, US North. Additional Regions will become available throughout public preview.

Public Preview: Multi-cluster Eviction and Disruption Budgets with Azure Kubernetes Fleet Manager

Operators using Azure Kubernetes Fleet Manager’s Cluster Resource Placement for intelligent execution of multi-cluster workload placement now have additional controls. With the introduction of ClusterResourcePlacementEviction, Fleet Manager’s workload placement provides operators with a way to forcibly remove placed resources from member clusters. When this happens, it is important for operators to be able to control eviction across their Fleet. For this purpose, a newly available ClusterResourcePlacementDisruptionBudget custom resource can help operators ensure that workload availability is maintained in the event of workload eviction.