The Office Deployment Tool deep dive — Solving Microsoft 365

The Office Deployment Tool (ODT) is Microsoft's command-line tool for granular control over Microsoft 365 Apps installation — what apps, what languages, what architecture, what update channel, with custom shortcuts and behaviour. For most Intune-managed estates, ODT runs under the covers; for traditional deployments, custom installers, or specific requirements, you drive ODT directly.

The XML configuration file

ODT is driven by an XML configuration file:

<Configuration>
  <Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
      <Language ID="en-gb" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="OneDrive" />
      <ExcludeApp ID="Lync" />
    </Product>
    <Product ID="VisioProRetail">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Display Level="None" AcceptEULA="TRUE" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <Property Name="SharedComputerLicensing" Value="0" />
  <RemoveMSI />
</Configuration>

This describes a specific install: 64-bit Monthly Enterprise Channel, Microsoft 365 Apps for Enterprise plus Visio Pro, English (US and UK), excluding the deprecated Groove, OneDrive, and Lync (Skype for Business) sub-products.

The Office Customization Tool

For the XML, don't write it by hand — use the Office Customization Tool at config.office.com. The GUI lets you pick:

Which Microsoft 365 product and Visio / Project add-ons.
Architecture (32 or 64 bit).
Update channel.
Apps to include / exclude.
Languages and proofing tools.
Display behaviour (silent or interactive install).
Activation behaviour.
Shared Computer Activation (for VDI).
Custom installation properties.

Then export the XML. Use that with ODT.

Running ODT

ODT itself is a small executable (setup.exe) you download from the Microsoft Download Center. Used with the XML:

:: Download the installation files
setup.exe /download configuration.xml

:: Install Office using the downloaded files
setup.exe /configure configuration.xml

:: Uninstall existing Office
setup.exe /configure uninstall.xml

Common scenarios

Install Microsoft 365 Apps with Visio

XML specifying both products. Useful for users who need Visio on top of standard Office.

Install for VDI / Cloud PC

Set SharedComputerLicensing = 1 so Office activates per-session rather than per-device.

Channel-pinning specific users

Pin a small population to the Current Channel (Preview) for early testing; everyone else on Monthly Enterprise Channel. Achieved via separate ODT configurations targeting different user groups.

Architecture migration (32 to 64 bit)

Migrate from 32-bit Office to 64-bit on a managed fleet. Requires uninstall, then reinstall with the new architecture. ODT scripts handle both steps cleanly.

Removing pre-existing classic Office

<RemoveMSI /> removes any legacy MSI-based Office installation before installing Microsoft 365 Apps. Essential for migrating users on older Office versions.

ODT vs Intune deployment

For Intune-managed estates, the Microsoft 365 Apps for Windows app type in Intune wraps ODT internally — you configure via Intune's UI (same options as the Office Customization Tool), Intune generates the XML and runs ODT under the hood.

When to drive ODT directly:

Configuration Manager (SCCM) deployments — ODT used in task sequences.
Custom installer packages — chocolatey-style packages or PSADT.
Specific customisations Intune's UI doesn't expose.
Offline / air-gapped scenarios — download via ODT, deploy from local share.

Operational considerations

Test in a controlled environment before mass deployment.
Document the XML configuration — undocumented Office configurations are confusing for future admins.
Source files — for offline scenarios, manage where the source .cab and .dat files live.
Update Office Customization Tool exports as Microsoft adds new options.
Update Channel migration — moving users between channels has specific procedures.

For Microsoft 365 customers with anything beyond standard Intune-driven deployment, ODT is essential tooling. The XML format, while verbose, gives complete control over Microsoft 365 Apps installation behaviour.