Microsoft Teams Screen Sharing Causes Remote Windows Cloud PC to Freeze When Accessed via the Windows App on Mac

Question

Microsoft Teams Screen Sharing Causes Remote Windows Cloud PC to Freeze When Accessed via the Windows App on Mac

Jeevan Ale 0

Issue: We are experiencing an issue where a Windows Cloud PC becomes completely unresponsive when Microsoft Teams screen sharing is used during a meeting.

Steps to reproduce:

Access an Intune-managed Windows Cloud PC remotely from a Mac using the Windows App.
Start or join a Microsoft Teams meeting on the remote Windows PC.
Share a window or application through Microsoft Teams.
After some time, the remote Windows session becomes completely unresponsive.

Observed behavior:

Mouse and keyboard input stop responding.
The Windows desktop and visual elements appear frozen.
The Teams audio connection remains active.
Disconnecting and reconnecting to the Cloud PC through the Windows App restores access.

Environment:

Client: Mac
macOS: Sequoia 15.7.3
Remote device: Intune-managed Windows Cloud PC
Remote access client: Windows App for Mac
Microsoft Teams version: 26213.1006.5014.9784

What we have tried: Reconnecting to the Cloud PC restores functionality, but the issue can occur again when Teams screen sharing is used.

Question: What could be causing the remote Windows Cloud PC to freeze when Microsoft Teams screen sharing is enabled?

Could this be related to:

Teams hardware acceleration or graphics processing
Windows App or Remote Desktop graphics configuration
GPU or hardware-accelerated video encoding/decoding
Intune device or configuration policies
Microsoft Teams configuration
macOS permissions or security settings

Are there any known issues, recommended policies, registry settings, Teams configurations, or Windows App settings that can prevent this behavior?

We can provide diagnostic information such as Windows Event Viewer logs, Teams logs, Windows App/Remote Desktop logs, GPU configuration, and relevant Intune configuration if required.

We would appreciate guidance on identifying the root cause and recommended steps for a permanent resolution.

0 comments

2 answers

Your answer

Answer 1

JeseminQH 515 Independent Advisor

Hi @Jeevan Ale

Regarding your issue, may I kindly ask a few questions so I can understand your issue better:

When did the issue first start, and were any updates or configuration changes made around that time?
Which meeting types are affected: one-to-one, group, channel, or all meetings?
Is this affecting only one user, or have other users reported the same behavior?
Is the behavior limited to one Cloud PC, or can it be reproduced on another Cloud PC?
Can you reproduce the issue when accessing the Cloud PC from another Mac or a Windows device?
Does the Cloud PC freeze when sharing the entire screen, a specific application window, or both?
When you join the meeting and share content using Teams on the web, does the same issue occur like Teams desktop application?

Feel free to share the requested details when convenient. I look forward to hearing from you.

Jeevan Ale 0 Reputation points

2026-09-02T06:14:01.63+00:00
Hi @JeseminQH, thank you for your questions. Please find the details below:

The issue has been occurring since the first usage of the Cloud PC and is still happening. The Cloud PC is freshly provisioned and Intune-managed, with the same configuration as our other Cloud PCs.

We generally use one-to-one meetings, and the issue occurs during one-to-one meetings.

The issue is affecting only one user. This is the only user who accesses the Cloud PC from a Mac laptop using the Windows App.

The issue appears to be specific to the Cloud PC when it is accessed from a Mac. We have another Cloud PC with the same configuration that works correctly when accessed from a Windows laptop using the Windows App.

When the affected Cloud PC is accessed from a Windows laptop, we do not experience the issue. Therefore, the issue appears to be related to accessing the Cloud PC from the Mac.

The issue occurs approximately 2–3 seconds after starting screen sharing. At that point, the Cloud PC completely freezes: the mouse becomes unresponsive and there is no graphical response. However, the meeting audio/voice continues to work.

The issue occurs with both the Teams desktop application and Teams on the web. We experience the same behavior with both.

We have primarily tested this scenario with one-to-one meetings.

In summary, the same Cloud PC configuration works normally when accessed from a Windows laptop. However, when the Cloud PC is accessed from the Mac using the Windows App, the Cloud PC freezes approximately 2–3 seconds after screen sharing starts during a Teams meeting, while the audio continues to work.

Please let me know if you need any additional information, logs, or diagnostic data from the affected Mac or Cloud PC.
JeseminQH 515 Reputation points Independent Advisor

2026-09-02T10:02:46.44+00:00

Hi @Jeevan Ale,

Thank you for sharing the detailed results. Based on your testing, the issue appears to occur specifically when the Cloud PC is accessed from the Mac through the Windows App. Since you have already confirmed that the same Cloud PC works correctly from a Windows device and that the issue occurs in both the Teams desktop application and Teams on the web, I suggest creating a ticket with Microsoft Support for further investigation.

When submitting the ticket through Help & support in the Microsoft 365 admin center, include the details you shared here, together with the affected user, Cloud PC name, Windows App version, and the date and time when the issue last occurred. This will allow the support team to collect the appropriate logs from the Mac and Cloud PC.

A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis.

For more details, please refer to: Get support - Microsoft 365 admin

If you’re unsure who the Global Admin is within your organization, you can find guidance on locating them here: How do I find my Microsoft 365 admin?

For details on how to collect Teams logs please refer to: Collect log files for monitoring and troubleshooting in Teams - Microsoft Teams

Note: If you’re an end-user, please coordinate with your Office 365 Global Administrator to handle these step

Before submitting the ticket, make sure the Support Assistant is turned Off as several customers have reported that when the Support Assistant is enabled, the Contact Support option may not appear.

As shown in the screenshot, simply switch Support Assistant > Off, then enter your issue description. Once disabled, the Contact Support button should appear, allowing you to submit the ticket normally.

I apologize for redirecting you to Microsoft Support. As a fellow community user, I do not have access to the diagnostic tools or backend systems required to investigate this issue effectively due to privacy and security limitations. Microsoft Support has the necessary permissions and tools to collect and review diagnostic data from the affected Mac and Cloud PC.

Answer 2

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
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:

Microsoft Teams Screen Sharing Causes Remote Windows Cloud PC to Freeze When Accessed via the Windows App on Mac

Microsoft Teams Screen Sharing Freezes Remote Windows Cloud PC

2 answers

Your answer