Microsoft Teams Screen Sharing Bug Causes Blank Screens on macOS
Microsoft has confirmed a Teams screen sharing issue that can cause blank or black screens on Macs during meetings.
Affected users may also see screen sharing stop unexpectedly or fail to start. Microsoft says the documented issue affects Macs running versions earlier than macOS Tahoe 26.4.
Access content across the globe at the highest speed rate.
70% of our readers choose Private Internet Access
70% of our readers choose ExpressVPN
Browse the web from multiple devices with industry-standard security protocols.
Faster dedicated servers for specific actions (currently at summer discounts)
The problem currently applies to Microsoft 365 Government environments, including GCC, GCC High, and Department of Defense tenants. Updating macOS resolves the known issue, while native macOS sharing offers a temporary workaround.
What happens when the Teams screen sharing bug appears?
The bug affects the visual content a Mac user attempts to present in a Microsoft Teams meeting. Other participants may see a blank or black area instead of the shared desktop or application.
In some meetings, screen sharing begins normally but stops without warning. Other users may find that Teams cannot start the sharing session at all.
The symptoms can interrupt presentations, training sessions, technical demonstrations, and support calls. Other meeting features, including audio, may continue working.
| Symptom | What users may experience |
|---|---|
| Blank or black screen | Participants cannot see the shared desktop or application |
| Interrupted sharing | The screen sharing session stops unexpectedly |
| Sharing failure | Teams cannot begin the sharing session |
| Reduced stability | Failures may occur more often on resource-constrained Macs |
Which Microsoft Teams users are affected?
Microsoft describes the issue in Message Center advisory MC1392559.
The advisory applies to Teams users in GCC, GCC High, and DoD environments who use Macs running versions earlier than macOS Tahoe 26.4.
Microsoft has not identified the problem as a general outage affecting every commercial Microsoft 365 tenant or every Mac user.
- Microsoft Teams users in GCC environments
- Microsoft Teams users in GCC High environments
- Microsoft Teams users in DoD environments
- Macs running versions earlier than macOS Tahoe 26.4
- Devices experiencing memory or disk constraints
Low memory and disk pressure may increase failures
Microsoft says screen sharing problems may appear more often on Macs with limited system resources.
Low available memory can affect Teams performance during video meetings and screen sharing. Heavy disk usage may also reduce system responsiveness.
Users should close unnecessary applications and browser tabs before a meeting. They should also confirm that the Mac has enough free storage space.
Updating macOS resolves the known issue
Microsoft recommends updating affected Macs to macOS Tahoe 26.4 or a later supported version.
Apple has released newer Tahoe updates since version 26.4. Its macOS Tahoe release notes list the updates currently available for compatible Macs.
Users can install updates through Software Update in macOS. Apple only offers releases compatible with the Mac model.
- Open the Apple menu.
- Select System Settings.
- Choose General.
- Open Software Update.
- Install macOS Tahoe 26.4 or a later available version.
- Restart the Mac when prompted.
Native macOS sharing provides a workaround
Users who cannot update macOS immediately can enable the native Mac sharing experience inside Teams.
Microsoft documents the option in its Teams screen sharing instructions.
The setting uses Apple’s native content picker when the user selects a desktop or application window to share.
- Open Microsoft Teams.
- Select Settings and more.
- Open Settings.
- Select General.
- Find the Screen sharing section.
- Enable Use macOS content sharing.
- Retry the screen sharing session.
Teams does not need a restart
Microsoft says the native sharing setting takes effect immediately. Users do not need to close or restart Teams after enabling it.
They can return to the meeting and attempt to share their desktop or application again.
The native macOS sharing experience has some limitations. For example, giving or taking control of shared content may not work while the setting remains enabled.
Microsoft delayed its in-product guidance
Microsoft plans to add automatic guidance that appears when Teams detects a screen sharing failure.
The company initially planned to begin the rollout in late June 2026 and finish by mid-July. The updated MC1392559 notice moves the rollout to late July 2026.
Microsoft now expects to complete deployment by mid-August 2026.
| Deployment stage | Original timeline | Updated timeline |
|---|---|---|
| Rollout begins | Late June 2026 | Late July 2026 |
| Rollout completes | Mid-July 2026 | Mid-August 2026 |
The Teams update adds guidance, not a software fix
The upcoming change will not repair the underlying problem on older versions of macOS.
Instead, Teams will recognize a sharing failure and display instructions. The message may ask the user to retry or recommend updating macOS.
Microsoft will enable the guidance automatically. Administrators will not need to activate a separate policy or configuration.
What IT administrators should do
Administrators should identify managed Macs running versions earlier than Tahoe 26.4.
Device management tools can help organizations locate outdated systems and determine whether company policies prevent users from installing updates.
IT teams should also review Apple’s macOS Tahoe update information before approving a release for managed devices.
- Identify Macs running versions earlier than Tahoe 26.4.
- Confirm whether affected users belong to GCC, GCC High, or DoD tenants.
- Push supported macOS updates where company policy allows.
- Document the native sharing workaround.
- Prepare helpdesk staff for black screen and sharing failure reports.
- Check available memory and disk space on affected Macs.
Helpdesk teams should check the macOS version first
When a user reports a black screen, support staff should first confirm the installed macOS version.
If the Mac runs an older release, the user should update to Tahoe 26.4 or later. When an update cannot happen immediately, support staff can enable native macOS content sharing.
The user should then follow Microsoft’s official Teams presentation guide and test the shared content with another participant.
Other problems can cause similar Teams symptoms
MC1392559 does not cover every screen sharing failure on a Mac.
Missing screen recording permissions, docking stations, external displays, outdated Teams builds, and graphics problems may also produce black screens or interrupted sharing.
If the Mac already runs Tahoe 26.4 or later, users should confirm that Teams has permission to record the screen under System Settings, Privacy and Security, and Screen and System Audio Recording.
What affected users should do now
Users should check their macOS version before their next important Teams meeting.
Installing Tahoe 26.4 or a later supported update provides Microsoft’s recommended resolution. Enabling native macOS sharing offers the main workaround when an update is not immediately possible.
Organizations should communicate both options to affected employees before Microsoft completes the in-product guidance rollout in mid-August 2026.
FAQ
Microsoft has confirmed a known issue affecting screen sharing on Macs running versions earlier than macOS Tahoe 26.4. Low memory or heavy disk usage may make failures more likely.
Microsoft currently lists GCC, GCC High, and Department of Defense environments in Message Center advisory MC1392559.
Update the Mac to macOS Tahoe 26.4 or a later supported version. Microsoft identifies this as the resolution for the documented issue.
Open Teams Settings, select General, find Screen sharing, and enable Use macOS content sharing. This switches Teams to Apple’s native sharing experience.
No. Microsoft says the setting takes effect immediately, so users do not need to restart Teams.
Microsoft plans to begin the rollout in late July 2026 and complete it by mid-August 2026. The change adds troubleshooting prompts rather than a software fix.
Read our disclosure page to find out how can you help VPNCentral sustain the editorial team Read more
User forum
0 messages