The Office Deployment Tool (ODT) is a free utility from Microsoft that gives IT administrators control over the configuration of select Click to Run versions of Office and Microsoft 365 Apps. The tool lets you manage the applications installed, their languages, software architecture, update channel and how the applications are updated.
Microsoft
Instead of following a standard installation process, you can define how Office is installed by using an XML configuration file. This makes ODT useful for individual, business and enterprise deployments of Office.
What is the Office Deployment Tool?
The Office Deployment Tool is a Windows utility that enables administrators to manage the installation of Office applications through configuration files and command lines. The executable file, setup.exe, interprets the XML configuration files and performs the requested task.
The tool can perform the following tasks:
- Acquire the Microsoft 365 Apps installation files.
- Choose supported Office products and languages.
- Pick a 32-bit or 64-bit Office installation.
- Disable applications that are not required.
- Adjust supported update channels and update sources.
- Install Office with a visible or silent installation.
- Customize applications that are already installed.
- Package the Office installation files for network deployment.
This capability is documented on the Microsoft Office Deployment Tools (ODT) overview and configuration reference.
Microsoft Learn
Key takeaway: ODT is not a separate office suite. ODT is a tool to deploy and configure supported office products.
Office Deployment Tool
Download the tool from the Official Microsoft Download Center to avoid getting a modified and potentially risky version of the utility.
Office Deployment Tool
Official Microsoft Download Center
Version listed on October 19, 2026: 16.0.20430.20146
The published version can change. Check the official page for the latest release before installation.
Microsoft
Download from Microsoft
How to extract the Office Deployment Tool
After downloading the self extracting executable:
- Run the executable
- Read and accept the license agreement if any
- Choose a folder to extract the files
- Complete the extraction
- Open the folder to locate the utilities and sample configuration files.
The extracted setup.exe is the utility that is to be run from Command Prompt. The XML file is to be used to configure what the utility installs or downloads.
Microsoft Learn
Important: Downloading and extracting ODT does not install a licensed copy of Microsoft Office. You need to configure the deployment, run the appropriate command and have the entitlement for the office product you want to use.
System Requirements and Things to Check Prior to Installation
Microsoft has posted information on their site regarding the availability of the Windows 10 and Windows 11 operating systems and some of the Windows Server operating systems. Note: You should verify the latest official requirements for your deployment.
Microsoft
Before starting, verify the following:
- You have a supported version of Windows.
- You have administrator access on the target computer.
- You have a valid license/subscription for the selected Office product.
- You have determined the applications and languages you require.
- Your internet connection has access to the Microsoft downloads, unless the installation files are available locally.
- You have the correct Product ID and configuration in your XML file.
- You know the architecture of Office and its configuration if it is already installed.
- You have determined if there are any organizational policies that control Office updates or deployment.
How to Use the Office Deployment Tool
To learn how to use ODT, follow along during the deployment process.
Deployment Process
Step 1: Download and Extract ODT
Go to the official website to obtain the executable file and extract setup.exe to a folder of your choosing.
Step 2: Create an XML File
Decide on the configuration of the Office product, architecture, language, and other installation settings.
Step 3: Run the Command Prompt
To download the Office installation files use the command /download. To install Office use the command /configure.
Step 4: Verify the Deployment
Check the command prompt for errors, and/or check the logged files. If command prompt shows no errors, open the Office applications to make sure they are configured correctly.
Microsoft documents download, configure, and customize as distinct operating modes.
Microsoft Learn
Step 1: Create a working folder
For an example, create a folder as: C:\OfficeODT
Place the extracted setup.exe in the folder.
You will save your configuration file in the same folder. Keeping the executable and XML configuration file in the same folder makes running commands and troubleshooting easy.
Step 2: Create configuration.xml file
Use Notepad to create the following configuration file for Microsoft 365 Apps for enterprise.
<Configuration>
<Add OfficeClientEdition=”64″ Channel=”Current”>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
</Product>
</Add>
<Display Level=”Full” AcceptEULA=”TRUE” />
</Configuration>
Save the configuration file as configuration.xml in C:\OfficeODT
In Notepad, change the file type to all files, as Windows assumes configuration.xml.txt and saves with that extension.
What do the settings mean?
Setting Explanation
OfficeClientEdition=”64″ Requests the 64-bit edition
Channel=”Current” Sets the channel to Current Channel
O365ProPlusRetail Defines Microsoft 365 Apps for enterprise
ID=”en-us” Requests the language English (US)
Display Level=”Full” Shows the installation interface
AcceptEULA=”TRUE” Accepts the End User License Agreement (EULA)
These settings are interpreted using Microsoft’s documented ODT configuration model. The product must be aligned with your licensing and deployment requirements.
Microsoft Learn
For Microsoft 365 Apps for business: The product ID may need to be O365BusinessRetail rather than O365ProPlusRetail. Select the ID that corresponds to your actual product entitlement.
Microsoft Learn
Step 3: Download the Office installation files
Open Command Prompt as administrator.
cd /d C:\OfficeODT
setup.exe /download configuration.xml
The tool interprets the configuration and downloads the installation files.
If the process completes without a visible progress window, check the files and the logs in the Temp folder rather than assuming the command has failed. Microsoft documents the Temp folder as a location for ODT troubleshooting logs.
Microsoft Learn
When should you use download mode?
Use this mode to prepare a local installation source, distribute Office files across multiple computers, or reduce repeated downloads when deploying compatible files within an organization.
Step 4: Install Microsoft Office
After making the installation files available, run the following command on the configuration file:
setup.exe /configure configuration.xml
The Office Deployment Tool applies the configuration and starts the installation. You must have local administrator rights on the computer on which you are performing the installation.
Microsoft Learn
If you want ODT to download the files and install Office from Microsoft’s content delivery network, then you can also use a configuration that omits the local SourcePath and run the configure command. An internet connection will be required for files that are not available locally.
Step 5: Verify that Office was installed successfully
After installation, check that the expected applications and language are available in the Office applications.
Check that subscription sign-in or activation is working.
If deployment is not successful, analyze command output, and check relevant temporary logs.
Microsoft’s installation guidance notes that successful configuration output and logs found in %temp% as examples of verification and troubleshooting output.
Microsoft Learn
Office Deployment Tool XML Configuration Examples
The Office Deployment Tool enables administrators to configure and customize the configurations used to deploy Microsoft Office.
Microsoft recommends using the web-based Office Customization Tool to create and edit configurations where possible.
Microsoft Learn
1. Install Office Without Publisher
If your organization doesn’t require the use of Publisher, you can exclude it from the Office suite.
<Configuration>
<Add OfficeClientEdition=”64″ Channel=”Current”>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
<ExcludeApp ID=”Publisher” />
</Product>
</Add>
<Display Level=”Full” AcceptEULA=”TRUE” />
</Configuration>
The ExcludeApp element is used to omit supported applications from the deployment. Other IDs supported for the ExcludeApp element include: Word, Excel, PowerPoint, Outlook, OneNote, Access, Teams, and OneDrive.
Microsoft Learn
2. Deploy Office in Different Language
In order to deploy multiple languages of Office, add the appropriate language IDs in the product configuration.
This example adds English (United States) and French (France). Verify that the languages are supported based on your product and deployment scenario. The first language entry also dictates the default language for the Office application user interface.
For a managed deployment where you don’t want the installation user interface to appear, use a configuration like the following:
<Configuration>
<Add OfficeClientEdition=”64″ Channel=”MonthlyEnterprise”>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
</Product>
</Add>
<Display Level=”None” AcceptEULA=”TRUE” />
</Configuration>
Use a Display Level=”None” configuration only after proper authorization and your organization has addressed user notification, licensing, and other related legal requirements.
For a managed deployment using a local installation source, where you don’t want the user interface to appear, use a configuration like the following:
<Configuration>
<Add SourcePath=”officefiles”
OfficeClientEdition=”64″
Channel=”Current”>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
</Product>
</Add>
<Display Level=”None” AcceptEULA=”TRUE” />
</Configuration>
Use Display Level=”None” only when your organization has fulfilled user notification, licensing, and other legal requirements.
MICROSOFT LEARN PLUS 1
For more information about the Office Deployment Tool, see the Office Deployment Tool Commands Explained article.
The following commands cover the most common deployment operations.
Command Purpose
setup.exe /download configuration.xml
Downloads the configured installation files
setup.exe /configure configuration.xml
Configures the installation, update or modify Office
setup.exe /customize preferences.xml
Configures supported application preferences and leaves other deployment settings unchanged.
setup.exe /help
Displays command-line help
Microsoft documents these operating modes in the official ODT overview.
Microsoft Learn
Practical tip: Run commands from the directory containing setup.exe and your XML file, or specify the correct full paths. This avoids many common file-location mistakes.
Office Deployment Tool vs. Office Customization Tool
These two Microsoft tools are related, but serve different purposes.
Feature Office Deployment Tool Office Customization Tool
Main Purpose
Execute Office deployment operations
Create and edit deployment configurations
Interface
Command Line
Web-based Interface
XML configuration
Reads and applies XML configuration
Helps generate configuration XML
Installation Workflow
Downloads, installs or modifies supported deployments
Helps to prepare the settings for deployment
Best suited for
Technicians, IT Admins, Scripted Deployments
Users who prefer a configuration interface
Microsoft recommends the Office Customization Tool for configuration file generation, while ODT performs deployment operations.
Microsoft Learn
You can access the Office Customization Tool to prepare your configuration.
How to Deploy Office on Multiple Computers
For IT and Business, the Office Deployment Tool can help set a defined configuration on multiple Windows devices.
A regular workflow is
- Approve a configuration for the required Office product.
- Download the required files to an approved location on the network.
- Test configuration on a sample computer.
- Confirm application selection, licensing, activation and update behaviors.
- Deploy the configuration to other authorized devices.
- Monitor installation results and update process.
For example, a company with 25 computers may create a single installation source that contains the required languages and applications for Microsoft Office, and use a deployment process to install the product on each computer.
There are a number of advantages to using ODT. Perhaps the biggest advantage is the ability to deploy settings without an administrator having to visit each computer and configure settings. Actual automation across multiple devices requires the use of an adequate execution and device-management solution. ODT, on its own, is not a complete solution for fleet-management.
For companies that manage centralized software updates, Microsoft has additional resources on ODT, which describes the use of local update sources.
Problem What to check
setup.exe is not recognized Is Command Prompt in the same folder as setup.exe? Is a full path defined for setup.exe?
Configuration file cannot be found Check the directory path, XML filename and extension
Office download fails Check the availability of disk space and proxy and firewall settings
Installation fails because of architecture Verify which 32-bit or 64-bit Office edition is being installed and ensure it is not in conflict with a previously installed edition
Wrong applications are installed Check the IDs of the products being installed, as well as every ExcludeApp entry
Installation runs without a visible window Check Display Level=”None” is not configured
Office does not activate Check product being installed, organizational/account activation settings and license entitlement
Office updates do not follow the expected channel Check the ODT configuration, and Group Policy or cloud settings
Architecture incompatibility and competing update policies are documented considerations in some of Microsoft’s ODT configuration and update-channel guidance.
Microsoft Learn
Where can you find Office Deployment Tool logs?
You can begin with checking the temporary files.
Look for logs created around the time of the failed deployment.
Be sure to record the exact command, configuration file and any errors displayed prior to making changes.
Microsoft specifically recommends reviewing temporary log files when diagnosing Office Deployment Tool download and installation issues.
Microsoft Learn
Avoid making numerous configuration changes simultaneously. Rather, make one change and check the result before running the deployment again.
Is the Office Deployment Tool Free?
The Office Deployment Tool is free. However, just because the tool is free, it doesn’t mean the Office products installed with the tool are free.
The licensing or subscription depends on the product deployed. The ODT is a tool to configure and deploy certain Office products; it can’t bypass product activation or grant a license.
Microsoft
Frequently Asked Questions
1. What is the Office Deployment Tool?
The Office Deployment Tool is used to download and install supported versions of Office products via Click-to-Run. It enables Administrators to control application and configuration settings using XML files and/or command line switches.
2. How do I install Office Deployment Tool?
You can download Office Deployment Tool from Microsoft Download Center. Be cautious not to use other unverified sources for download.
3. Can I use Command Prompt to install Office products?
Yes, you can. But keep in mind that your XML configuration defines the end result.
4. What’s the difference between /download and /configure commands?
The /download command is used to save the installation files to a local directory. The /configure command is used to apply a configuration to perform an install or other supported changes to a deployment.
5. Can I use the Office Deployment Tool without an internet connection?
You can install from a local source when the installation files are compatible with your configuration. Preparing or downloading those files requires network connectivity, and licensing or activation may also require internet access.
6. Can I select which Office applications to install?
Yes. The ExcludeApp configuration element can be used to omit applications from an installation. Availability and behavior of application IDs and products are listed in the official configuration reference.
7. Does the Office Deployment Tool work on Windows 11?
Yes. Windows 11 is listed among the supported operating systems on the Microsoft ODT download page. Always check the requirements for the exact product you want to deploy.
Microsoft
8. What should I do if Office Deployment Tool is not working?
Check command syntax, XML file name, product ID, permissions, installation source, and network connectivity. If the problem persists, check the temporary logs, and compare your configurations with Microsoft’s official documentation.
1. Can I use ODT to switch Office update channels?
Yes, ODT can alter update-channel settings; however, existing Group Policy or Cloud-based update management settings may take precedence. See Microsoft’s guidance on update channels before making any changes to managed devices.
Microsoft Learn
2. Is ODT geared more towards home users?
It could be useful toward home users for more advanced, custom installs. However, for basic installs and re-installs of Office at home, users can follow Microsoft’s standard install processes.
Microsoft Learn
Conclusion
The Office Deployment Tool is an enhanced solution over a standard install process for configuring and deploying various versions of Microsoft Office. Its flexibility and ease of use lend it to IT professionals for business deployments.
Start by downloading ODT from Microsoft’s website, adjust configuration files to meet your product and licensing requirements, run an install command, and confirm the success of the install. When doing large deployments, perform a small scale test of configuration and deployment to identify issues before rolling it out across your organization.
The most critical aspect of a successful Office deployment is a correct config, verified install source, and correct product.
