Forum Discussion
In Azure AD joined PCs, how to prevent Teams from Auto-Launch
Need to prevent Teams from auto-launching on my Azure AD joined PCs.
Have a read of this article:
Deploy Microsoft Teams with Microsoft 365 Apps - Deploy Office | Microsoft Docs
If your clients are native Azure-joined then you'd be looking to use an MDM like InTune to deliver any policy settings.
If your clients are hybrid-joined, you can leverage Active Directory group policy.
Cheers,
Lain
Hi Lain,
I did use Intune's "Prevent Microsoft Teams from starting automatically after installation (User)"
but sadly it does not work for me. I have deployed it to ALL DEVICES and ALL USERS.
I did use Intune's "Prevent Microsoft Teams from starting automatically after installation (User)"
but sadly it does not work for me. I have deployed it to ALL DEVICES and ALL USERS.
Yeah, fair enough.
Did you read the "tip" in the green box?
If you are deploying the policy setting after Teams has already been used by the user, it won't work just by deploying the setting on its own. You need to include the script linked inside that green "tip" box.
That script needs to be run per user, not just once per machine.
Pretty clunky solution in my opinion, but this is how things are these days.
Cheers,
Lain
- I may be overthinking this but, the script you mentioned has a Group Policy aspect that would not pertain to us because we are Azure joined PCs. Please see below,
"If you want to use the "Prevent Microsoft Teams from starting automatically after installation
Group Policy setting, make sure you first set the Group Policy setting to the value you want
before you run this script."
I will deploy this script anyways and give you an update.- Yeah, it may seem that way but if you're running Windows Enterprise or Education (which is effectively almost just a different SKU of Enterprise) then group policy is still highly relevant - even on Azure-only joined computers (since the group policy engine is part of the Windows client, not an exclusive component of something like on-prem Active Directory.)
InTune can and does leverage the local group policy engine, meaning that statement is still relevant since you could definitely have InTune deploying group policy to Azure-native clients.
In an InTune context, the script heading's really just saying, "hey, if you've already deployed Teams, make sure you have deployed the policy setting via InTune first, and then deploy me - the script - second."
Cheers,
Lain