Government Teams users face another ******* month of filtered captions
Microsoft has confirmed that its Teams Live Captions profanity filter will remain switched on by default for certain government users until the end of August, a month later than originally planned. The filter, introduced in 2023, replaces swear words with asterisks in live captions, and Microsoft had intended to switch it off by default for new and unconfigured users to make captions more accurate and to support accessibility and regulatory alignment, including EU rules.
The change reached general availability for most users after being added to the roadmap in April with a June rollout target, but Government Community Cloud (GCC), GCC High and Department of Defense environments have seen completion slip from the end of July to the end of August. Microsoft has not explained the reason for the delay, though it remains an opt-in setting users could always toggle themselves.
- Teams caption profanity filter delay hits US government users specifically
- Rollout to disable filter by default now slips to end of August
- Microsoft hasn't explained why government environments lag behind
New here? Start with this
Microsoft Teams can display live captions during meetings, turning speech into text on screen. Since 2023, its profanity filter has replaced swear words in those captions with asterisks.
The filter has settings that determine whether it is on by default, and users can change it themselves. Microsoft’s planned default change is intended to make captions more accurate and support accessibility and regulatory requirements.
The later rollout affects users in Government Community Cloud, GCC High and Department of Defense environments, which are versions of Teams for US government organisations. The timing matters because captions help people follow meetings, including those who are deaf or hard of hearing.
Both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
Government institutions maintain particular standards of professional decorum in their communications, and a profanity filter by default provides a baseline level of appropriateness across diverse audiences without preventing users from disabling it if they choose. The concern is that removing such filtering in official government settings could undermine institutional values and the professional tone expected in government communications.
The case against
The profanity filter directly undermines the accuracy and accessibility that Microsoft itself identified as priorities. For deaf and hard-of-hearing users relying on captions, asterisks obscure meaning and context, making captions less useful rather than more. Additionally, the EU regulatory requirements mentioned point towards accuracy and accessibility taking precedence, and users should be able to control their own settings rather than having profanity replacement imposed by default.