Document Details
Increase Private Endpoint Vnet Limits
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
powershell_heavy
⚠️
windows_first
⚠️
missing_linux_example
Summary:
The documentation demonstrates a Windows bias by providing PowerShell examples and referencing the Azure Portal UI, both of which are more familiar to Windows users. While an Azure CLI example is included, it is presented after PowerShell, and there are no explicit Linux shell (bash) or cross-platform scripting examples. There is also no mention of Linux-specific tools or guidance for Linux administrators.
Recommendations:
- Present Azure CLI (which is cross-platform) examples before PowerShell to avoid implying Windows-first workflows.
- Include bash shell examples for common tasks, especially for validation steps, to assist Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for Linux users where appropriate.
- Where PowerShell is used, clarify if the commands are compatible with PowerShell Core on Linux/macOS, or provide alternative bash/CLI scripts.
- Expand validation instructions to include command-line methods (e.g., using az CLI and jq) for Linux users, not just Portal and PowerShell.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-08 00:00 | #105 | completed | ✅ Clean |
| 2025-08-08 00:00 | #74 | completed | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
Flagged Code Snippets
### Enable High Scale Private Endpoints
To enable this feature, configure *Private Endpoint virtual network Policies*. We recommend enabling this property for all virtual networks you want to include in this feature and for all connected compute virtual networks in peering scenarios.
> [!WARNING]
> Upgrading or downgrading this feature triggers a platform update and results in a one-time connection reset. We recommend performing this action during a maintenance window.
#### [**PowerShell**](#tab/ARG-HSP-Powershell)
---
### Validate configuration
To validate the configuration, verify all necessary properties are set correctly. You can do this by checking the following:
#### [**Portal**](#tab/validate-portal)
1. In the search box at the top of the portal, enter **Virtual network**. Select **Virtual networks**.
1. Select **myVNet**.
1. In settings of **myVNet**, select **Subnets**.
1. Select your subnet.
1. In the **Edit subnet** pane, under **Network Policy for Private Endpoints**, confirm **Route Table** is selected.
1. In the virtual network overview page, select **JSON view** in the top right corner.
1. In the **Resource JSON** pane, select the latest API Version.
1. Validate that the virtual network property *privateEndpointVNetPolicies* is set to **Basic**.
1. Confirm that you can deploy more than 1,000 private endpoints in the respective virtual network.
#### [**PowerShell**](#tab/validate-PowerShell)