⚙️🪟💻CP - User Experience - Remove Chat Icon
That speech bubble Windows 11 plants in the taskbar is the consumer Teams, not the one you pay for. This removes the impostor.
What this policy is about 💬
Windows 11 ships with a little chat bubble pinned in the taskbar next to Search. It looks like Teams because it is Teams, just the wrong one: the consumer client that signs in with a personal Microsoft account, sitting right next to the managed Teams your business actually runs. This policy removes it, so there is exactly one Teams on the taskbar and it is the right one.
The consumer Chat button is not "Teams with fewer features". It is a separate app on a separate identity. Leaving it next to managed Teams is how users end up signed into the wrong one, wondering where their work chats went.
Why this matters 🕵️
Two near-identical Teams icons is a support ticket generator. A user clicks the consumer one, gets prompted for a personal account, signs in, and now their "Teams" has none of their work chats. The helpdesk fields the call, every time. Worse, that personal sign-in is an identity boundary you did not choose, on a device you manage. Removing the icon closes both: no wrong-client confusion, no stray personal account, and a cleaner taskbar with one less "what is this?" waiting to happen.
The managed Teams client stays exactly where it is, pinned by your standard taskbar layout. Only the consumer impostor goes.
🛠️ Configuration
Where: Intune admin center → Devices → Configuration → Create → Windows → Settings catalog → Experience.
| Setting | Value |
|---|---|
| Configure Chat Icon | Disabled |
| Assignment, include | All devices |
| Assignment, exclude | 🛡️🪟💻⛓️Group - Autopilot Devices - IoT 🛡️🪟💻⛓️Group - Autopilot Devices - W365 Boot |
Setting it to Disabled removes the button entirely; it is not just unpinned, and the user cannot bring it back from taskbar settings.
Caveats ⚠️
This tattoos. The setting writes to the Experience CSP and stays put. Excluding a device later does not restore the Chat icon on a machine that already received the policy. There is no exception group here, so no paired inverse is needed; if a tenant ever genuinely wants the icon back, that is a deliberate re-enable, not an unassignment.
Excluded device types never showed it anyway. IoT and W365 Boot endpoints run kiosk or bootstrap experiences with no normal taskbar, so the consumer Chat button was never going to appear. They are excluded to keep the profile clean, not because they need the icon.
The user override is gone on purpose. Once applied, pinning or unpinning Chat from Settings no longer works. The policy wins, which is the intended behavior on a managed device.
License and reversibility. Included in Business Premium. One-way by nature: plan a re-enable rather than an unassign if you ever need it back.
🔗 Related
- ⚙️🪟💻CP - User Experience - Disable Widgets: the same taskbar-decluttering instinct, aimed at the Widgets board.
There can be only one Teams on the taskbar, and it is the one you manage. ☝️