Microsoft Entra ID
General

Connect Ports

In brief

The port tables were updated, including formatting for the HTTPS 443 SSO registration entry and descriptions of required communications.

What Entra admins need to know

Administrators can use the updated tables when reviewing Microsoft Entra Connect network requirements.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Table 3 - Microsoft Entra Connect and AD FS Federation Servers/WAP

This table describes the ports and protocols that are required for communication between the Microsoft Entra Connect server and AD FS Federation/WAP servers.

Protocol Ports Description
The following tables describes the ports and protocols that are required for communication between the Microsoft Entra Connect and Microsoft Entra ID.

Table 6a - Pass-through Authentication with SSO

Protocol Ports Description
HTTP 80 (TCP) Used to download CRLs (Certificate Revocation Lists) to verify TLS/SSL certificates. Also needed for the connector auto-update capability to function properly.
Protocol Ports Description
HTTPS 443 (TCP) Used to enable SSO registration (required only for the SSO registration process).

In addition, Microsoft Entra Connect needs to be able to make direct IP connections to the Azure data center IP ranges. Again, this is only required for the SSO registration process.

Table 7a - Ports and Protocols for Microsoft Entra Connect Health agent for (AD FS/Sync) and Microsoft Entra ID

This table describes the following outbound ports and protocols that are required for communication between the Microsoft Entra Connect Health agents and Microsoft Entra ID.

Protocol Ports Description
Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…