Microsoft Teams: Prevent presence transition to "Do not disturb" setting when screen sharing (GCC High, DoD)
We're introducing a setting that allows users to opt-out of transitioning presence automatically to Do Not Disturb when presenting or screen sharing. This ensures that they can continue to receive calls, keeping them connected and responsive without manual presence adjustments.
DIGITAL SKILL WORKS LTD / 12 PANES
What it is
Microsoft Teams: Prevent presence transition to "Do not disturb" setting when screen sharing (GCC High, DoD) is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: Launched.
What it does
We're introducing a setting that allows users to opt-out of transitioning presence automatically to Do Not Disturb when presenting or screen sharing. This ensures that they can continue to receive calls, keeping them connected and responsive without manual presence adjustments.
Why you should care
Board
Track as Horizon signal; decide whether it changes Wave 0 priority or stays on the watchlist.
CISO
Confirm identity, data access, and overshare exposure before enabling for broad cohorts.
CFO
Map licence or consumption impact to the frozen value case; avoid seat spray.
Adoption
Pilot with a named cohort and measure changed work, not vanity clicks.
Suggested action
Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Decide: adopt for a named cohort, defer, or reject. If adopting, update licence and adoption plans in the same week.
12 Panes: 03 Horizon · 08 Adoption
Communication needed
- Security: Assess exposure, Conditional Access, and agent/tool permissions.
- GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
- FinOps: Forecast seat or credit impact; align to frozen value case.
- Adoption: Plan cohort messaging, clinics, and success measures.
- Comms: One story for board and staff — what changes, what does not, who owns risk.
Benefits
- May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
- Roadmap visibility helps Horizon planning without guessing dates.
Risks
- Status and dates change; treat MRC as directional, not a contract.
- Enabling without Steady controls can amplify overshare or cost leakage.
Source
- MRC id: 567300
- Status: Launched
- Products: Microsoft Teams
- GA / disclosure: September CY2026
- Preview: —
- Platforms: Desktop, Mac
- Cloud instances: GCC High, DoD
- moreInfoUrls: —
- Open on Microsoft 365 Roadmap
Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.