Blog Post

Microsoft Teams Community Blog
4 MIN READ

Overview of Teams Desktop Client Auto Update Process

SanjayKumar_Pendyala's avatar
SanjayKumar_Pendyala
Brass Contributor
Nov 03, 2021

Microsoft Teams has revolutionized the communications and the collaboration experience for Office 365 users across the Globe with a suite of all the power-packed collaboration features into one Technology and providing users with a Seamless and most powerful Collaboration tool.


The rich collaboration features of Microsoft Teams can be leveraged by users across various platforms wiz. Desktop, Mobile or Web client. However, owing to integration with the Office applications and Intranet network compatibility for leveraging all the rich collaboration features, majority of the users across an organization prefer the Teams Desktop client for the world class user experience. Microsoft has been investing enormous efforts in roll out of the latest features for enhancing user experience regularly and predominantly across Microsoft Teams Desktop Client version, hence this article would be mostly confided to Teams desktop client auto update process on Windows machines.


Microsoft has been agile in terms of the MS Teams latest features roll out in form of upgraded versions of Teams Desktop client packages on a frequency of every two weeks and usually on a Tuesday.Teams desktop client by virtue is enabled for Auto updates as mentioned in below screen shot and is a seamless process to get the users upgraded to latest version.


On a high level the Teams Desktop client Auto update follows the given process, check for latest updates every few hours behind the scenes, download it when package available, and then waits for the computer to be idle before silently installing the update and provide the user with latest features.

 

Step 1: Check for Updates

Teams desktop client does check for availability of latest version of Teams desktop client by running the below mentioned query from the tool in the context of given installed user account.

 

https://teams.microsoft.com/desktopclient/update/X.X.X.X/windows/OSBit?ring=general


Here X.X.X.X would be the current version of the Teams Desktop client app.


In case if there is a latest desktop client version available for the given user, there is a web response on the given web query as mentioned below with values.

 

isUpdateAvailable, nugetPackagePath, releasesPath, url, scenarioCode, deltaPackagePath, deltaReleasesPath

 

Based on the response Teams Desktop client proceeds with further steps.


In case if the available version of Desktop Client is latest there is no web response on the above web query and no further action is required.


Step 2: Download the latest Package

Based upon the web response in above the latest package of the Teams desktop client is downloaded from the below mention URL across to your local computer location at %localappdata%\Microsoft\Teams\packages. The package is downloaded in the format of NuPKG (NuGet Package) format.


https://statics.teams.microsoft.com/production-windows/Y.Y.Y.Y/Teams-Y.Y.Y.Y-full.nupkg

 

Here Y.Y.Y.Y is the latest version of the available MS Teams.


Step 3: Latest Package Installation

Teams client Auto update is a pretty seamless process which is predominantly handled on background without any intervention from logged in user and it is usually designed to install the latest available downloaded package as soon as the system is idle.


Few of the scenarios when the Teams Desktop client Auto update process might be blocked even after downloading of the latest package are mentioned as below.

  • In case if the Microsoft Teams has been not installed on Default location, this might prevent completion of Teams Auto update installation process.
  • If a user powers off the computer when finished using Teams, Teams will have no way to run the update process.

 

Step 4: Installation Completed

Once the installation process has been completed the given Teams Desktop client’s current version is updated to the latest version and the latest features are rolled out across to given user.

 

Note: 

Microsoft deploys an internal algorithm for phased roll out of MS Teams latest versions to avoid any Network choking issues while downloading the packages with low bandwidth client locations. That’s the reason you might find users in different versions.


For manual download of the latest Teams client package available for given user, Users can use web client by navigating to ellipsis and clicking on Download Teams Desktop app. The web download location for Teams executable package would be from the below mentioned URL.


https://statics.teams.cdn.office.net/production-windows-x64/Y.Y.Y.Y/Teams_windows_x64.exe

 

Bio:
Sanjay Kumar has a decade plus of experience across architecting, operations and maintenance of Microsoft collaboration and cloud Technologies. Currently serving as an Infrastructure Architect with Cognizant Technology Solutions. He has a technical expertise across architecting and administration of SharePoint On-premises, Azure IAAS/PAAS, Microsoft 365 (across Exchange Online, SharePoint Online, Teams, Azure AD, Yammer, Power Automate platform and Graph API automation) and has been working for few of the fortune 500 clients.

 

To write your own blog on a topic of interest as a guest blogger in the Microsoft Teams Community, please submit your idea here: https://aka.ms/TeamsCommunityBlogger

 

 

Published Nov 03, 2021
Version 1.0

9 Comments

  • MatiasK-SMG's avatar
    MatiasK-SMG
    Copper Contributor

    Hello

     

    Microsoft Teams Classic clients are being automatically upgraded at the same time, causing saturation of our internet links.

     

    How we can control it?

     

    Thanks

  • MattJTHunt's avatar
    MattJTHunt
    Copper Contributor

    danny_grasso thanks for coming back. I just picked this up again, and seems MS have now addressed this is the newest release.

     

    I'm currently running version 23335.232.2637.4844 of Teams which has installed the Microsoft Teams Add-in for Microsoft Office version 1.23.33413. I no longer have Classic Teams installed and intend on removing Classic from our estate gradually to prevent the CVEs. Cheers.

  • danny_grasso's avatar
    danny_grasso
    Brass Contributor

    MattJTHunt we seem to be getting success in deploying the Teams classic client in this way. Still means that whenever a vulnerability is found I need to update the deployment through Intune.

     

     

  • MattJTHunt's avatar
    MattJTHunt
    Copper Contributor

    danny_grasso this is also the position I find myself in currently. We've tested rollout of the new Teams client, and likewise are finding the Classic client is causing Defender to pick up on old versions where it is not following the auto-update cycle.

     

    Curious how you are combating this, and if you've had any success with your Intune Win32 app deployment in updating the Classic client?

     

    I've been doing manual remediation until now but am eager to find an automated solution.

  • danny_grasso's avatar
    danny_grasso
    Brass Contributor

    Ian_Omar In my experience if the Teams app is not automatically starting, then it will not update. This has become more apparent as we've started trialing the new Teams client. We are seeing warnings from our Microsoft Defender for Endpoint Vulnerability Management that Teams has vulnerability that are not addressed and shows Teams is not updated, however when we open the new Teams client and check settings, it is showing up to date.

    It appears that the older classic Teams binaries are still there and are not being updated. Confirmed with the version showing in the control panel and on the classic Teams executable. Checked against builds here https://learn.microsoft.com/en-us/officeupdates/teams-app-versioning and downloaded/ran the specific Teams client using the method SanjayKumar_Pendyala indicates above. Testing deployment with an Intune Win32 app until we see what the Teams migration path looks like for these users.
    Other unverified option is to run the classic Teams Update.exe in the users profile folder but appears to require update location information anyway.

  • Ian_Omar's avatar
    Ian_Omar
    Copper Contributor

    Do Teams auto-update when the application is closed? Does it have to be opened or running for the auto-update process to work.

     

  • Bruce Bading's avatar
    Bruce Bading
    Copper Contributor

    Teams has been breached at one of our customers after an inactive user logged in and launched a vulnerable version of teams and zero click and zero-day exploits hit. We now run a auto removal of all Teams once per month so that only current users re-install the updated version of teams. Whey teams has a per-user install is a bad design as it accumulates vulnerabilities quickly for inactive users that have not updated for many months after they sign in recently. Developers focus on functionality instead of security (ISACA) and this needs to change.

  • Hello Markus_Johansson Thanks a lot for an interesting question. However seems like MS has never released/published any release notes for Microsoft Teams desktop clients and are being only updated and deployed with a frequency of every 2 weeks and most of the users' desktop clients are being updated as per the auto update process in place. 

     

    First of all as a best practice I would suggest everyone to be always be on the latest available MS Teams Desktop client version for leveraging most of the latest features and at same time for also being secured and compliant. 

     

    However the easiest way to backtrack the installed previous versions of MS Teams on a given desktop/machine can be tracked from SquirrelSetup-Teams.log of MS Teams Diagnostic Logs (Use Alt+Ctrl+Shift +1 for downloading the Ms Teams Diagnostic logs) and the given file can be located under the Desktop folder and might give insights into the versions installed across your machine previously.

     

    Though its not recommended to roll back to a previous version until any serious issues/concerns with latest versions impacting the productivity, the below mentioned download file link did work absolutely fine and downloads the required backtracked version which can be verified by navigating to Properties and Details and check the version details of the given executable as shown in below screenshot.

    https://statics.teams.cdn.office.net/production-windows-x64/1.4.00.29473/Teams_windows_x64.exe

     

     

    As per my previous checks with Public Preview there has been no changes in the Teams desktop client version, rather by  enabling the Teams Public Preview by navigating to Ellipsis and Select About → Public preview. Select Switch to Public preview. would enable preview features which might be still under development and not usually available under Public release. 

    Hope this answers and clarifies your queries.

  • SanjayKumar_Pendyala well written. 
    Is there a list of released versions publicly available? 
    I had version 1.4.00.29473 installed on my machine. But when I try to grab the exe I can't
    https://statics.teams.cdn.office.net/production-windows-x64/1.4.00.29473/Teams_windows_x64.exe

    Seems the latest is 1.4.00.29469
    https://statics.teams.cdn.office.net/production-windows-x64/1.4.00.29469/Teams_windows_x64.exe 

    Just curious to understand which version I had? 
    Also wondering if the client version is changed if I toggle to Public preview sometimes?