{"id":3832,"date":"2020-01-28T11:35:03","date_gmt":"2020-01-28T19:35:03","guid":{"rendered":"https:\/\/blogs.poly.com\/?p=3832"},"modified":"2020-01-28T11:35:03","modified_gmt":"2020-01-28T19:35:03","slug":"is-your-network-ready-for-microsoft-teams","status":"publish","type":"post","link":"https:\/\/blogs.poly.com\/is-your-network-ready-for-microsoft-teams\/","title":{"rendered":"Is Your Company\u2019s Network Ready for Microsoft Teams?"},"content":{"rendered":"

PART 2 OF A 5-PART SERIES<\/h4>\n

In part one of this series<\/strong><\/a>, my colleague Vince Griffin laid out some important considerations that savvy IT Managers should take into account before taking the plunge and migrating their organizations to Microsoft Teams. \u00a0Today we\u2019ll focus on providing some general best practices around ensuring your company\u2019s network is reviewed and ready. Performing a readiness review of the network is essential to ensure its ability to handle the traffic and operational rigor required for advanced calling and collaboration features available with Teams.<\/p>\n

It\u2019s important to understand that Microsoft Teams uses different types of traffic for each of its features, calling for unique networking requirements to facilitate simultaneous peer-to-peer communications, conferencing communications and the data moving between the Microsoft Teams client and Microsoft Edge. Organizations must ensure that external firewalls, internal firewalls, traffic shapers, proxy devices, and so on are all perfectly configured to provide the best path for the data traffic in order to avoid failure to the network.<\/p>\n

 <\/p>\n

What to Cover During a Basic Network Review?<\/strong><\/h3>\n

Microsoft 365 Ports and Protocols being open on the Firewall (Internal and External)<\/strong><\/h4>\n

The Microsoft Teams calling and meetings experience is built on the next generation cloud-based infrastructure that is also used by Skype and Skype for Business. These technology investments include Azure-based cloud services for media processing and signaling, H.264 video codec, SILK and Opus audio codec, network resiliency, telemetry, and quality diagnostics. \u00a0Microsoft is continuously improving all these services and adding new functionality, which means the required ports, URLs, and IP addresses may change over time. Check out the following link for more information: Office 365 URLs and IP address ranges<\/a><\/strong><\/p>\n

Use of Network Planner to identify if the bandwidth is enough to cover each site <\/strong><\/h4>\n

Network Planner<\/a><\/strong> is a new tool that is available in the Microsoft Teams admin center. In just a few steps, the Network Planner can help you determine and organize network requirements for connecting Microsoft Teams users across your organization. When you provide your network details and Microsoft Teams usage, the Network Planner calculates your network requirements for deploying Microsoft Teams and cloud voice across your organization\u2019s physical locations.\u00a0<\/strong><\/p>\n

Check for enough bandwidth on Internet facing links<\/strong><\/h4>\n

When planning on the implementation of Microsoft Teams within your network, you must ensure you have the required bandwidth required for real-time media. \u00a0IT Managers who assume they have enough bandwidth and attempt to deploy Microsoft Teams without proper planning and design will quickly start receiving reports about sub-optimal audio or video quality. In most cases, Microsoft Teams is not the issue, it’s usually something within the network.<\/p>\n

Check for poor or insufficient Wi-Fi coverage<\/strong><\/h4>\n

Wi-Fi networks aren\u2019t necessarily designed or configured to support real-time media. Optimizing a Wi-Fi network to support Microsoft Teams is an important consideration for a high-quality deployment. Ensure that media traffic is getting prioritized accordingly over the Wi-Fi networks and be thoughtful about optimizing access point placement so that channels don\u2019t overlap.<\/p>\n

Check for any problematic subnets or network devices<\/strong><\/h4>\n

To increase user satisfaction, you should limit any impairments on your network. The most common network impairments are delay (latency), packet loss, and jitter. When testing for these impairments you should test on each subnet with Microsoft Teams enable users.<\/p>\n

Don\u2019t forget the VPN!<\/strong><\/h4>\n

Another common mistake that we see a lot is when organizations forget to think about configuring a VPN for employees who work from home. A misconfigured VPN for Microsoft Teams will be a complete headache for remote user and your support desk alike. Remote offices should be considered as well. Regardless of whether they use local internet or obtain it by connecting to the HQ, don\u2019t forget to account for the fact that all traffic used by these offices adds to bandwidth consumption!<\/p>\n

\u00a0<\/strong>Still in Need of a Hand?<\/strong><\/h4>\n

While Microsoft does offer a number of tools to help with network assessment, you may still need help depending on your team\u2019s expertise and\/or size and the scale of your organization\u2019s network. Poly offers a couple of options for network assessment including Poly Network Readiness for Microsoft Teams<\/strong> and Network Assessment Advanced <\/strong>where our experts can assist and advise on the network requirements to ensure that users have the best possible experience.<\/p>\n

For more information about Poly Services for Microsoft Solutions including our Network Assessment Services, email us at\u00a0TeamMicrosoft@poly.com<\/strong><\/a>\u00a0or visit\u00a0https:\/\/www.polycom.com\/collaboration-solutions\/microsoft-unified-communications\/microsoft-teams.html<\/strong><\/a>.<\/p>\n

Poly will be at ISE 2020 (Integrated Systems Europe) exhibition in Amsterdam on February 11-14, so if you would like to discuss things in more detail, visit us in the Smart Building, Booth 9 B-175.<\/p>\n","protected":false},"excerpt":{"rendered":"

PART 2 OF A 5-PART SERIES In part one of […]<\/p>\n","protected":false},"author":53,"featured_media":3833,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1457,517,526],"tags":[1479,20,1480,43,1481,1482,1483,1484,1485,1486,415,1203],"_links":{"self":[{"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/posts\/3832"}],"collection":[{"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/users\/53"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/comments?post=3832"}],"version-history":[{"count":0,"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/posts\/3832\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/media\/3833"}],"wp:attachment":[{"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/media?parent=3832"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/categories?post=3832"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.poly.com\/wp-json\/wp\/v2\/tags?post=3832"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}