Why the Office Deployment Tool Contacts the CDN During Installation
Question details
Determine why the Office Deployment Tool contacts the Microsoft CDN when installation files are available on an internal network share.

- Product
- Office Deployment Tool for Microsoft 365 Apps
- Device & OS
- not provided
- Scenario
- An administrator runs an Office installation using an XML configuration that points to an internal network share.
- Observed behavior
- The Office Deployment Tool requests installation files from the internet instead of using the expected files on the share, and the firewall blocks the request.
Locate the XML file used for installation and the Office files on the network share. Check that the installing client can reach the share and that you have permission to download files to it if needed.
Match the downloaded Office package to the installation XML
Use this when the configuration was changed after the Office installation files were downloaded.
Open install.xml in a text editor and check the product ID, version, update channel, language, architecture, and SourcePath. Confirm that these settings match the intended package and network share.
Using the latest Office Deployment Tool, open a command prompt and run setup.exe /download install.xml. Make sure SourcePath points to the intended share and that the download account can write to it.
Without changing the package settings, run setup.exe /configure install.xml on the client. If the configuration must change, download the matching files again before installing.

Check network share access and language fallback
Use this if the package appears to match the XML but the client still contacts the CDN.
Use WPS Office as an Alternative to Microsoft 365 Apps
WPS Office is a free, lightweight alternative with a familiar interface for working with existing Office documents. Its format compatibility makes it easier to move everyday document work without changing the Office Deployment Tool configuration.

Frequently Asked Questions
Why did the deployment start working after I downloaded the files again?
The installation XML may have requested a different product, version, language, channel, or architecture than the files on the share. Running setup.exe /download install.xml again supplies files for the configuration you plan to install.
Does AllowCdnFallback control every CDN request?
No. AllowCdnFallback in the Add element concerns missing language packs. Other settings, including update settings, can also affect whether Office contacts the CDN.
How can I check whether the client can use the network share?
On the installing client, open the UNC path listed in the XML's SourcePath and confirm that the installing account can read the Office files. Also check share and folder permissions if access fails.
Can I edit the XML after downloading the Office files?
You can edit it, but changes to package settings such as product, language, version, channel, or architecture may require another download. Run setup.exe /download with the updated XML before running setup.exe /configure.




