Network ports for Microsoft Dynamics 365

Article
11/28/2017

Applies To: Dynamics 365 (on-premises), Dynamics CRM 2016

This section describes the ports that are used for Microsoft Dynamics 365. This information is helpful as you configure the network when users connect through a firewall.

In This Topic

Network ports for the Microsoft Dynamics 365 web application

Network ports for the Asynchronous Service, Web Application Server, and Sandbox Processing Service server roles

Network ports for the Organization Web Service server role

Network ports that are used by the SQL Server that runs the SQL Server and Microsoft Dynamics 365 Reporting Extensions server roles

Network ports for the Microsoft Dynamics 365 web application

The following table lists the ports used for a server that is running a Full Server installation of Microsoft Dynamics 365. Moreover, except for the Microsoft SQL Server role, and the Microsoft Dynamics 365 Reporting Extensions server role, all server roles are installed on the same computer.

Protocol	Port	Description	Explanation
TCP	80	HTTP	Default web application port. This port may be different as it can be changed during Microsoft Dynamics CRM Server Setup. For new websites, the default port number is 5555.
TCP	135	MSRPC	RPC endpoint resolution.
TCP	139	NETBIOS-SSN	NETBIOS session service.
TCP	443	HTTPS	Default secure HTTP port. The port number may differ from the default port. This secure network transport must be manually configured. Although this port is not required to run Microsoft Dynamics 365, we strongly recommend it. For information about how to configure HTTPS for Dynamics 365, see Make Dynamics 365 client-to-server network communications more secure.
TCP	445	Microsoft-DS	Active Directory service required for Active Directory access and authentication.
UDP	123	NTP	Network Time Protocol.
UDP	137	NETBIOS-NS	NETBIOS name service.
UDP	138	NETBIOS-dgm	NETBIOS datagram service.
UDP	445	Microsoft-DS	Active Directory service required for Active Directory access and authentication.
UDP	1025	Blackjack	DCOM, used as an RPC listener.

Important

Depending on your domain trust configuration, additional network ports may need to be available for Microsoft Dynamics 365 to work correctly. More information: Active Directory and Active Directory Domain Services Port Requirements

Network ports for the Asynchronous Service, Web Application Server, and Sandbox Processing Service server roles

The following table lists the additional ports that are used for a deployment where the Sandbox Processing Service is running on a separate computer.

Protocol	Port	Description	Explanation
TCP	808	Dynamics 365 server role communication	By default, communication over port 808 occurs as follows. The Asynchronous Service and Web Application Server services communicate to the Sandbox Processing Service through this channel. The Sandbox Processing Service communicates to the Web Application Server through this channel. The default port is 808, but can be changed in the Windows registry by adding the DWORD registry value TcpPort in the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\.

TCP

808

Dynamics 365 server role communication

By default, communication over port 808 occurs as follows.

The Asynchronous Service and Web Application Server services communicate to the Sandbox Processing Service through this channel.
The Sandbox Processing Service communicates to the Web Application Server through this channel.

The default port is 808, but can be changed in the Windows registry by adding the DWORD registry value TcpPort in the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\.

Network ports for the Organization Web Service server role

The following table lists the additional port that is used by the Organization Web Service server role.

Protocol	Port	Description	Explanation
TCP	808	Used for Fetch-based reports	Microsoft SQL Server Reporting Services servers that run Fetch-based reports initiated by Dynamics 365 clients communicate with the Organization Web Service server role (a Front End Server role) over this port.

Network ports that are used by the SQL Server that runs the SQL Server and Microsoft Dynamics 365 Reporting Extensions server roles

The following table lists the ports that are used for a computer that is running SQL Server and has only SQL Server and the Microsoft Dynamics 365 Reporting Extensions (SRS Data Connector) server roles installed.

Protocol	Port	Description	Explanation
TCP	135	MSRPC	RPC endpoint resolution.
TCP	139	NETBIOS-SSN	NETBIOS session service.
TCP	445	Microsoft-DS	Active Directory service required for Active Directory access and authentication.
TCP	1433	ms-sql-s	SQL Server sockets service. This port is required for access to SQL Server. This number may be different if you have configured your default instance of SQL Server to use a different port number or you are using a named instance.
UDP	123	NTP	Network Time Protocol.
UDP	137	NETBIOS-NS	NETBIOS name service.
UDP	138	NETBIOS-dgm	NETBIOS datagram service.
UDP	445	Microsoft-DS	Active Directory service required for Active Directory access and authentication.
UDP	1025	Blackjack	DCOM, used as an RPC listener.

Important

In addition to the ports listed previously, UDP port 1434 (SQL Server Browser Service) on the SQL Server is required by Microsoft Dynamics CRM Server Setup to return a list of the computers that are running SQL Server during the installation of Microsoft Dynamics 365 Server. To work around this, specify the SQLServer\InstanceName during Setup.

Network ports for Microsoft Dynamics 365

In This Topic

Network ports for the Microsoft Dynamics 365 web application

Network ports for the Asynchronous Service, Web Application Server, and Sandbox Processing Service server roles

Network ports for the Organization Web Service server role

Network ports that are used by the SQL Server that runs the SQL Server and Microsoft Dynamics 365 Reporting Extensions server roles

See Also

Additional resources