Configure Microsoft Entra Connect Ports for Active Directory and AD FS
Question details
Identify the network ports needed for Microsoft Entra Connect to communicate with on-premises Active Directory and, where applicable, AD FS.

- Product
- Microsoft Entra Connect, formerly Azure AD Connect
- Device & OS
- not provided
- Scenario
- Planning firewall rules for a hybrid identity deployment that connects on-premises Active Directory to Microsoft Entra ID and may use AD FS.
- Observed behavior
- The user needs a port list that accounts for deployment architecture, protocols, endpoints, and traffic direction.
Identify the Entra Connect server, domain controllers, DNS servers, and any AD FS servers in your deployment. Record the firewall boundaries and traffic direction between them before selecting rules.
Use Microsoft's port tables to configure the required firewall rules
Choose ports based on the components and communication paths used in your deployment.
Common Active Directory services include DNS on TCP and UDP 53, Kerberos on TCP and UDP 88, LDAP on TCP and UDP 389, LDAPS on TCP 636, SMB on TCP 445, and RPC endpoint mapping on TCP 135. Whether each is needed depends on the documented communication path and your configuration.
Entra Connect also needs HTTPS connectivity on TCP 443 for applicable Microsoft Entra endpoints. AD FS and Windows Remote Management ports depend on whether those components and management operations are used.
Visit https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/reference-connect-ports and review the network connectivity tables for Microsoft Entra Connect.
In the Active Directory port table, match each source and destination to your Entra Connect server, domain controllers, and DNS servers. Record the protocol, port, and traffic direction for each applicable service.
Review the AD FS and Microsoft Entra connectivity sections in the same reference. Add only the HTTPS or Windows Remote Management rules needed for your servers and deployment operations.
Check the RPC entries in the port reference and your Windows RPC configuration before creating firewall rules. Dynamic RPC ports may be required; do not open an entire high-port range without confirming the configuration and applicable rules.
Create the approved source-to-destination rules in your firewall management console, then use your network testing tools to verify connectivity on the required paths.

Document Entra Connect Firewall Rules with WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and compatibility with Microsoft Office formats, making it easy to bring existing planning documents into your workflow. It can help you document firewall rules, but it does not configure Entra Connect or replace its network requirements.

Frequently Asked Questions
Where can I find the current Entra Connect port requirements?
Open Microsoft's network connectivity reference at https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/reference-connect-ports and review the tables for the components in your deployment.
Does every deployment need AD FS ports?
No. Review the AD FS sections of Microsoft's port reference if your deployment uses AD FS or related management operations. Select rules for the actual servers and traffic paths involved.
Should I open all high ports for RPC?
Not without checking first. Review the RPC entries in Microsoft's port tables and confirm your Windows RPC configuration and firewall requirements before allowing any dynamic port range.
Is TCP 443 the only port Entra Connect needs?
No. HTTPS on TCP 443 is used for applicable cloud endpoints, but communication with on-premises Active Directory may also require DNS, Kerberos, LDAP, SMB, RPC, or other ports depending on the deployment.




