Use ADMX Policy to prevent Microsoft Teams from starting automatically after installation with Intune – Mobile-First Cloud-First

There can be scenarios where you don’t want Microsoft teams to start automatically for the user after it is installed , this is now possible with the new ADMX from July 9 for Office. At the moment there is only one policy settings that you can set with Microsoft Teams. You properly know how to update your Group Policy Central Store in a Active Directory, in this blog post I will describe how to do the same with Microsoft Intune and how you configure the settings that is is the policy today.

If you remember a few months back you will know that Microsoft Teams now is default when you are installing Office 365 Pro Plus, so when ever you are using the default installer of Office 365 Pro Plus your end user will get Teams by default.

Note : This policy setting only applies if you are installing or updating to Version 1905 or later of Office 365 ProPlus (or Office 365 Business).

To use this policy setting, download at least version 4882.1000 of the Administrative Template files (ADMX/ADML), which were released on July 9, 2019.

First you need to download the new ADMX files for Office from the above link.

Then you can that there is a new ADMX file teams16 and that is the one we need, open it with your favorite reader and copy the content you will be need it later.

Then go to the Microsoft 365 Device Management portal 

  1. Click Device configuration
  2. Click profiles
  3. Click Create profile

  1. Enter Name : ADMX – MSTeams
  2. Select Platform : Windows 10 and later
  3. Select Profile type : Custom
  4. Click Settings
  5. Click Add

  1. Enter name : ADMX – MSTeams
  2. Enter OMA_URI : ./Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/msteamsADMX/Policy/msteamsADMX
  3. Select Data type : String
  4. Value : Copy the content from teams16.admx

  1. Enter Name : Teams_PreventFirstLaunchAfterInstall
  2. Enter OMA-URI : ./User/Vendor/MSFT/Policy/Config/msteamsADMX~Policy~L_Teams/Teams_PreventFirstLaunchAfterInstall_Policy
  3. Select Data type : String
  4. Enter Value : 

After you have applied the profile to your end user you will be able to see it in the registry : HKEY_CURRENT_USERSOFTWAREPoliciesMicrosoftoffice16.0teams

Happy testing 🙂

Read more:

Use Group Policy to control the installation of Microsoft Teams

Related Posts