Should Teams announce out loud when recording or transcription starts?

You’re right to worry about the people who miss the banner. Being open about recording only works if everyone actually knows, and a visual cue doesn’t reach people dialling in, people on a phone in their pocket, or anyone who can’t see the screen.

Here’s what’s going on. Roadmap 559609 is In development, with general availability targeted for December 2026. It describes a policy that “plays an audio announcement when recording or transcription starts”, which can be applied “tenant-wide or to specific groups”, to make sure participants are informed and to improve accessibility. Platforms listed are desktop, Mac, iOS and Android. It’s not here yet, so plan for it but don’t promise it.

It joins controls you already have:

• Custom banner messages. You can rewrite the recording and transcription notice (up to 200 characters, per language and scenario) and point the Privacy policy link at your own page. They aren’t supported in 1:1 calls, and mobile currently shows plain text only.
• Explicit consent. With ExplicitRecordingConsent on, other participants are muted with cameras off when recording or transcription starts, until they agree. Their choice is recorded in the attendance report and audit logs. Dial-in users press 1 to consent or 2 to decline.
• Copilot’s transcript setting. Copilot in meetings can run Only during the meeting on temporary speech-to-text that isn’t saved, or During and after the meeting, which needs a retained transcript. Learn notes that Copilot prompts and responses may still be kept under your Purview retention policies.

The audio announcement covers the gap the banner leaves: people who aren’t looking. Explicit consent goes further, because it makes people actually agree. You might want different combinations for different groups, say HR and legal meetings compared with project stand-ups.

One thing to check when it arrives: the roadmap talks about recording or transcription starting. Test whether Copilot’s temporary Only during the meeting mode triggers the announcement in your tenant before you tell anyone it does.

Options that actually work:

1. Use custom banners now, and add audio for sensitive groups when it ships. Send the privacy link to a plain-English page about meeting AI. Best Steady path.
2. Turn on explicit consent for high-sensitivity policies. It’s stronger than an announcement, but it adds friction, so scope it to the groups that need it.
3. Switch audio on tenant-wide at GA. It’s simple and inclusive, but some long-running meetings may find it repetitive. Pilot it first.
4. Rely on the banner alone. It’s the least effort, and it leaves dial-in and accessibility gaps.

12 Panes action / comms: Tell your DPO: 559609 adds an audio notice from December; here’s how it fits our transparency notice and explicit-consent groups. Tell the Teams admin: Draft custom banner text and a privacy URL now; plan an audio pilot for HR, legal and external meetings. Tell users: If you hear or see that recording or transcription has started, that includes Copilot’s transcript; here’s how to decline. Leadership: Making meeting AI visible to everyone, including people who can’t see the screen.

Benefits / risks: Better transparency and accessibility, notices you can scope by group, and a simpler story for UK GDPR transparency conversations. On the risk side: it isn’t released yet, it may not cover Copilot’s temporary mode, and stacking several notices can tire people out. Get legal advice on the consent model rather than treating an announcement as consent.

I’d suggest this week: write your 200-character banner text and privacy page, decide which policies need explicit consent, and put a December reminder in the change log to test 559609.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer