Ports | UDP ports 3478 through 3481 |
IP addresses | 13.107.64.0/18, 52.112.0.0/14, and 52.120.0.0/14 |
DNS record | Service | Protocol | Priority | Weight | Port | Target |
---|---|---|---|---|---|---|
SRV | sipfederationtls | TCP | 100 | 1 | 5061 | sipfed.online.lync.com |
Network optimization task | Details |
---|---|
Network planner | For help assessing your network, including bandwidth calculations and network requirements across your org's physical locations, check out the Network Planner tool, in the Teams admin center. When you provide your network details and Teams usage, the Network Planner calculates your network requirements for deploying Teams and cloud voice across your organization's physical locations. For an example scenario, see Using Network Planner - example scenario. |
Advisor for Teams | Advisor for Teams is part of the Teams admin center. It assesses your Microsoft 365 or Office 365 environment and identifies the most common configurations that you may need to update or modify before you can successfully roll out Teams. |
External Name Resolution | Be sure that all computers running the Teams client can resolve external DNS queries to discover the services provided by Microsoft 365 or Office 365 and that your firewalls are not preventing access. For information about configuring firewall ports, go to Microsoft 365 and Office 365 URLs and IP ranges. |
Maintain session persistence | Make sure your firewall doesn't change the mapped Network Address Translation (NAT) addresses or ports for UDP. |
Validate NAT pool size | Validate the network address translation (NAT) pool size required for user connectivity. When multiple users and devices access Microsoft 365 or Office 365 using Network Address Translation (NAT) or Port Address Translation (PAT), you need to ensure that the devices hidden behind each publicly routable IP address do not exceed the supported number. Ensure that adequate public IP addresses are assigned to the NAT pools to prevent port exhaustion. Port exhaustion will contribute to internal users and devices being unable to connect to the Microsoft 365 or Office 365 service. |
Routing to Microsoft data centers | Implement the most efficient routing to Microsoft data centers. Identify locations that can use local or regional egress points to connect to the Microsoft network as efficiently as possible. |
Intrusion Detection and Prevention Guidance | If your environment has an Intrusion Detection or Prevention System (IDS/IPS) deployed for an extra layer of security for outbound connections, be sure to allow all Microsoft 365 or Office 365 URLs. |
Configure split-tunnel VPN | We recommend that you provide an alternate path for Teams traffic that bypasses the virtual private network (VPN), commonly known as split-tunnel VPN. Split tunneling means that traffic for Microsoft 365 or Office 365 doesn't go through the VPN but instead goes directly to Microsoft 365 or Office 365. Bypassing your VPN will have a positive impact on Teams quality, and it reduces load from the VPN devices and the organization's network. To implement a split-tunnel VPN, work with your VPN vendor. Other reasons why we recommend bypassing the VPN:
|
Implement QoS | Use Quality of Service (QoS) to configure packet prioritization. This will improve call quality in Teams and help you monitor and troubleshoot call quality. QoS should be implemented on all segments of a managed network. Even when a network has been adequately provisioned for bandwidth, QoS provides risk mitigation in the event of unanticipated network events. With QoS, voice traffic is prioritized so that these unanticipated events don't negatively affect quality. |
Optimize WiFi | Similar to VPN, WiFi networks aren't necessarily designed or configured to support real-time media. Planning for, or optimizing, a WiFi network to support Teams is an important consideration for a high-quality deployment. Consider these factors:
Each wireless vendor has its own recommendations for deploying its wireless solution. Consult your WiFi vendor for specific guidance. |
Bandwidth(up/down) | Scenarios |
---|---|
30 kbps | Peer-to-peer audio calling |
130 kbps | Peer-to-peer audio calling and screen sharing |
500 kbps | Peer-to-peer quality video calling 360p at 30fps |
1.2 Mbps | Peer-to-peer HD quality video calling with resolution of HD 720p at 30fps |
1.5 Mbps | Peer-to-peer HD quality video calling with resolution of HD 1080p at 30fps |
500kbps/1Mbps | Group Video calling |
1Mbps/2Mbps | HD Group video calling (540p videos on 1080p screen) |