Back from HUMID Orlando Florida and another year of Ignite. There was a theme on the Modern Workspace side of the conference of Teams Teams Teams. There was, as expected, some concern and confusion over the announced removal of Skype for Business Online for sub-500 tenants. Surprisingly (at least to me) there was a general question of what the Skype for Business v2 (SRSv2) system was and even what Teams was.
Since there is little more that can be said about what Teams is I will not go into that and hopefully this audience is aware of the SRSv2. However, I do think it is important to take the time to reemphasize the need and requirement to perform (yourself or with an external consultant) network validations and health checks PRIOR to implementing a real-time communication SaaS such as Teams. Korneel Bullens and Siunie Sutjahjo provided a session where the discussion of the network health was stressed once again, and some great input was provided.
When I am asked to perform a network health check for Skype for Business/Teams there are multiple things I am looking for but often overlooked that those items need to be looked at from all SUPPORTED client networks. You may say my network is healthy and that if I get positive test results from one location or VLAN I have no reason to test another. I would argue, really? Users working in a remote user office with 10 total clients may end up having an even better experience than those in the 10k employee corporate office simply because of the network (assuming local breakout for the remote office). Then you have the Wi-Fi network and all that it entails – sometimes the Wi-Fi network is something that until fixed must be classified as an unsupported client network. I have yet to be involved in a deployment that did not have at least one area to address within the LAN/WAN but if you are the company – congratulations (and this assumes you did not already perform a network discovery and remediation for a previous Skype for business or an earlier version).
From a basic network discussion, the questions that come to mind when it comes to Teams specifically are:
Are the correct network ports open inbound/outbound
(188.8.131.52/18 tcp/443 AND 184.108.40.206/14 udp/3478-3481)?
Are there content filters/proxies in the mix?
Do all locations have a direct ingress/egress point of Internet (really for all O365 workloads and no, Express Route does not fix this need)?
Are PCs/Laptop network drivers up to date (the video and IO subsystem drivers are important too, but this is about networking)?
Keep the network health and utilization top of mind when working with SfB, SfB0 and Teams and your deployment will be a great success.