Close Menu
Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    Facebook X (Twitter) Instagram
    Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    • Home
    • Intune
    • Windows
      • Modern Workplace
    • macOS
    • Android
    • iOS
    • Automation
      • Logic Apps
      • Intune Monitoring
      • GitHub
    • Security
      • Passwordless
      • Security
    • Speaking
    • About me
    Peter Klapwijk – In The Cloud 24-7Peter Klapwijk – In The Cloud 24-7
    Home»Intune»Remove the built-in Teams client and chat icon from Windows 11
    Intune

    Remove the built-in Teams client and chat icon from Windows 11

    Peter KlapwijkBy Peter KlapwijkOctober 8, 2021Updated:August 31, 2022164 Mins Read

    After modifying the start menu of Windows 11, I also want to remove the built-in Microsoft Teams client from the OS. And besides that, I also want to remove the chat icon from the taskbar.

    I want to remove these because the chat icon starts the Teams client, and this client can only be used with a personal Microsoft account. So as long as we can’t use this client with corporate accounts, I don’t want this client on my corporate Windows devices.

    Let’s see how easy it is to remove the Teams client and chat icon from Windows 11.

    Remove the built-in Teams client

    For Windows 10 we could use the store apps, and Microsoft Intune to uninstall the built-in Windows Store apps. For Windows 11, this seems not possible because of the changes in the Store.

    Another solution for Windows 10, and also for Windows 11, is to use a PowerShell script to remove those apps from Windows. I first used the approach to use a PowerShell script, wrapped it as win32 app, and deployed it (during Autopilot enrolment). But this Microsoft Teams app seems to be installed over and over again (by Windows updates I assume), so I switched to using a script with Proactive remediations which is available with Microsoft Intune.
    The benefit of using proactive remediations is that these scripts are not run once but at a repeated schedule. So if the app is reinstalled again, at the next scheduled run it is also removed again.

    Proactive remediation consists of a detection script and a remediation script. In the remediation script, we check if the Teams app is installed by using the Get-AppxPackage command. But we first need to determine what the name of the app is. To retrieve the name from the Teams client, run below in PowerShell:

    Get-AppxPackage -Name *teams*

    With the remediation script, we remove the Teams app. This can be done by running:

    Get-AppxPackage -Name MicrosoftTeams | Remove-AppxPackage -ErrorAction stop

    With this information, we can create two simple scripts to get the job done.

    This is our detection script:

    #Script detects the new Microsoft Teams consumer app on Windows 11.
    
    if ($null -eq (Get-AppxPackage -Name MicrosoftTeams)) {
    	Write-Host "Microsoft Teams client not found"
    	exit 0
    } Else {
    	Write-Host "Microsoft Teams client found"
    	Exit 1
    
    }

    And this is our remediation script:

    #Script removes the new Microsoft Teams consumer app on Windows 11.
    #App is removed because this app can only be used with personal Microsoft accounts
    
    try{
        Get-AppxPackage -Name MicrosoftTeams | Remove-AppxPackage -ErrorAction stop
        Write-Host "Microsoft Teams app successfully removed"
    
    }
    catch{
        Write-Error "Errorremoving Microsoft Teams app"
    }

    Let’s implement the proactive remediation.

    • Sign in to the Microsoft Endpoint Manager admin center
    • Browse to Reports – Endpoint Analytics – Proactive remediations
    • Click +Create script package
    • Enter a Name and Description (optional)
    • Click Next
    • Upload the Detection and Remediation script
    • Set Run this script using logged-on credentials to Yes
    • Set Run script in 64-bit PowerShell to Yes
    • Click Next

    We can assign the remediation for example to All devices and use a filter to only run the scripts on Windows 11 devices.

    When we click on Daily (under schedule) we can edit the schedule based on which the script is run.

    The remediation script is scheduled and will remove the Teams app on a daily base.

    Remove the chat icon

    To remove the chat icon from the taskbar, we have the Configure chat icon setting available in the Settings Catalog in Intune.

    • Sign in to the Microsoft Endpoint Manager admin center
    • Browse to Devices, Windows, Configuration profiles
    • Click +Create profile
    • Select Windows 10 and later as Platform
    • Select Settings Catalog as Profile type
    • Click Create
    • Give the profile a Name
    • Enter a Description (Optional)
    • Click Next
    • Click Add settings
    • Scroll down to Experience and select Configure chat icon
    • Set Configure chat icon to Hide

    Save the configuration profile and deploy it to your Windows 11 devices.

    End result

    The end result is of course that the chat icon is removed from the taskbar, and I’ve only left the Microsoft Teams client which is installed as part of the Office suite.

    That’s it for this post. Thanks for reading.

    EMS Intune MEM Microsoft 365 Microsoft Endpoint Manager Windows Windows 11
    Share. Facebook Twitter LinkedIn Email WhatsApp
    Peter Klapwijk
    • Website
    • X (Twitter)
    • LinkedIn

    Peter is a Security (Intune) MVP since 2020 and is working as Modern Workplace Engineer at Wortell in The Netherlands. He has more than 15 years of experience in IT, with a strong focus on Microsoft technologies like Microsoft Intune, Windows, and (low-code) automation.

    Related Posts

    Create a Windows Driver update approval report with Logic Apps

    July 18, 2023

    Configure Cloud Site List Management for IE mode

    October 21, 2021

    Export Edge favorites to use in an Intune profile or GPO

    April 9, 2021
    View 16 Comments

    16 Comments

    1. Michaël Van den Steen on October 15, 2021 11:27

      Thanks a lot for another useful article!

      Reply
    2. T.J. Smith on October 27, 2021 23:30

      How do you do your detection rule in Intune?

      Reply
      • Peter Klapwijk on October 28, 2021 10:32

        In the example script, I use $StoreResults to write a registry key. If the script runs successfully, it writes Success under that key.
        That’s used as a detection method.

        Reply
      • T.J. Smith on October 28, 2021 17:47

        Reading is hard for me apparently. Re-read the article and answered my own question.

        Reply
        • Peter Klapwijk on October 30, 2021 13:56

          🙂 No problem T.J.!

          Reply
    3. ed hixon on December 17, 2021 01:40

      Have you seen the personal Teams app reappear after uninstalling with a PS script like this? Others claim to have seen it, and use a different method to permanently solve the problem.
      TIA,
      Ed

      https://thenewnumber2.com/2021/10/25/removing-the-built-in-microsoft-teams-app-with-intune-take-two-a-better-approach/

      > My friend Loryan Strant (Check out his awesome wisdom here) reached out and mentioned that he has seen some occurrences of the built-in Teams app reappearing some time after the PowerShell Script has been run to remove the App.

      Reply
      • Peter Klapwijk on December 31, 2021 15:15

        That’s why I changed the approach to using Proactive Remediation and changed the article.

        Peter

        Reply
        • Carl M on February 9, 2022 20:03

          So you are saying that this Proactive Remediation as listed above, will continue to keep the Teams built-in app uninstalled after the initial run? No manual intervention going forward?

          Reply
    4. chris on February 20, 2022 22:50

      awesome work – i was able to follow the article and it delivered on the first attempt – good stuff man ! keep it up

      Reply
    5. George G. on April 19, 2022 17:31

      Since this is using logged-in user credentials, will it work for users that are not admins on their devices? Or, will we have to add a “-allusers” parameter to the script?

      Reply
      • Peter Klapwijk on April 20, 2022 09:51

        Yes, it works for standard users.

        Reply
    6. Sven on April 29, 2022 14:19

      Thanks for the blogpost!

      For simplicity the Teams chat icon can also be removed via the settings catalog as an extra option 🙂
      To remove the Chat icon using Intune – Settings Catalog, do the following steps:

      Create a new Configuration Policy.
      Search for Experience.
      Select Configure Chat icon.
      https://docs.microsoft.com/en-us/troubleshoot/windows-client/application-management/managing-teams-chat-icon-windows-11

      Reply
    7. Tony Spencer on May 24, 2022 07:24

      As per
      https://docs.microsoft.com/en-us/mem/analytics/overview

      Proactive remediations also requires users of the devices to have one of the following licenses:

      Windows 10/11 Enterprise E3 or E5 (included in Microsoft 365 F3, E3, or E5)
      Windows 10/11 Education A3 or A5 (included in Microsoft 365 A3 or A5)
      Windows 10/11 Virtual Desktop Access (VDA) per user

      So won’t work with Microsoft 365 Business Premium?

      Reply
      • Peter Klapwijk on June 26, 2022 09:36

        It will most likely work on these devices, but you don’t meet the license requirements. So, that’s a no go.

        Reply
    8. Richard on June 28, 2022 05:14

      The proactive remediation script does not work for me I’m afraid, I had to add -Allusers after Get-AppxPackage in the detection script. And then the same thing after Get-AppxPackage and Remove-AppxPackage in the remdiation script. Nevertheless thank for the article it got me to where I need to be :).

      Detection
      if($null -eq (Get-AppxPackage -Allusers -Name MicrosoftTeams))
      {
      Write-Host “Microsoft Teams client not found”
      exit 0
      }
      Else{
      Write-Host “Microsoft Teams client found”
      Exit 1
      }

      Remediation
      #Script removes the new Microsoft Teams consumer app on Windows 11.
      #App is removed because this app can only be used with personal Microsoft accounts

      try {
      Get-AppxPackage -Allusers -Name MicrosoftTeams | Remove-AppxPackage -AllUsers -ErrorAction stop
      Write-Host “Microsoft Teams app successfully removed”
      }
      catch {
      Write-Error “Error removing Microsoft Teams app”
      }

      Reply
    9. Ffej on January 18, 2023 00:47

      On M$ EPM AC it gives me errors saying I’m not authorized to view it.. Any idea why? 11 build is from M$ site…

      Reply
    Leave A Reply Cancel Reply

    Peter Klapwijk

    Hi! Welcome to my blog post.
    I hope you enjoy reading my articles.

    Hit the About Me button to get in contact with me or leave a comment.

    Awards
    Sponsor
    Latest Posts

    Hide the “Turn on an ad privacy feature” pop-up in Chrome with Microsoft Intune

    April 19, 2025

    How to set Google as default search provider with Microsoft Intune

    April 18, 2025

    Using Windows Autopilot device preparation with Windows 365 Frontline shared cloud PCs

    April 13, 2025

    Using Visual Studio with Microsoft Endpoint Privilege Management, some notes

    April 8, 2025
    follow me
    • Twitter 4.8K
    • LinkedIn 6.1K
    • YouTube
    Tags
    Administrative Templates Android Automation Autopilot Azure Azure AD Browser Conditional Access Edge EMS Exchange Online Feitian FIDO2 Flow Google Chrome Graph Graph API Identity Management Intune Intune Monitoring iOS KIOSK Logic Apps macOS MEM MEMMonitoring Microsoft 365 Microsoft Edge Microsoft Endpoint Manager Modern Workplace Office 365 OneDrive for Business Outlook Passwordless PowerApps Power Automate Security SharePoint Online Teams Windows Windows 10 Windows10 Windows 11 Windows Autopilot Windows Update
    Copy right

    This information is provided “AS IS” with no warranties, confers no rights and is not supported by the authors, or In The Cloud 24-7.

     

    Copyright © 2025 by In The Cloud 24-7/ Peter Klapwijk. All rights reserved, No part of the information on this web site may be reproduced or posted in any form or by any means without the prior written permission of the publisher.

    Shorthand; Don’t pass off my work as yours, it’s not nice.

    Recent Comments
    • Peter Klapwijk on Using Windows Autopilot device preparation with Windows 365 Frontline shared cloud PCs
    • John M on Using Windows Autopilot device preparation with Windows 365 Frontline shared cloud PCs
    • Christoffer Jakobsen on Connect to Azure file shares with Microsoft Entra Private Access
    • Ludo on How to block Bluetooth file transfer with Microsoft Intune
    • RCharles on Automatically configure the time zone (during Autopilot enrollment)
    most popular

    Application installation issues; Download pending

    October 1, 2024

    Restrict which users can logon into a Windows 10 device with Microsoft Intune

    April 11, 2020

    How to change the Windows 11 language with Intune

    November 11, 2022

    Update Microsoft Edge during Windows Autopilot enrollments

    July 9, 2024
    Peter Klapwijk – In The Cloud 24-7
    X (Twitter) LinkedIn YouTube RSS
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.

    Manage Cookie Consent
    To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
    Functional Always active
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
    View preferences
    {title} {title} {title}