- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Potential Conflict Between FortiEDR / FortiClient EMS and Microsoft Teams on macOS Sequoia (M3 Max)
Hi Fortinet Community,
I’m currently experiencing recurring issues with Microsoft Teams on my MacBook Pro (Apple M3 Max, 32 GB RAM) running macOS Sequoia 15.3.2.
When joining Teams meetings that involve video streaming, I regularly encounter interruptions or complete application crashes. This significantly affects my ability to participate in video calls.
My system is running both
FortiEDR
and
FortiClient
EMS (VPN connection active or inactive
After some testing, I’ve noticed that when I disable #FortiEDR, the crashes no longer occur. This leads me to believe that FortiEDR may be interfering with Teams or some system-level resources like video, audio, or network handling
Has anyone experienced similar issues or is aware of known compatibility problems between FortiEDR and Microsoft Teams on macOS?
Any advice, workarounds, or recommended configurations would be greatly appreciated.
- Labels:
-
FortiEDR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We're still looking for an answers or help. In the meantime, if anyone has any input on the topic, it's very welcome!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I would start with reviewing communication control events to isolate if any communication to teams is being blocked by EDR due to known vulnerability in a specific version or reputation could be a problem. You can do so by following below steps:
Login to FEDR -> Communication Control -> Applications -> Search for teams -> Select the application and on right side under Application details look for action in a respective policy which your collector group is part of.
If communication control is not blocking any teams traffic, it's worth to review the processes under event viewer to isolate if any teams process is being blocked when trying to perform a read or write operation.
Lastly, is the version, in case FortiEDR collector version is 4.1.0.188, consider uninstalling it and do a fresh installation using GA 6.0.10.1022 as upgrades from .4.1.x to 6.0.10.x is not supported from FEDR Manager and can be done only through Jamf Pro or manually as mentioned above.
If problem still persists, kindly reach out to our support team and we would be happy to help you with isolating the issue if any.
Thanks & Regards,
