Private network connectors
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 4bcfa96 · +2 −2 lines · also on GitHub
⋯ 158 unchanged lines
159159
We recommend the following specifications for each Microsoft Entra private network connector:
160160
161161
- **Memory**: 8 GiB or more.
162
−- **CPU**: 4 CPU cores or more.
162
+- **CPU**: Four CPU cores or more.
163163
164164
Keep peak CPU and memory utilization per connector under 70%. If sustained utilization exceeds 70%, add connectors to the group or scale up host capacity to distribute load. Monitor with Windows performance counters to validate that utilization returns to an acceptable range.
165165
166
−You can expect up to ~1.5 Gbps aggregate TCP throughput (combined inbound and outbound) per connector on an Azure VM sized at 4 vCPU and 8 GiB RAM with standard networking. You can achieve higher throughput by using larger VM sizes (more vCPUs, more memory, and accelerated or high-bandwidth NICs), or by adding more connectors in the same group to scale out.
166
+You can expect up to about 1.5-Gbps aggregate TCP throughput (combined inbound and outbound) per connector on an Azure VM sized at four vCPUs and 8 GiB of RAM with standard networking. You can achieve higher throughput by using larger VM sizes (more vCPUs, more memory, and accelerated or high-bandwidth NICs), or by adding more connectors in the same group to scale out.
167167
168168
We derived this performance guidance from controlled lab tests that used iPerf3 TCP data streams in a dedicated test tenant. Actual throughput can vary based on:
169169
⋯ 68 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 9 Oct 22:51 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.