#Ports for skype for business update
The steps in red are part of the Exchange Server configuration and the steps in blue are performed on the Skype for Business side.Īssumptions made for the environment used with this article are that Exchange Server 2013 has been deployed with a relatively recent service pack or cumulative update applied. The sections in this article are outlined in the following configuration steps. Thus is is recommended to start with UM integration and follow these articles in the order they were posted.
If these are configured in the opposite order, meaning that the Instant Messaging integration is performed first, then the setup of Unified Messaging can break the IM integration due to duplicate, conflicting entries for the Exchange Server in SfB. Establishing this first will mean that when the IM integration is tackled there will be no need to defined the Exchange Server as a third-party Trusted Application in the SfB topology. Configuring UM first will enable automatic discovery of the Exchange environment in Skype for Business using the configured SIP domain namespace. One caveat to be aware of is the recommendation to configure UM integration before enabling Instant Messaging (IM) integration with Outlook Web Access. This article will tie all steps into a single set of instructions which can be completed linearly. Unfortunately the official documentation is partially incomplete and is also split across the separate product guides for SfB and Exchange Server, making it difficult to understand what is needed for a successful integration. The following configuration covers generally the same approach used to integrate previous version of Lync Server and Exchange Server which was outlined in this older article. The guidance provided here is a more detailed look at what is partially covered in the official TechNet documentation. These articles also apply when using Exchange Server 2016, with one exception related to Instant Messaging integration which will be the next topic addressed in a future article. Microsoft has recently released to the public the installation package for Exchange Server 2016 for use in on-premises deployments.
#Ports for skype for business series
Note that this series of Exchange integration articles leverages Exchange Server 2013 and will continue to do so for continuities’ sake. article covers the configuration steps for introducing voice mail support into a Skype for Business (SfB) Server 2015 environment by integrating with Exchange Server 2013 Unified Messaging (UM). *. – optional Azure Rights Management & MOM Packĭc. – optional Azure AD RemoteApp The main URL’s for the proxy are as follows: *. The followind will detail the other services:ĭefault ports are 80, 443, 25 (for any client mail routing outside of Exchange this would also require 587) and 49443 if ADFS is being used with ClientTLS. The following is the baseline firewall ports and URL’s required to consume Office 365. So which ports are required for clients?Īll clients need to be able to directly connect to Skype for Business Online on the following destination ports: TCP: 80, 443 No clients are excluded and there are no specific minimum version required. This change applies to all clients supported against Skype for Business Online.
Is there a minimum client version required to benefit from the port changes? The following is the URL’s that SfB Online from the client will use to get to the SfB Online servers so if the traffic is going through internet proxies and you are having issues these URL’s will be helpful: *. Skype for Business Mobile push notifications – iOS Only This is from the clients machine to Office 365: Port DestinationĪudio, Video, Application sharing sessions and Web Conferencing The following are the requirements of Skype for Business Online, note this information can change as the service evolves.
0 kommentar(er)
