Prerequisites:

• MS Teams needs to have been installed using the Teams Machine-Wide Installer option:
  msiexec /i Teams_windows_x64.msi OPTIONS="ALLUSERS=1”
   

• User needs to have logged in completely at least once to MS Teams, (the status icon will be visible).

  

1. Create a new Application Settings Manager policy for MS Teams on either the Computer or User side, depending on whether the GPO applies to computer or user objects. If the GPO applies to the OU containing only computer objects, then create the policy on the computer side, if the GPO applies to the OU containing only User objects, then create the policy on the user side, etc.
    

2. Enable the three settings (see image below) in the Microsoft Teams policy, then click Ok to save the settings.
   
   Note: Only the underlined settings are being reapplied when the policy processes, the other options are not being changed.

   

3. Next, create a new Scripts & Triggers policy within the same GPO, under the same configuration side, user or computer that you used in Step 1.
   
   Note: If applying the policy on the computer side choose switched mode like in the screenshot below.

   ​

4. At the “On apply action” screen select “PowerShell script” from the dropdown, then in the main text window, paste in the script below, check the two options “Run script as user” and “Run interactively”, then click “Next”.

   

5. Click “Next” at the “On revert action” screen to skip that screen, then at the “specify process mode” screen choose the “On trigger” option, then choose “Logon” from the drop down before clicking “Next” to continue.
   
6. At the “Policy settings” screen give the policy a descriptive name then click “Finish. 
7. Lastly, test the policy by logging into a computer as a user that should receive the policy.  If everything works Teams should open minimized and you should see the MS Teams icon in the systray. 

Note:  Users may initially see two MS Teams icons for a few seconds in the Systray at the same time, however, one of the icons will disappear shortly. Also, if this is the first time logging in since the policy was applied it may take a 2^nd login for the policy to kick in.