05 September 2026
Voice chat in M365 Copilot — and the Teams Stop button
Voice chat (481138) launched; Teams stop-while-generating (325948) rolling out. Transcripts follow Purview; Steady norms for spoken work.
DIGITAL SKILL WORKS LTD / 12 PANES

Illustration: Paper/Ink header (AI-assisted). DIGITAL SKILL WORKS LTD / 12 PANES.
Talking to Copilot is faster when your hands are full. Stopping a runaway Teams answer is just as important. Two roadmap items define that control surface.
What shipped / what’s on the roadmap
Voice chat in Microsoft 365 Copilot (MRC 481138) — status Launched. Natural, hands-free conversation on desktop and mobile — search, catch-up, brainstorm, multiple languages. Platforms listed include Android, Desktop, iOS, Web. GA listed September 2025 on the item.
Teams: Ability to Stop Copilot while it is generating a response (MRC 325948) — status Rolling out. A Stop control after sending a prompt — before or during generation — then start a new prompt. Desktop; GA May 2025 on the item.
What Learn says
Updated Windows and Microsoft Copilot Chat experience documents voice chat from November 2025: short/long press of the Copilot key (or Win+C), and an opt-in “Hey Copilot” wake word via Frontier timing noted in Learn. Voice follows the same enterprise data protection commitments as text. Text transcripts from voice chats are stored and managed like regular Copilot conversations — retention, eDiscovery, and audit apply to transcript content. No user or Copilot audio is stored. There is no feature-specific admin toggle to disable voice alone; turning off optional connected experiences disables web grounding for voice and other Copilot experiences.
Learn / prior-year release notes also record voice input for Copilot across the Microsoft 365 Copilot app and starting surfaces such as Outlook, Word, and PowerPoint (roadmap 481138).
Why you should care (12 Panes)
Board. Accessibility and speed claims — fund literacy and privacy norms with the feature.
CISO / GRC. Transcripts are the compliance object. Open-plan voice use needs behavioural guidance.
CFO. No separate “voice SKU” story here — still Copilot licence economics.
Adoption. Teach Stop in Teams; teach when not to speak sensitive prompts aloud.
Panes. 04 Security · 05 GRC · 08 Adoption · 12 Frontier (wake word / preview edges).
Diagram

Diagram: 12 Panes / tldraw — board “12 Panes — Blog Diagrams”.
Suggested action
- Update staff guidance: spoken prompts become text in audit/retention scope.
- Include Teams Stop in Copilot clinics — control is part of Steady.
- Review optional connected experiences policy with Security before blaming “voice settings”.
- Keep wake-word / Frontier features on a bounded Frontier list until Steady holds.
Communication needed
Security + GRC: transcript retention. Adoption + Comms: public-space etiquette. IT: Copilot key mapping policies where relevant.
Benefits and risks
Benefits. Hands-free catch-up. User agency via Stop. Same EDP model as text for commercial users.
Risks. Overheard prompts. Assuming audio is retained when only text is. Disabling connected experiences and surprising users when web grounding vanishes.