Microsoft plans to give Government Community Cloud High (GCC High) and Department of Defense (DoD) Microsoft Teams users a long-awaited choice: the ability to stop Teams from automatically switching their presence to Do Not Disturb when they share their screen or present. The feature, outlined in the Microsoft 365 Roadmap under ID 567300, is slated for general availability in September 2026.
It marks a shift for users in environments where a blocked call during a briefing could have serious operational consequences. Until now, that automatic presence change was hard-coded, leaving no room for a presenter to remain reachable without manually adjusting settings—a workflow that often gets forgotten in the heat of a live presentation.
The concrete change: an opt-out toggle, not a new default
At its core, the update introduces a user-level setting that lets individuals choose whether Teams should suppress incoming calls and notifications while they’re actively sharing content. Microsoft’s own roadmap wording describes it as an opt-out, not a blanket behavior change. In practice, that means the existing Do Not Disturb behavior will stay the default; those who want to keep interruptions at bay during presentations don’t have to do anything. But users who need to stay available—for incident response, command directives, or time-sensitive coordination—can flip a switch and let calls come through as normal.
The feature is exclusive to GCC High and DoD tenants, and it applies to the Teams desktop client on both Windows and Mac. It does not extend to the commercial public cloud, nor does it cover the web or mobile clients at this stage. Microsoft added the roadmap entry on July 14, 2026, with a target rollout date of September 2026, though the company cautions that such dates are planning estimates and can shift.
No specifics are yet available on where exactly the control will live in the Teams interface. Microsoft has not published a screenshot or detailed the path—Settings, Privacy, Notifications, or a dedicated presence section are all plausible. Similarly, there’s no word yet on whether tenant admins will be able to set a policy, define an organization-wide default, or lock the setting for certain users. Those details typically emerge closer to public preview or rollout.
What it means for you: by audience
For the defense or government user
If you’ve ever presented a mission dashboard, a remote-support session, or a live incident review only to realize afterward that you missed a critical call from your command post, this update is for you. The automatic Do Not Disturb function works by suppressing all calls and most notifications once a screen share starts; you may not even notice you’re marked as Do Not Disturb until you end the session and see the missed calls. The new option eliminates that blind spot.
You’ll be able to decide, before or even during a meeting, whether you want to remain reachable. The trade-off is straightforward: turn the setting off, and you might get an audible call alert or a pop-up while you’re sharing sensitive material. Keep it on, and you get the silence you’re used to. It’s a personal choice, not an IT mandate.
For the administrator
Right now, there’s no action you need to take, but you should start thinking about your organization’s guidance. Many agencies have internal policies that reference Teams presence as a reliable indicator of someone’s availability. Once this feature lands, that assumption will no longer be uniformly true. A user could be presenting—their screen fully visible to a room of stakeholders—and still receive a direct call from a senior leader. That may be exactly what you want, but it could also introduce confusion if teams aren’t aware of the new behavior.
Plan to review your training materials and user documentation. Consider whether you’ll want the ability to control this setting via policy or leave it entirely in users’ hands. If Microsoft eventually provides admin toggles, you’ll need to decide on defaults. For now, the best move is to flag the change for your security and operations leads and keep an eye on the roadmap for any admin-control announcements.
For the developer or integrator
If you build compliance recording, presence-awareness, or workflow automation that relies on Teams presence states, the change could create edge cases. A user who is presenting but not in Do Not Disturb might trigger different routing logic. Watch for Microsoft Graph API updates and presence-reason enrichment so your solutions don’t assume a presenter is always DND.
How we got here: presence as a dual-use tool
Microsoft Teams’ presence model has always been a blend of user-set status and automatic state changes driven by calendar, calls, and now screen sharing. The auto-DND during presenting arrived in a 2020 update as a quality-of-life improvement for the broad commercial base: it cut down on embarrassing notification pop-ups during external client demos and prevented background music or message pings from interrupting a flow.
But in GCC High and DoD clouds, Teams is often the only real-time communication fabric spanning classified and unclassified workflows. The same person who presents a weekly status report might also be the on-call responder for a time-critical event. The blanket DND rule became a frequent pain point, generating UserVoice and feedback portal requests that Microsoft acknowledged as far back as 2023.
The roadmap entry signals that the engineering team sees a clear delineation between general-purpose collaboration and mission-critical communication. Instead of overhauling presence across all clouds, they’re adding a targeted exception where the need is highest—without disturbing the experience for the millions of commercial users who appreciate the silence.
What to do now: no immediate action, but preparation pays
The feature is still in development. You can’t enable it today, and there’s no preview build to test. That said, you can take three preparatory steps:
- Notify your Teams champions and training leads. Let them know that a change is coming so they’re not caught off guard when users start asking about it. Share the roadmap link (ID 567300) so they can track progress.
- Revisit your presence-reliance documentation. If your operational playbooks say something like “presenters will be in Do Not Disturb and unreachable,” now’s the time to pencil in a rewrite. The exact phrasing can wait until you see the admin controls, but the concept of a reachable presenter should no longer be treated as an error.
- Watch for admin-policy details. Microsoft frequently releases admin controls a few weeks before the user-facing toggle goes live. As the September 2026 date nears, check the Message Center and the Teams admin center for new policies related to “presence” or “sharing.” Early awareness will let you pilot the setting with a test group before broad deployment.
On the user side, the day the toggle arrives, you’ll simply need to decide your preference: stay quiet or stay available. No training course required—just a new checkbox or switch that puts you back in charge of your own presence.
Outlook: what to watch next
The most important unanswered question is administrative control. If Microsoft delivers policy granularity—say, a PresenceAutoDNDMode setting with options for Default, OptOutAllowed, or Disabled—then organizations can tailor the experience to different roles. Even without that, the feature is a nod toward more context-aware presence in secure clouds. It may pave the way for similar exceptions in other automatic state changes, such as during video calls or when a user joins a secondary device.
For now, the countdown is on to September 2026. It’s a small toggle with outsize implications for anyone who’s ever had to choose between giving a smooth presentation and fielding a call they couldn’t afford to miss.