For managed deployment of the new Microsoft Teams client, use Microsoft’s Teams bootstrapper rather than the old per-user Classic installer. A typical online provisioning command is teamsbootstrapper.exe -p; to stage a specific MSIX package, use the offline option, for example teamsbootstrapper.exe -p -o C:\Path\MSTeams-x64.msix.

Plan the deployment context carefully: the online bootstrapper needs network access from the account running the install, and the installed client may be newer than the version shown by packaging catalogs because the bootstrapper retrieves current Teams content. If the rollout must remove Teams Classic, include the bootstrapper uninstall/removal option supported by Microsoft and validate it separately from the new-client install detection.

Official source: Microsoft bulk install guidance for the new Teams client.

For managed deployment of the new Microsoft Teams client, use Microsoft’s Teams bootstrapper rather than the old per-user Classic installer. A typical online provisioning command is teamsbootstrapper.exe -p; to stage a specific MSIX package, use the offline option, for example teamsbootstrapper.exe -p -o C:PathMSTeams-x64.msix. If the rollout must remove Teams Classic, include the documented bootstrapper option -u and validate classic-client removal separately from new-client detection.

Official source: Teams official documentation/product page.

For new Microsoft Teams bulk installs, plan for the Teams bootstrapper to need internet access from the installing account and to install the current Teams build available at run time. If you also need to remove classic Teams during the deployment, include the bootstrapper uninstall/remove option in the managed command rather than assuming the new install removes classic Teams automatically.

Source: Teams official documentation/download page.

For managed deployment of the new Microsoft Teams client, use Microsoft’s Teams bootstrapper rather than the old per-user Classic installer. A typical online provisioning command is teamsbootstrapper.exe -p; to stage a specific MSIX package, use the offline option, for example teamsbootstrapper.exe -p -o C:\Path\MSTeams-x64.msix.

Plan the deployment context carefully: the online bootstrapper needs network access from the account running the install, and the installed client may be newer than the version shown by packaging catalogs because the bootstrapper retrieves current Teams content. If the rollout must remove Teams Classic, include the bootstrapper uninstall/removal option supported by Microsoft and validate it separately from the new-client install detection.

Official source: Microsoft bulk install guidance for the new Teams client.

For managed deployment of the new Microsoft Teams client, use Microsoft’s Teams bootstrapper rather than the old per-user Classic installer. A typical online provisioning command is teamsbootstrapper.exe -p; to stage a specific MSIX package, use the offline option, for example teamsbootstrapper.exe -p -o C:PathMSTeams-x64.msix. If the rollout must remove Teams Classic, include the documented bootstrapper option -u and validate classic-client removal separately from new-client detection.

Official source: Teams official documentation/product page.

For new Microsoft Teams bulk installs, plan for the Teams bootstrapper to need internet access from the installing account and to install the current Teams build available at run time. If you also need to remove classic Teams during the deployment, include the bootstrapper uninstall/remove option in the managed command rather than assuming the new install removes classic Teams automatically.

Source: Teams official documentation/download page.