The roadmap entry says admins can apply the policy to the whole tenant or only to specific groups. Microsoft says the goal is to make sure all participants know what's happening and to improve accessibility awareness. The item is marked In development. Its estimated general availability date is December 2026, for the Worldwide (Standard Multi-Tenant) cloud, on Android, desktop, iOS and Mac clients.
Treat that date as a forecast, not a promise. Microsoft's roadmap describes its release dates as estimates and warns that all information is subject to change.
What the roadmap item says, and what it doesn't
Confirmed by the roadmap entry:
- Who turns it on: admins, through a policy
- What triggers it: recording or transcription starting
- Scope: the whole tenant or specific groups
- Platforms: Android, desktop, iOS, Mac
- Status: In development, GA estimated for December 2026
Still unknown:
- The exact wording, language support or voice of the announcement
- Whether recording and transcription each get their own announcement
- Whether the policy is on or off by default
- Where admins will configure it in the Teams admin center or PowerShell
- Whether it covers meetings, events, 1:1 calls, PSTN calls, or some mix
- Licensing requirements
- Whether every listed platform behaves the same way
Web isn't on the platform list. Don't read anything into that until Microsoft publishes setup documentation.
Section summary: The basic idea is confirmed: an audible alert, controlled by admin policy, scoped to the tenant or to groups. The details admins usually need for change management haven't been published yet.
How it fits with the controls Teams already has
The new audio cue joins a fairly crowded set of recording and transcription controls. Here's what exists today.
The visual banner. Microsoft Learn says that when recording or transcription starts, Teams displays a notification banner composed of four elements. Admins can already customize the banner text and the privacy policy URL. The setting, Show customized in-meeting notification for recording and transcription, sits in the Recording & transcription section of a meeting policy under Meetings → Meeting policies. An audio announcement would add sound to what has so far been a visual-only notice for most participants.
Explicit recording consent. This one is easy to confuse with the new feature, and it's much stricter. For Audio Conferencing, Microsoft says that when the explicit recording and transcription policy is enabled, all participants are muted once the meeting recording or transcription starts. Participants then have to give consent before they can unmute. Dial-in users do this from the keypad: 1 - Give consent to being recorded and transcribed in a call and un-mute their microphone.
Audio notices on phone-style endpoints. Some Teams users already hear recording notices. An answer on Microsoft Q&A says Teams enforces an audible recording notification ("This call is being recorded") for calls involving analog, SIP, or PSTN endpoints connected through gateways or Direct Routing. That's a community Q&A response, not formal product documentation. Still, it suggests the new roadmap item extends an audible cue to the main Teams clients under admin policy.
Separate policies for meetings, events and calls. Microsoft's recording overview says meeting policies, events policies and voice calling policies each control recording and transcription for their own scenarios. If they aren't aligned, the results can be inconsistent. Microsoft's own example is a finance team blocked from recording 1:1 calls that can still record meetings and events because those fall back to the Global policies. If the new announcement policy follows the same pattern, admins may need to check it per scenario. The roadmap text doesn't say whether it will.
Section summary: The audio announcement makes participants aware. Consent is a separate control. Nothing in the roadmap entry says participants have to acknowledge the announcement, that they can refuse recording, or that it changes who is allowed to record.
Why an audio cue matters
A banner is easy to miss:
- A participant on a phone with the screen locked won't see it.
- Someone presenting full-screen may never notice it.
- A blind or low-vision attendee may only find out if a screen reader happens to announce it.
- Someone who walks into a conference room after the meeting started may have no idea the session is recorded.
A spoken announcement fixes most of that, which fits Microsoft's accessibility framing. It also helps with the odd case where someone starts transcription mid-meeting and nobody notices until a recap shows up later.
There are costs. In back-to-back meetings where someone recording out of habit is normal, a repeated announcement could start to feel like an airline safety briefing. That's probably why group scoping matters. Admins could turn it on for HR, legal, external-facing teams or regulated groups and leave it off for internal engineering stand-ups, or the reverse. This is my reading of the "specific groups" option, not documented guidance from Microsoft.
An audio announcement is not legal consent
This is the main caution for admins. An audio announcement makes sure people were told. It doesn't make sure they agreed. In places where all parties must consent to recording, or where your internal policy requires opt-in, the audio cue doesn't replace the explicit recording consent policy or your legal team's advice.
Microsoft's roadmap description only talks about informing participants and accessibility. It doesn't present the feature as a compliance or consent tool, and you shouldn't either.
Community advice on Microsoft Q&A for organizations that don't enforce explicit consent points the same way. It suggests stating recording and transcription intent in the invite, in the agenda, and out loud before recording begins. The new feature automates that last step.
Related change in the same window
This isn't the only recording change scheduled for late 2026. The M365 Admin message-center tracker reports that Teams will change the Record and transcribe automatically meeting option so organizers only see the automatic options their policies allow. That change includes a new "Record only" choice. According to the tracker, it is rolling out November-December 2026.
If both changes land around the same time, organizers could see new recording options and participants could start hearing announcements in the same few weeks. That's a good reason to send one combined update to users instead of two separate ones.
How to prepare now
You can't turn this on yet, but you can get ready:
- Check your current recording and transcription policies. Look at meeting, events and voice calling policies, and confirm which users are on Global and which have custom assignments. The audio policy can be scoped to groups, so knowing your group-based assignments will make targeting easier later.
- Decide which groups should get the announcement. Typical candidates are groups that record external calls, handle sensitive HR or legal matters, or include employees who rely on assistive technology.
- Bring legal and compliance in early. Agree that the announcement is a notification step and doesn't count as consent. Decide whether explicit recording consent should stay on, or be added, for certain groups.
- Line it up with your banner text. If you already use a custom in-meeting notification or privacy URL, make sure the written notice and the spoken one won't contradict each other.
- Write the user notice. Tell people they may start hearing an announcement when recording or transcription starts. That heads off "why is my meeting talking to me?" tickets.
- Watch the roadmap and Message Center. Wait for Microsoft's setup documentation before you look for the setting. Don't assume it will appear in the meeting policy page just because the banner customization lives there.
Bottom line: An audio announcement is a modest but useful addition to Teams' recording controls. It covers a real gap for participants who can't see or easily miss the on-screen banner. Until Microsoft publishes configuration details, treat December 2026 as an estimate, plan which groups should get it, and keep it separate from your consent requirements.