
Office Deployment Tool for Controlled Deployments
Office Deployment Tool gives administrators a scriptable way to download and install Click-to-Run editions of Microsoft 365 Apps and supported Office products on Windows devices. Instead of accepting a fixed setup path, administrators define products, languages, architecture, update channels, display behavior, and related settings in an XML configuration file, then run setup.exe with the appropriate command. The Office Deployment Tool is designed for managed deployments where consistency matters across multiple PCs, test groups, shared computers, or enterprise environments. It can prepare installation content in advance, deploy directly from Microsoft’s content delivery network or a local source, and support repeatable configurations that reduce manual setup differences between machines.
Deployment revolves around a small executable and configuration XML, so the same instructions can be reused from command scripts, management systems, network shares, or local folders. Office Deployment Tool supports separate download and configure modes, while customize mode can apply application preferences without changing other deployment settings. Administrators can also control update behavior, remove selected products, exclude individual applications, migrate Office architecture in supported scenarios, and suppress the user interface for unattended installations. For teams documenting or coordinating local utilities around managed PCs, the Desktop companion application can serve as a related reference in a broader desktop software workflow. Microsoft recommends using the latest ODT version before downloading or installing Office.
Benefits of Using Office Deployment Tool
The main benefit of Office Deployment Tool is predictable control over how Office reaches each managed device, which reduces configuration drift and repeated hands-on setup. Administrators can standardize product selections, languages, bitness, update channels, source locations, and display settings in reusable XML files, then apply the same deployment logic across a fleet. Download mode can stage installation files before rollout, helping teams plan bandwidth use and support sites with limited connectivity, while configure mode can install, update, or remove supported products from the same command-line workflow. Selective application exclusions prevent unwanted components from being installed, and silent display settings support unattended provisioning. Update paths and target versions can also be governed centrally when a deployment policy requires tighter change control. Because the configuration is text-based, it can be reviewed, versioned, copied between environments, and incorporated into existing administrative scripts, making Office rollouts easier to reproduce, audit, troubleshoot, and maintain.
Office Deployment Tool Software Information
- Developer: Microsoft Corporation
- Current Version: 16.0.20326.20112
- File Size: 3.4 MB
- Language: English
- Platform: Windows
System Requirements
- Processor: 2-core CPU
- RAM: 2 GB RAM
- Storage: 1 GB
- Graphics / GPU: Not required
Visit the official Office Deployment Tool website
Office Deployment Tool Features
XML Deployment Control
Office Deployment Tool reads configuration XML that specifies products, languages, architecture, update channels, source paths, display settings, and other deployment options. This makes installations reproducible across devices because administrators can keep one reviewed configuration for a rollout instead of making the same choices manually on every computer.
Download and Configure Modes
The tool separates content acquisition from installation through download and configure modes. Download mode retrieves the required Office files to a chosen location, while configure mode uses XML instructions to install, update, or remove products. Separating these steps helps administrators stage content before deployment and reuse the same source across multiple machines.
Selective App Installation
Administrators can define specific Office products and omit individual applications that are not needed in a deployment. ExcludeApp settings can prevent components such as Access, OneNote, Outlook, PowerPoint, Teams, or Word from being installed with a selected product, helping organizations match software sets to roles, licensing plans, and operational requirements.
Update Channel Management
Office Deployment Tool can set the Office update channel and configure how installed apps receive updates after deployment. Administrators can define update paths and, when needed, target a specific supported build. This control is useful for organizations that test changes before broader rollout or coordinate updates with internal change-management schedules.
Unattended Installation Options
Display settings let administrators choose a full installation experience or run setup without a visible user interface. The configuration can also accept Microsoft Software License Terms when appropriate, allowing managed deployments to proceed with less user interaction. These options support scripted provisioning, device imaging workflows, and other situations where consistent unattended installation behavior is required.
Architecture Migration Support
Supported configuration settings can move an existing Microsoft 365 Apps installation between 32-bit and 64-bit architecture when the required conditions are met. This helps administrators standardize device fleets or modernize older deployments without building an entirely separate installation process, while still respecting compatibility rules for installed Office architecture.
Application Preference Deployment
Office Deployment Tool includes a customize mode that can apply supported application preferences to computers where Microsoft 365 Apps is already installed. Because customize mode changes preferences without altering other deployment settings, administrators can adjust selected Office behavior after installation while avoiding a complete reinstall or a broader configuration change.
Tenant Inventory Association
Version 16.0.19929.20062 and later supports the TenantAssociationKey property, which can associate connected devices with an organization in Inventory within the Microsoft 365 Apps admin center. Including the tenant-specific key in XML gives administrators another way to connect deployment work with centralized device inventory and management processes.
Office Deployment Tool Old Versions
Version 16.0.20228.20124 Updated: 2026-08-11 Download
Version 16.0.20131.20090 Updated: 2026-07-14 Download
Version 16.0.20026.20112 Updated: 2026-06-10 Download
Version 16.0.19929.20090 Updated: 2026-05-13 Download
Version 16.0.19929.20062 Updated: 2026-04-20 Download
Office Deployment Tool FAQs
What is Office Deployment Tool used for?
It is used to download and deploy Click-to-Run versions of Office, including Microsoft 365 Apps, on Windows client computers. Administrators control installation details through XML, including products, languages, architecture, update behavior, source paths, and whether users see the installation interface.
Does it install Microsoft 365 Apps offline?
It can stage Office installation files in advance with download mode and then install from a configured local or network source. The exact workflow depends on the XML settings and the Office products being deployed, so administrators should prepare the required content before running configure mode on target devices.
Can Office Deployment Tool install selected Office apps?
Yes. Administrators can choose supported products and use ExcludeApp settings to leave out individual applications they do not want installed. This is useful when different device groups need different Office components, but the configuration should be tested because exclusion behavior can depend on what is already installed.
Can it run without user interaction?
Yes. The Display element can set the installation interface to None, allowing deployment without progress screens or completion dialogs. Administrators can also configure license-term acceptance where appropriate. Silent deployment is useful for scripted or centrally managed provisioning, but configuration and permissions still need to be correct.
Which Windows versions are supported?
Microsoft currently lists Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025 for the current download. Support for the Office products being deployed can have additional requirements, so administrators should also check the relevant Microsoft 365 Apps documentation.
