Please publish the update history for Microsoft Teams Client on the Web. I can check the list of Update history for Office 365 ProPlus on t
Please publish the update history for Microsoft Teams Client on the Web.
I can check the list of Update history for Office 365 ProPlus on the web.
We also want to publish information on the Web, so that I can see the details of added and updated features for Microsoft Teams clients.
Thank you for your feedback. You can check the update history at https://support.microsoft.com/office/what-s-new-in-microsoft-teams-d7092a6d-c896-424c-b362-a472d5f105de. The team is exploring options to improve the update history list, and the possibility of including build numbers.
14 commentsComments are closed
We also have this problem: 14 different versions on about 1000 pcs... some updates, other not.
Please Microsoft, provide a history list and the ability to compare and download the latest.
Now, we have warnings on 1.3.00.3563 that we have only 30 days to upgrade if we want to continue using this software. Did check, nothing new available. Incredible...
Please help !
Raul Villegas commented
When trying to determine what version the user should be on it would help
Still no good version history site to address versioning confusions you are delivering by having linked old versions of Teams on Docs while the demand of VDI installations of Teams keeps growing? Thanks
Pick latest version number: https://www.techspot.com/downloads/6976-microsoft-teams.html
Download MSI: https://statics.teams.cdn.office.net/production-windows-x64/<insert latest version here>/Teams_windows_x64.msi
I typically go to https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi this document for my Teams Setup with VDI. We use VMware with non-persistent disks. The link to the 64-bit version is to version 1.3.00.21759. It has been this for quite some time. I know there are newer versions of Teams. In a VDI setup, should 1.3.00.21759 be used or can newer versions be used? Should the link be updated?
I agree, we should have an update history list, just like O365 Client.
I concur, for a tool that is also being heavily pushed for corporate level communication and collaboration.
The lack of update history is short sighted and is one of the items gathered in the first steps of basic troubleshooting for support teams.
How do I know if I have the latest version or if something is wrong? I tell it to manual check for updates, but no indication if I have it... I hear about cool new features rolling out, but have no clue if I need an update for them to appear or work... Very poor transparency Microsoft...
Unbelievably that Microsoft do not publish release notes or any version summary information for Teams. Enterprise Sysadmins are really been left out of the loop and they are supposed to manage and support this mess.
Office 365 Japan Support Team commented
*English follows Japanese
VDI 環境用の Microsoft Teams バージョンの公開について
Publish the version of Teams in the VDI environment
Please create some public information about the difference between the normal desktop client version of teams and the one in the VDI environment.
In cases where there is a difference, please create release notes for the VDI environment version.
Also, can Micrsoft start including the version number for the desktop, mobile, web client on all documentation. Using the version number to make sure all of your employees are running the same version is easy but trying to use that same number to make sure you are up-to-date with Microsoft's latest version is a pain.
James Bainbridge commented
Genuinely surprised that this is not available to view. Every other product has a version number and associated history. It's impossible to know if you are actually up to date.
I need this too. We are deploying Teams to our enterprise and we would like to always deploy the latest package. Having the update history available publicly will allow us to watch for this and ensure we stay ahead of the curve.
Alan Whitten commented
The Microsoft Teams Client shows the currently installed version. It would be helpful for admins to be able to compare the version installed against the update history.