Simplified port requirements for Skype for Business Online
Note: This article applies only to Office 365 Worldwide (including Government Community Cloud). For guidance on Office 365 operated by 21 Vianet, Office 365 Germany, Office 365 U.S. Government DoD or Office 365 U.S. Government GCC High click on the respective links. We are happy to announce that the 50,000-59,999 port range (UDP and TCP) is no longer a requirement for Skype for Business endpoints to communicate with Skype for Business Online. Earlier this year we talked about making simplification for network connectivity for Skype for Business Online (see blog article here) and we recently updated our guidance and removed the mentioned port range as a requirement: Office 365 URLs and IP address ranges So which ports are required for clients? All clients need to be able to directly connect to Skype for Business Online on the following destination ports: (the IP addresses and FQDNs can be found in the Office 365 URLs and IP address ranges) TCP 80, 443 UDP 3478, 3479, 3480, 3481 Optional: UDP/TCP 50,000-59,999 Is there a minimum client version required to benefit from the port changes? This change applies to all clients supported against Skype for Business Online. No clients are excluded and there are no specific minimum version required (although we always recommend to run the latest version). Why are these ports not required anymore? To answer this question, it is important to understand first how the 50,000-59,999 ports were used in the first place. (To understand all the details of their purpose, we recommend watching Troubleshoot media flows in Skype for Business across online, server and hybrid.) Let's have the following example: User A wants to call User B For the sake of the example, the direct connection between User A and User B is blocked (e.g. User and User B are at different branch offices behind firewalls), so the media traffic cannot go directly peer to peer and needs to flow via Skype for Business Online There are now the following possible media paths The 50,000-59,999 port range can be leveraged to include only a single Relay Server in the media path Without the 50,000-59,999 port range, the traffic needs to travel via two Relay Server. As you can see, closing the 50,000-59,999 port range will force the traffic to travel via an additional hop. While logic tells us that usually we want to avoid additional hops under all circumstances, the analysis on call quality data has shown us, that this additional hop does not significantly affect call quality - since both these Relay Servers are homed on the Microsoft Network, all traffic between the Relay Servers is sent over a highly reliable pipe designed for real-time communication. Our organization has these ports open, should we close them? Having the 50,000-59,999 port range open can still have (some) benefits when it comes to call setup times and under some circumstances on call quality. However in our data analysis and pilot deployments with some customers these differences did not show significance. If you have the ports open today, it makes sense to leave them open. What does this change for hybrid between Skype for Business Server and Skype for Business Online? This change only applies to users who are homed in Skype for Business Online. If you have an on-premises deployment of Skype for Business, the requirements for your Edge Server to communicate to Skype for Business Online remain unchanged (and also for any Federation scenarios including Skype for Business on-premises). The A/V Edge Server in your environment will need to be configured liked this. Please note that the Source Port is only relevant, if your firewall requires a source port to be specified (and a lot of firewalls do not require this setting): Source IP Destination IP Source Port Destination Port A/V Edge service interface Any UDP 3478 UDP 3478 A/V Edge service interface Any TCP 50,000-59,999 TCP 443 Any A/V Edge service interface Any UDP 3478 Any A/V Edge service interface Any TCP 443 Full requirements for Skype for Business Edge Server can be found here: Edge Server environmental requirements in Skype for Business Server 2015. Does this change anything for Cloud Connector Edition? No, the requirements for Cloud Connector Edition (see Plan for Skype for Business Cloud Connector Edition) remain unchanged. Call to Action Celebrate about the simplified port requirements Update any design templates you might have For future deployments, open only TCP 80, 443 and UDP 3478, 3479, 3480, 3481 per new guideline (and, optionally, 50,000-59,999 UDP and TCP) If you have any questions or comments, please let us know in the community This post is brought to you by Skype Academy. Visit Skype Academy for technical trainings and readiness around the Skype Operations Framework.Skype for Business Server 2019 now GA!
Today we are excited to announce that as part of the Office Servers launch, Skype for Business Server 2019 is now generally available. This release enables customers to continue using Skype for Business in a on-premises environment while making it easy to take advantage of key cloud experiences. Key features at GA include: Cloud Voicemail support enables all your Skype for Business 2019 users—whether they are homed on premises or online—to have access to Cloud Voicemail. Cloud Call Data Connector greatly simplifies call monitoring in a hybrid environment by using online tools to monitor users call quality. Streamlined Teams Migration allows administrators to easily move on-premises to Teams with a simple Admin experience. TLS 1.2 support now enabled for improved security. Added support for Windows Server 2019 and continued support for Windows Server 2016. Looking forward, we’ll deliver additional capabilities including: Support for Cloud Auto Attendant, so that on-premises customers can always use the latest version. Customers will need to use a hybrid configuration for users syncing to AAD. Please note that Cloud Auto Attendant will be available later this year – we will announce when ready. Meetings First – Continue to use Skype for Business Server for Chat and Calling while harnessing Microsoft Teams for true cloud-based meetings. Your users will enjoy a great meetings experience while your company experiences improved performance using the Microsoft global cloud infrastructure. Our commitment remains strong to enable our customers with on-premises and cloud features. If you want to learn more about the release, please watch or download the Ignite session recording and the accompanying PowerPoint presentation. You can also read our latest documentation.Windows Server 2016 support for Skype for Business Server 2015
We are happy to announce that Skype for Business Server 2015 is supported to run on Windows Server 2016 - if you have the May 2017 update (aka CU5) for Skype for Business Server installed. Please refer to the following resources for more information: Our official support article: Supports to use Windows 2016 as the operating system in Skype for Business Server 2015 The Updated TechNet documentation: Operating systems for Skype for Business Server 2015 Our blog article on CU5: Announcing the release of Skype for Business Server Cumulative Update 5 Any questions or comments? Please let us know in our community! This post is brought to you by Skype Academy. Visit Skype Academy for technical trainings and readiness around the Skype Operations Framework.Welcome to the Skype for Business Community!
Greetings & welcome to the Skype for Business Community! We’re so glad you are here and excited to have this forum to collaborate and discuss all things Skype for Business. I am a Program Manager here at Microsoft within the Skype for Business Engineering team and am the Skype for Business Community Manager. My job is to make sure our customers and partners have a place to get answers to their questions and share information related to Skype for Business.
