The same batch of Teams updates also adds two other admin-relevant features: a pop-out call window for Teams in the browser, and an optional rule that makes participants accept custom terms before they can join a meeting. Each one has its own rollout schedule.
What the profanity policy actually does
Microsoft's roadmap entry describes it plainly: Teams administrators will be able to use a meeting policy to control whether profane words are masked in live transcription and saved meeting transcripts. Filtering remains on by default.
The setting appears in the Teams admin center. A new setting called Filter out profane words in live transcription will be available in the Teams admin center under: Meetings > Meeting policies > Meeting settings > Recording and transcription.
Here is the correction. Neowin reported that the policy lets Teams admins censor profane words in live transcription, but save them in meeting transcripts. Microsoft's own notice describes a single switch that controls both views together:
- When the setting is on, profane words are masked in live transcription and in the saved transcript.
- When the setting is off, words that would otherwise be masked can appear in live transcription and in the saved transcript.
Microsoft doesn't describe any mode that masks the live view but keeps the uncensored words in the saved file. It's either masked in both places or unmasked in both.
| Policy setting | Live transcription | Saved transcript | Live captions |
|---|---|---|---|
| On (default) | Masked | Masked | Each participant's own setting |
| Off | Can appear in full | Can appear in full | Each participant's own setting |
The organizer's policy decides
The setting follows the meeting organizer, not each attendee. The meeting organizer's assigned policy determines the behavior for the meeting. Microsoft's Message Center notice MC1478003 adds that organizers and co-organizers can't override it for individual meetings.
Topedia, a Microsoft 365 blog, spells out what that means in practice: if the filter is disabled for the organizer, the transcript shows profane words from all participants unfiltered. If one organizer's policy has filtering off, everyone who speaks in that organizer's meetings gets transcribed word for word, including guests.
Captions are a separate setting
Live captions keep their existing behavior. Each participant's live-caption profanity preference is unaffected, and live captions continue to use the participant's existing setting. That personal caption filter isn't new. Topedia notes that meeting captions have offered the option to enable or disable the profanity filter since 2023. The user-level toggle is labeled as Filter out profane words in live captions (does not control transcripts).
So one meeting can contain:
- A participant whose captions mask profanity
- A participant whose captions show it in full
- A live transcription view and a saved transcript, both controlled by the organizer's admin policy
None of these filters touch the audio. As Office 365 IT Pros noted when the caption filter first launched, if you're listening to the meeting, you'll hear the objectionable term in its full glory because Teams doesn't filter the audio feed. The same site also found that detection was imperfect: it detected some words and ignored others. Treat the masking as a convenience feature, not a guarantee about what ends up in the record.
Why the saved transcript matters
Captions are temporary. Transcripts are kept. According to Microsoft Learn, live captions give real-time subtitles but Teams doesn't save them, while transcripts are stored with meeting recordings in OneDrive and SharePoint. The searchable transcript, with timestamps and speaker attribution, stays available after the meeting.
Turning the filter off therefore changes the content of a stored file that other people can search and review later. The setting itself doesn't change retention periods or permissions. Your existing recording and transcript policies still apply.
Rollout status
The feature appears under roadmap ID 570467 and Message Center post MC1478003. In the archived roadmap entry, last updated November 4, 2026, it is marked Launched, with general availability in October 2026, for Android, desktop, iOS, Mac and web, in the Worldwide and GCC clouds. MC1478003 had scheduled Targeted Release for early to mid-October and general availability for mid to late October.
Topedia reports that the setting was first exposed through PowerShell, and that the admin center option should also be available in the Teams admin center > Settings & policies > Meetings later. If you can't see the toggle in the admin center yet, your tenant may simply not have the UI. Check before assuming something is broken.
How to roll it out
Microsoft says notify compliance, legal, and helpdesk teams that saved transcripts may contain profane words that were previously masked. Update internal transcript guidance if your organization changes the default policy behavior. A reasonable approach:
- Do nothing by default. Masking stays on, and MC1478003 says no action is needed to keep the current behavior.
- Write down why you need it. Microsoft says the option exists for workflows in which words that are currently masked need to remain visible in the transcript. Verbatim records for investigations or HR are one example. Keep a record of the reason.
- Use a custom meeting policy, not the Global one. Assign the custom policy only to the organizers who need verbatim transcripts. Changing the Global policy affects every user without a custom assignment.
- Brief helpdesk staff on why captions and transcripts may show different wording in the same meeting. That's the ticket most likely to come in first.
- Test it. Hold a short meeting under a test organizer, turn on transcription, and compare the live view with the saved file.
Teams on the web gets a pop-out call window
The second change is for people who use Teams in a browser. Roadmap item 569206 says browser users can pop a call out into a simplified window that stays available while they move away from, hide or minimize the browser tab or progressive web app (PWA) running the call. Microsoft says the goal is easier multitasking during calls.
The roadmap lists the web platform, the Worldwide (Standard Multi-Tenant) cloud and an October 2026 general availability target. Its most recent archived status, from October 14, is Rolling out, not Launched, so some tenants won't have it yet. The roadmap doesn't list required browsers or versions.
For users on locked-down machines, VDI, or Chromebooks who rely on Teams in a browser, this removes a long-standing annoyance: until now, switching away from the call tab meant losing sight of the call.
Admins can require consent before people join meetings
The third feature, described in Message Center post MC1454114 (roadmap ID 561914), lets organizations require participants to accept custom content before they join a meeting. Examples include terms and conditions, disclaimers, recording notices or responsible-AI use guidelines. Admins can preview what participants will see before turning it on, and acceptances are recorded in audit logs.
What to know:
- Off by default. Nothing changes unless an admin enables it.
- No exemptions. Organizers, internal users, external users and anonymous attendees all have to accept before joining a meeting covered by the policy.
- Languages. One default language plus up to four more. Participants see the version matching their device language, or the default if their language isn't configured.
- Rollout. Targeted Release from September 2026. Worldwide and GCC from mid-October to mid-November 2026. GCC High and DoD from mid-November to mid-December 2026.
Microsoft's PowerShell documentation for Set-CsTeamsMeetingPolicy lists an EnablePreMeetingConsent parameter. Setting it to true means every participant must accept a custom consent dialog before joining any meeting hosted by the tenant, and it requires at least one consent content entry to be configured. At the time of writing, that page still says the feature isn't fully released and that the setting will have no effect, so check your own tenant before relying on it. MC1454114 also says supporting Learn documentation is expected closer to general availability.
This adds a step to every join. Before you enable it, review the legal wording, test the translations, and tell external partners, who will see the prompt without warning.
Summary
- Profanity policy: One organizer-level switch masks or reveals profanity in both live and saved transcripts. It does not split the two. On by default, marked launched for Worldwide and GCC.
- Captions: Still controlled by each participant's personal setting. Audio is never filtered.
- Browser pop-out calls: Rolling out on the web in Worldwide.
- Pre-meeting consent: Opt-in, applies to everyone including organizers, logged for auditing, rolling out through mid-December depending on your cloud.
The profanity setting is the one that changes what gets stored. Before switching it off, decide whether your organization wants an exact record of everything said, and get compliance and legal teams to sign off first.