'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Can the Office Deployment Tool Install a Word XML Add-In?
Question details
The user wants to know if they can use the Office Deployment Tool (ODT) to integrate and install a Word add-in provided as an XML manifest across multiple tenant computers.
- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- Deploying a custom Word XML add-in to all tenant computers within an organization using local administrator rights.
- Observed behavior
- The Office Deployment Tool successfully deploys Office but does not automatically process or install the XML add-in manifest, prompting the user to seek a compatible deployment method.
Ensure you have local administrator rights on the target tenant computers and access to either the Microsoft 365 admin center or your preferred endpoint management tool.
Deploy the XML Add-In via Microsoft 365 Admin Center
Instead of using the Office Deployment Tool, the most efficient way to deploy an XML add-in across tenant computers is through Centralized Deployment in the Admin Center.
The Office Deployment Tool (ODT) is designed to handle standard Office installation packages (like MSI or Click-to-Run files), not XML manifests. Centralized Deployment is Microsoft's recommended alternative for distributing custom XML add-ins to users within a tenant.
Sign in to the Microsoft 365 admin center using your global or Exchange administrator credentials.
Go to 'Settings' in the left-hand navigation pane, select 'Integrated apps', and then click on 'Add-ins'.
Click 'Deploy Add-in', choose to upload a custom app, select 'I have the manifest file (.xml) on this device', and browse for your XML file to upload it.
Select the specific users, groups, or the entire organization that should receive the add-in, and follow the remaining prompts to complete the deployment wizard.
Distribute the XML File Using a Management Script
If Centralized Deployment is not an option, you can deploy the XML manifest separately using a script or an endpoint management tool like Microsoft Intune.
Switch to WPS Office for Streamlined Document Management
If complex deployment tools, MSI installers, and manual XML add-in management in Microsoft Office are taking up too much IT time, consider WPS Office. It provides a lightweight, highly compatible alternative with built-in productivity features, reducing the need for deploying complex third-party add-ins.
- 1. Download the Installer: Visit the official WPS Office website and download the free, lightweight installer package.
- 2. Deploy Across Computers: Run the setup file to easily install the suite across your devices without needing complex deployment tools.
- 3. Open Your Documents: Launch WPS Office to instantly open, edit, and save your existing Word documents seamlessly.
Frequently Asked Questions
Why doesn't the Office Deployment Tool support XML add-ins directly?
The Office Deployment Tool (ODT) is explicitly engineered for downloading and configuring Microsoft 365 core application files, such as Click-to-Run or MSI packages. An XML manifest is not an installation package; it is a configuration file that directs Word to web-hosted add-in resources, thus requiring a different distribution mechanism like Centralized Deployment.
Can I test an XML add-in locally before deploying it to all tenant computers?
Yes. You can sideload the XML add-in for testing. Place the XML file in a local or shared folder, go to Word > File > Options > Trust Center > Trust Center Settings > Trusted Add-in Catalogs, add the folder path, and check 'Show in Menu'. You can then insert the add-in from the Shared Folder tab.
Do end-users need local administrator rights to receive centrally deployed XML add-ins?
No, if you deploy the add-in via the Microsoft 365 admin center (Centralized Deployment), end-users do not need local admin rights. The add-in is linked to their Microsoft 365 account and appears automatically. However, manually modifying local registries to trust a catalog folder does require admin rights during the deployment phase.
