Private network connectors
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit cb832f0 · +11 −14 lines · also on GitHub
⋯ 25 unchanged lines
2626
2727
Deploy at least two connectors for redundancy and scale. The service and connectors handle high availability, and you can add or remove connectors at any time. Each request routes to an available connector. If a connector is unavailable, it doesn't handle traffic. The service tags unused connectors as inactive and removes them after 10 days of inactivity.
2828
29
−
3029
> [!NOTE]
3130
> You can monitor the [version history page](reference-version-history.md) to stay informed on the latest updates so that you can schedule appropriate connector upgrades.
3231
⋯ 22 unchanged lines
5554
## Handling connector server issues
5655
If one or more connector servers are down because of a server, network, or similar outage, follow these steps to maintain continuity:
5756
58
−1. Identify and remove the affected (“bad”) servers from the connector group.
59
−2. Add available healthy servers (“good”) or backup servers into the connector group to restore capacity.
60
−3. Reboot affected servers to drain any pre-existing connections. Existing ongoing connections don’t drain immediately with connector group changes.
57
+1. Identify and remove the affected ("bad") servers from the connector group.
58
+2. Add available healthy servers ("good") or backup servers into the connector group to restore capacity.
59
+3. Reboot affected servers to drain any pre-existing connections. Existing ongoing connections don’t drain immediately with connector group changes.
6160
6261
Use this sequence to keep service stable and minimize disruption when connector servers have issues.
6362
⋯ 51 unchanged lines
115114
Private Network connectors initiate TCP/UDP connections to designated destination endpoints, requiring available source ports on the connector host machine. Expanding the ephemeral port range can improve the availability of source ports, particularly when managing a high volume of concurrent connections.
116115
117116
To view the current dynamic port range on a system, use the following netsh commands:
118
−- netsh int ipv4 show dynamicport tcp
119
−- netsh int ipv4 show dynamicport udp
120
−- netsh int ipv6 show dynamicport tcp
121
−- netsh int ipv6 show dynamicport udp
117
+- `netsh int ipv4 show dynamicport tcp`
118
+- `netsh int ipv4 show dynamicport udp`
119
+- `netsh int ipv6 show dynamicport tcp`
120
+- `netsh int ipv6 show dynamicport udp`
122121
123122
Sample netsh commands to increase the ports
124
−- netsh int ipv4 set dynamicport tcp start=1025 num=64511
125
−- netsh int ipv4 set dynamicport udp start=1025 num=64511
126
−- netsh int ipv6 set dynamicport tcp start=1025 num=64511
127
−- netsh int ipv6 set dynamicport udp start=1025 num=64511
123
+- `netsh int ipv4 set dynamicport tcp start=1025 num=64511`
124
+- `netsh int ipv4 set dynamicport udp start=1025 num=64511`
125
+- `netsh int ipv6 set dynamicport tcp start=1025 num=64511`
126
+- `netsh int ipv6 set dynamicport udp start=1025 num=64511`
128127
129128
These commands set the dynamic port range from 1025 to the maximum of 65535. The minimum start port is 1025.
130129
⋯ 62 unchanged lines
193192
194193
## Inactive connectors
195194
A common issue is that connectors appear as inactive in a connector group. A firewall blocking the required ports is a common cause for inactive connectors.
196
−
197
−
198195
199196
## Next steps
200197
⋯ 4 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.