Windows 11 ships with a consumer-flavoured Microsoft Teams app pre-installed, separate from the enterprise Teams client your organization actually deploys. For most managed fleets you’ll want exactly one Teams app on the device (the enterprise version), and the consumer one is at best confusing and at worst a support-ticket generator. The good news is that you can remove the built-in Teams app with Intune in a fully automated, repeatable way. This post walks through three options to clean it up: a one-line PowerShell remediation that uninstalls the consumer Teams package per-user, a configuration-profile approach that hides the Chat icon for new and existing profiles, and the tamper-resistant route for locked-down deployments.
A built-in Teams client is shipped with Windows 11. This client can only be used with a personal Microsoft account, so it is usually not welcome in corporate environments where the managed enterprise Teams client is the only one users should see. How to remove this built-in client with the help of Intune I will show you step by step in this blog post.
Table of contents
Why remove the built-in Teams app with Intune
Before we jump into the configuration, it is worth understanding why so many admins choose to remove the built-in Teams app with Intune. The consumer client auto-pins itself to the taskbar via the Chat icon, prompts users to sign in with a personal account, and can sit side by side with the corporate client. That duplication confuses end users and increases the helpdesk load. By using Intune you get a centrally managed, scalable answer that applies the same policy to every enrolled Windows 11 device without touching machines one by one.
Remove the built-in Teams app with Intune using PowerShell
To uninstall the Teams client automatically we need a PowerShell script — more precisely, one line of PowerShell code. Because the consumer Teams package is installed per user, the script must run in the logged-on user context, which Intune supports out of the box.
Get-AppxPackage | Where-Object Name -like "*MicrosoftTeams*" | Remove-AppxPackage
I put this code line in a .ps1 script and uploaded it to my git repository. If you want the official background on how platform scripts are deployed, the Microsoft Learn documentation for the Intune Management Extension is the authoritative reference.
- Open the Intune admin center and navigate to Devices -> Scripts
- Click ADD
- Enter a name
- Click Next
- Upload the script
- Select Yes at “Run this script using the logged on credentials“
- Click Next
- Click Add Groups
- Select a Group and click Select
- Click Next
- Click Add
Remove the Chat Icon
Uninstalling the package is only half the job. To fully remove the built-in Teams experience you should also hide the Chat icon so it does not reappear, which we do with a configuration profile and an OMA-URI policy.
- Open the Intune admin center
- Navigate to Devices -> Configuration Profile
- Click + Create profile
- Select Windows 10 and later as Platform
- Select Template -> Custom as Profile type
- Click Create
- Enter a Name
- Click Next
- Click Add
- Enter the following information
- Name: RemoveTeamsIcon
- OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Experience/ConfigureChatIcon
- Data type: Integer
- Value: 3
- Click Save
- Click Next
- Deploy the script to a Group
- Click Next
- Click Next
- Click Create
Verify the result and next steps
After the policies sync, the consumer client is gone and the Chat icon no longer shows up, so you have successfully managed to remove the built-in Teams app with Intune across your fleet. If you want to harden things further for kiosk or shared devices, the AppLocker / WDAC route adds a tamper-resistant layer on top. For more Intune walkthroughs like this one, browse the other guides on my blog.
I hope I could help you and clearly explain how to remove the built-in Teams app with Intune from your Windows 11 devices. Thanks for reading this blog.
Stay healthy, Cheers
Jannik
[…] taskbar became fuller with Windows 11. In a previous blog I explained how to remove the teams icon or delete it completely. In this blog I want to explain […]