Create Pull Request
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 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 | cancelled |
Biased
|
### 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)