With the recent General Available of New Teams on Mac, there are changes that impact the management of some tenants regarding new Teams and Microsoft Teams classic (formerly Microsoft Teams).<\/p>\n
\u00a0<\/p>\n
Users can switch seamlessly between New Teams and Microsoft Teams classic via an in-app toggle.<\/p>\n
However, there are effects on tenant management that administrators should be aware of.<\/p>\n
Note:<\/strong>\u00a0this is the same bundle ID for the preview version which was named Microsoft Teams (work preview)<\/p>\n \u00a0<\/p>\n MacOS .app file name changes with the recent General Available of new Teams:<\/em><\/p>\n \u00a0<\/p>\n If you have an MDM implementation that periodically checks whether Microsoft Teams is installed on a given Mac device in your tenant based upon the .app name, and then installs a version of Teams if it isn\u2019t present, then you may find that devices can have two version of Teams classic installed on the device: Microsoft Teams and Microsoft Teams classic.<\/p>\n If this happens, it should not require any action to remove the duplicate old Microsoft Teams version. When the old Microsoft Teams version next updates, the machine will be left with a single Microsoft Teams classic version on the device.<\/p>\n \u00a0<\/p>\n Daily users of the now Microsoft Teams classic, should have automatically received an update that changed the name of the app from Microsoft Teams to Microsoft Teams classic in September via built-in custom updater.<\/p>\n User who rarely open Teams should have recently received the update via Microsoft Auto-update which was released on 10\/10\/23<\/p>\n The latest Microsoft Teams classic build can be downloaded here from the Teams_osx.pkg download page (https:\/\/go.microsoft.com\/fwlink\/?linkid=869428)<\/p>\n Builds with the original \u201cMicrosoft Teams.app\u201d naming convention \u2013 626463 and earlier<\/p>\n Builds with the new \u201cMicrosoft Teams classic.app\u201d naming convention \u2013 627656 and later<\/p>\n Important! Ensure that any new MDM deployments that you may use include a build that uses the Microsoft Teams classic.app convention, meaning with a build 627656 and later.<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n For general information on upgrading and policies related to deployment of the new Teams, see:<\/p>\n\n
Important MDM scenarios these changes can impact:<\/strong><\/h3>\n
Transition Timeline for Microsoft Teams Classic:<\/strong><\/h3>\n