Hybrid Identity Required Ports and Protocols

The following document is a technical reference on the required ports and protocols for implementing a hybrid identity solution. Use the following illustration and refer to the corresponding table.

What is Azure AD Connect

Table 1 - Azure AD Connect and On-premises AD

This table describes the ports and protocols that are required for communication between the Azure AD Connect server and on-premises AD.

Protocol Ports Description
DNS 53 (TCP/UDP) DNS lookups on the destination forest.
Kerberos 88 (TCP/UDP) Kerberos authentication to the AD forest.
MS-RPC 135 (TCP/UDP) Used during the initial configuration of the Azure AD Connect wizard when it binds to the AD forest, and also during Password synchronization.
LDAP 389 (TCP/UDP) Used for data import from AD. Data is encrypted with Kerberos Sign & Seal.
LDAP/SSL 636 (TCP/UDP) Used for data import from AD. The data transfer is signed and encrypted. Only used if you are using SSL.
RPC 49152- 65535 (Random high RPC Port)(TCP/UDP) Used during the initial configuration of Azure AD Connect when it binds to the AD forests, and during Password synchronization. See KB929851, KB832017, and KB224196 for more information.

Table 2 - Azure AD Connect and Azure AD

This table describes the ports and protocols that are required for communication between the Azure AD Connect server and Azure AD.

Protocol Ports Description
HTTP 80 (TCP/UDP) Used to download CRLs (Certificate Revocation Lists) to verify SSL certificates.
HTTPS 443(TCP/UDP) Used to synchronize with Azure AD.

For a list of URLs and IP addresses you need to open in your firewall, see Office 365 URLs and IP address ranges.

Table 3 - Azure AD Connect and AD FS Federation Servers/WAP

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

Protocol Ports Description
HTTP 80 (TCP/UDP) Used to download CRLs (Certificate Revocation Lists) to verify SSL certificates.
HTTPS 443(TCP/UDP) Used to synchronize with Azure AD.
WinRM 5985 WinRM Listener

Table 4 - WAP and Federation Servers

This table describes the ports and protocols that are required for communication between the Federation servers and WAP servers.

Protocol Ports Description
HTTPS 443(TCP/UDP) Used for authentication.

Table 5 - WAP and Users

This table describes the ports and protocols that are required for communication between users and the WAP servers.

Protocol Ports Description
HTTPS 443(TCP/UDP) Used for device authentication.
TCP 49443 (TCP) Used for certificate authentication.

Table 6a & 6b - Pass-through Authentication with Single Sign On (SSO) and Password Hash Sync with Single Sign On (SSO)

The following tables describes the ports and protocols that are required for communication between the Azure AD Connect and Azure AD.

Table 6a - Pass-through Authentication with SSO

Protocol Port Number Description
HTTP 80 Enable outbound HTTP traffic for security validation such as SSL. Also needed for the connector auto-update capability to function properly.
HTTPS 443 Enable outbound HTTPS traffic for operations such as enabling and disabling of the feature, registering connectors, downloading connector updates, and handling all user sign-in requests.

In addition, Azure AD Connect needs to be able to make direct IP connections to the Azure data center IP ranges.

Table 6b - Password Hash Sync with SSO

Protocol Port Number Description
HTTPS 443 Enable SSO registration (required only for the SSO registration process).

In addition, Azure AD 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 & 7b - Azure AD Connect Health agent for (AD FS/Sync) and Azure AD

The following tables describe the endpoints, ports, and protocols that are required for communication between Azure AD Connect Health agents and Azure AD

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

This table describes the following outbound ports and protocols that are required for communication between the Azure AD Connect Health agents and Azure AD.

Protocol Ports Description
HTTPS 443(TCP/UDP) Outbound
Azure Service Bus 5671 (TCP/UDP) Outbound

7b - Endpoints for Azure AD Connect Health agent for (AD FS/Sync) and Azure AD

For a list of endpoints, see the Requirements section for the Azure AD Connect Health agent.