Let admins manage updates
For corporate use please let stop automatic updates and user side updates.
Admins can deploy updates in a managable way
Yay — we’ve started work on this!
Shaun Wells commented
The ability to control updates is crucial in a financial institute, as we're governed by many controls and policies - Controlling what versions of software have been deployed into the Enterprise is critical to us.
Kanth Kolluru commented
Hi, Is there any progress on this? Auto update seems to have been compromised with a vulnerability identified where it can be tweaked to download package from any source instead of just Microsoft teams update packages. Being able to control the auto update behavior has become all the more crucial now.
Arti R commented
Hi any update on this would be very welcome.
The certificate used to sign the application changed last week and this impacted many users since we block executable files from running in the AppData folder structure except for trusted signed apps. Since we cannot control when the updates are executed, we can hardly update the trusted certificates list in advance making this security measure harder to manage.
Any update on this?
Jon Tydda commented
I do all my other MS updates via SCCM, why is Teams different? I want all my users to be on the same (approved and tested) version, not necessarily the latest version.
application white-listing + auto updating teams client is a killer.
John Marques commented
does anyone have status on how to disable auto updates for MS Teams client?
echoing Ewald's comment
Ewald Bracko commented
Also I'd like to add:
Don't create an Teams application icon on the user desktop by default. This needs to be an administrative option.
Ewald Bracko commented
The best way to achieve this would be to install Teams into the %ProgramFiles% folder in general. Create an enterprise-specific install for that if necessary.
Use the user profile folders only to store user specific configuration settings and user specific temporary data like cache files.
Create and install a system service that handles the Teams Update. The Teams update mechanism should be limited to updating the central installation folder only and it should be avoided to do registry manipulations, especially not within the HKLM hive of the registry.
The Teams Updater service should first download the update package locally. Then it should check if any instance of Teams is running and delay the update process in that case for some minutes until doing a recheck. Updates should be deployed only if Teams is not being used on the system.
That way Teams will be well suited for any kind of business environment, even RDS and Citrix.
This update issue kicked me from Teams during a meeting where we were looking at a planner. There was no evidence of what was happening, no notification, just disappeared and then restarted. Not really acceptable behaviour.
Teams can't just "decide" to auto update at will
and for windows too.
todd jones commented
client runs in an RDS environment with 40 users. VDI maybe the next step. BUT since adding Teams a month ago, the update creates a storm of user activity since runs on each user session individually and slows the server to 100% usage. Be nice to find a solution that updates is managed and maybe after hours or weekend and not immediately at run time.
There is also a downside on the desktop app that when it automatically updates our antivirus blocks it and then we cant use it for a while until it gets approved, such a hassle.
Scott Yates commented
Please allow us to disable this while we have the app loaded. It is fine to update when we first load or we we choose to re-load the app, but not while we are in flow, and coding. It distracts developers and we lose time getting back into flow.
I has got a strong demand from our customers.Customer need client update manegement of Teams．
Craig Watson commented
having something like below would be helpful
1. set a random back off timer for when the update is downloaded
2. add a dns record to redirect updates to a server that has the new bits within the organization.
Noriko Yamashita commented
In the almost case of Japanese customer, they doesn’t separate their network for their core systems and communication infra etc. If some Office 365 teams update is hugged their network systems, IT admin is nervous to keep to use Office 365 due to no control and no estimated network capacity.