How can we make Microsoft Teams better?

Let admins manage updates

For corporate use please let stop automatic updates and user side updates.
Admins can deploy updates in a managable way

287 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • Anonymous commented  ·   ·  Flag as inappropriate

    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.

  • Jon Tydda commented  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    application white-listing + auto updating teams client is a killer.
    any update?

  • Ewald Bracko commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    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.

  • todd jones commented  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    I has got a strong demand from our customers.Customer need client update manegement of Teams.

  • Craig Watson commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

  • Kunio Sato commented  ·   ·  Flag as inappropriate

    Customer need client update manegement of Teams.It is absolutely necessary for consumption.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Any time update kicks in it distracts my workflow by redirecting to the Teams window a few times during auto-update.

    I wish to disable it but there is no option right now.

    Please add an option to disable auto-upadates.

  • Takuya Sugiyama commented  ·   ·  Flag as inappropriate

    If there are no function of client update management, company admins cannot control their network load or estimate network capacity.
    So it would be great to manage updates like Office 365 ProPlus.

← Previous 1

Feedback and Knowledge Base