Using Microsoft Teams on macOS, including installation, features, and compatibility
On macOS, Teams screen sharing and app responsiveness depend heavily on OS permissions, display/docking configuration, and the Teams client version. For mac devices where sharing stops unexpectedly and the app freezes, use the following checks and mitigations:
- Verify macOS screen recording permissions for Teams
- Go to Apple menu > System Settings > Privacy & Security.
- Open Screen & System Audio Recording.
- Ensure the Microsoft Teams toggle is turned On.
- If permissions were changed, rejoin the meeting and start sharing again via Share in the meeting controls.
- If using Teams on the web, also ensure the browser has screen recording permission.
- Avoid or reconfigure problematic docking setups on macOS 14+
- There is a known issue on macOS 14 and higher where using DisplayLink or some docking stations affects sharing indicators and control panels.
- If users are on macOS 14+ and connected through DisplayLink or similar docks, test:
- Disconnecting from the dock and sharing directly from the built‑in display.
- Updating dock/DisplayLink drivers and macOS to the latest version.
- If the issue disappears when undocked, treat the dock/DisplayLink path as the root cause and adjust usage accordingly.
- Confirm Teams is allowed to start and maintain sharing
- In a meeting, select Share.
- If prompted, select Allow when Teams asks for screen recording.
- If the prompt was missed, use Open System Settings from the pop‑up (when it appears again) to re‑enable permissions, then retry sharing.
- Try the native macOS content sharing path
- In Teams, go to Settings and more > Settings > General > Screen sharing.
- Enable Use macOS content sharing.
- This switches to the native macOS sharing experience, which can be more stable on some Mac setups.
- Note: Giving and taking control of shared content is not supported in this mode.
- Check for high‑motion sharing and performance impact
- If users frequently share video or high‑motion content, Teams may increase frame rate, which uses more CPU/GPU and network.
- High resource usage can contribute to freezes on constrained devices.
- During a meeting, open More > Settings > Call health and review the Screen Sharing section (frame rate, resolution, bandwidth). If values are high and the device is under heavy load, reduce concurrent apps or switch to sharing a specific window instead of the full screen.
- Validate VDI/virtual desktop scenarios on Mac
- If users connect from Mac endpoints into AVD/Windows 365 or Citrix and run Teams inside the virtual machine:
- Ensure the environment meets the minimum versions for the new SlimCore‑based optimization.
- Be aware of known Mac issues: slow mouse cursor during app sharing, problems when attaching/detaching external monitors during a call.
- Outgoing screen sharing is disabled in end‑to‑end encrypted meetings on Mac VDI.
- If screen sharing fails or freezes only in VDI sessions, test Teams directly on the Mac (outside VDI) to isolate whether the VDI optimization path is involved.
- If users connect from Mac endpoints into AVD/Windows 365 or Citrix and run Teams inside the virtual machine:
- Monitor and correlate issues centrally (admin)
- In the Teams admin center, configure alerts for in‑progress meeting screen sharing issues:
- Go to Notifications & alerts > Rules.
- Use Audio quality for in‑progress meetings and configure Application sharing (VBSS) conditions.
- Set thresholds for freeze, frame rate, sync, hardware failures, and loss recovery attempts.
- Scope alerts to affected users/subnets and send notifications to a Teams channel or webhook.
- Use these alerts plus Call Health data to identify patterns (specific macOS versions, docks, networks).
- In the Teams admin center, configure alerts for in‑progress meeting screen sharing issues:
If, after applying the above, screen sharing still terminates and Teams freezes, collect:
- macOS version (including whether it is 14+ or 15.x/Sequoia),
- Dock/DisplayLink usage,
- Whether native macOS content sharing is enabled,
- Call Health metrics during the incident, then escalate through Microsoft support with these details.
References: