logo
search
Microsoft 365 Installation Problems

How to Add the New Microsoft Teams to Office Deployment Tool

Huma Ashraf ChHuma Ashraf Ch Sep 30, 2026 868 views

Question details

The user wants to configure the Office Deployment Tool (ODT) to include and install the new Microsoft Teams client.

Adding the New Microsoft Teams Client to Office Deployment Tool
Product
Office Deployment Tool (ODT)
Device & OS
not provided
Scenario
Deploying Microsoft 365 applications to user devices using an ODT XML configuration file.
Observed behavior
The new Microsoft Teams client cannot currently be installed by adding an app ID to the Office Deployment Tool configuration file.
Before you start

Ensure you have administrative privileges on the target machines to manually deploy standalone installers or use alternative endpoint management software.

Solution 1Recommended

Deploy the New Teams Client Separately

Because ODT does not currently support an app ID for the new Teams client, you must install it manually, deploy it via an endpoint manager, or upgrade from the classic client.

Microsoft has not yet integrated the new Microsoft Teams client natively into the Office Deployment Tool. Until this functionality is added, IT administrators and users must rely on standalone deployment methods or the built-in upgrade toggle found in the classic Teams application.

1
Download the standalone installer

Visit the official Microsoft Teams download page and download the MSIX or executable installer specifically meant for the new Microsoft Teams client.

2
Deploy using an endpoint manager

If you are deploying across an organization, use tools like Microsoft Intune, Endpoint Configuration Manager, or a third-party deployment tool to push the downloaded MSIX package to user devices instead of using ODT.

3
Switch from the Classic Teams client

Alternatively, you can continue using ODT to deploy the classic Teams client. Once installed, instruct users to open the app and toggle the 'Try the new Teams' switch located in the upper-left corner of the interface.

4
Submit feedback to Microsoft

To request native ODT support, open the Microsoft Feedback Portal or use the feedback option within the Microsoft 365 Admin Center to request an app ID for the new Teams client.

ODT Updates: Microsoft frequently updates deployment tools. Keep an eye on the official Microsoft 365 deployment release notes to see if an App ID for the new Teams client is added in future updates.
Free Microsoft Office alternative

Looking for an Easier Office Suite to Deploy?

Avoid complex ODT configuration files and deployment errors. WPS Office provides a lightweight, highly compatible alternative to Microsoft Office that is much simpler to install, manage, and use across all your devices.

  1. 1. Download the installer: Visit the official WPS Office website and click the 'Free Download' button.
  2. 2. Run the installation: Open the downloaded setup file and follow the straightforward on-screen prompts to install the suite.
  3. 3. Start working immediately: Launch WPS Office and instantly open your existing Microsoft Office files without formatting loss.
Simple and fast installation process without needing complex deployment tools.Seamless compatibility with Microsoft Office formats including DOCX, XLSX, and PPTX.Familiar, tabbed user interface that requires zero retraining for your team.Lightweight software footprint that saves system resources and storage space.
QA img-9

Frequently Asked Questions

Will ODT support the new Teams client in the future?

Microsoft has not officially announced when or if the new Teams client will be natively added to ODT via an app ID. Submitting feedback through official Microsoft channels helps prioritize this feature.

Can I still deploy the classic Teams client using ODT?

Yes, the classic Teams client can still be included in your ODT XML configuration file using the standard Teams App ID. Users can then manually transition to the new Teams within the app.

How do I automate the installation of the new Teams without ODT?

You can automate the deployment using the Teams bootstrapper executable or the MSIX package deployed via Microsoft Intune, Configuration Manager, or basic command-line scripts.