Description
This article describes the most common issues users encounter when using both FortiGate and Microsoft Teams.
It is a basic verification of a few checks for improvised or better working of Microsoft Teams.
Scope
FortiGate.
Solution
There are three important things to verify to resolve Microsoft Teams performance issues:
Multiple issues have been reported to occur due to lower UDP threshold packets. The audio and video functions of Microsoft Teams both use UDP packets.
Most UDP packets are dropped due to a lower threshold for UDP packets. This can be verified in the DDOS logs.
Test Microsoft Teams with no DDOS policy to better identify the issue.
See the article Using Microsoft Teams with DOS Policy.
Microsoft recommends using VPN in split tunnelling mode (see this link). The network design should consider the topologies and call flows described in Microsoft's Documentation. Below are some useful links to help in planning and designing the split networks, NAT, and routing back and forth:
Some issues are also noted in FortiClient. It is recommended to test with earlier versions.
Some UTM features can lead to false positives.
To avoid these issues, use FortiGate ISDB entries as Destination in a firewall policy without UTM profiles. This is also mentioned in Microsoft's Network Requirements section 1: 'open the TCP ports and IP addresses listed for Teams in Office 365 URLs and IP address ranges.'
Investigate any of these five possible causes as applicable. If an issue still persists, contact the TAC team.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.