Using Microsoft Teams on macOS, including installation, features, and compatibility
This matches known Teams-in-VDI and Windows App for macOS limitations more than an Intune policy issue.
Most relevant causes supported by the documented known issues:
- Teams app sharing on Mac endpoints has a known cursor/app-sharing performance issue
For AVD/W365 on Mac endpoints, app sharing can cause slow cursor or dragging behavior, and stopping then reinitiating app sharing removes the lag. This is documented as fixed in Teams 26149.x.x.x or higher. Since the reported Teams version is 26213.1006.5014.9784, that specific cursor-lag issue should already include the fix, but it still points to the screen-sharing path as a sensitive area. - Windows App for macOS has a Teams screen capture protection limitation
On macOS, enabling screen capture protection can interfere with screen sharing in Microsoft Teams, causing shared windows to appear blank or not display properly. If screen capture protection is enabled in the environment, it should be treated as a likely contributor and may need to be temporarily disabled on the device when Teams collaboration is required. - Teams in virtualized environments has multiple screen-sharing limitations
In Azure Virtual Desktop, Teams has documented limitations around application window sharing, including rendering/update problems when windows overlap, inability to select minimized windows, and other sharing-related constraints. These issues show that screen sharing in a virtualized session is a known problem area. - Mac endpoint audio/video device behavior is limited in virtualized Teams
On macOS, Teams in a remote session doesn’t enumerate individual audio devices the same way as local Teams because of a WebRTC limitation. This does not directly explain the freeze, but it confirms that the macOS + remote-session media stack has platform limitations.
What is not supported by the available documentation:
- No documented registry setting is provided here to prevent this exact freeze.
- No Intune policy is identified here as a known root cause for this exact symptom.
- No documented Windows App graphics setting is provided here as a fix for this exact freeze.
- No documented Teams hardware-acceleration toggle for this Mac/Cloud PC scenario is provided here.
Recommended next steps based on the documented guidance:
- Verify whether screen capture protection is enabled for the Cloud PC or virtual desktop environment. If it is enabled, test with it disabled because it is documented to interfere with Teams screen sharing on macOS.
- Confirm Teams optimization is being used for the Cloud PC session. Poor Teams performance on Windows 365 Boot is specifically tied to whether Teams optimizations are in use.
- Test by stopping and reinitiating app sharing when the issue begins, since that is the documented mitigation for the Mac endpoint app-sharing lag issue.
- Collect Teams logs from the Cloud PC for support investigation:
- Desktop app log:
%appdata%\Microsoft\Teams\logs.txt - Calls/meetings diagnostics log: press Ctrl + Alt + Shift + 1 in Teams, then collect
%userprofile%\Downloads\MSTeams Diagnostics Log DATE_TIME.txt
- Desktop app log:
- If the issue persists, contact Microsoft support with the Teams logs and a clear note that the problem occurs specifically during Teams window/app sharing from a Windows Cloud PC accessed through Windows App on macOS.
Based on the documented material, the strongest candidates are:
- a Teams-in-virtualized-session screen-sharing limitation, and/or
- screen capture protection on macOS interfering with Teams sharing.
References: