'%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)
Fix Office Deployment XML Ignoring Local Source Path
Question details
The user is attempting to deploy Microsoft 365 Apps from a local network share, but the deployment ignores the SourcePath and AllowCdnFallback settings.
- Product
- Microsoft 365 Apps
- Device & OS
- not provided
- Scenario
- Deploying Microsoft 365 Apps in a local or enterprise environment using an XML configuration file and the Office Deployment Tool.
- Observed behavior
- The installation continues downloading from the Microsoft CDN despite the XML configuration specifying a local or network SourcePath and having AllowCdnFallback set to false.
Ensure you have administrator privileges on the deployment machine and verify that the target network path is accessible and contains the completely downloaded Office source files.
Recreate the XML Configuration File using the Office Customization Tool
Generating a fresh XML file using the official web tool ensures syntax accuracy and correct parameter settings for local deployment.
Manual edits to the XML configuration can easily introduce syntax errors or conflicting attributes that force the Office Deployment Tool to default back to the CDN.
Navigate to the official Office Customization Tool in your web browser at config.office.com.
Select your product, channel, and architecture. Under the 'Installation' section, ensure you set the correct local network path in the 'SourcePath' field.
Toggle the 'AllowCdnFallback' setting to false to strictly prevent the installer from using the internet for source files.
Click 'Export' to download the new XML file. Replace your existing configuration file with this new one.
Execute the deployment command (e.g., setup.exe /configure new_config.xml) using the corrected XML file.
Test Deployment with a New Windows User Profile
Creating a new user profile helps determine if the issue is tied to account-specific network permissions or corrupted local account settings.
Escalate to Your IT Administrator or Microsoft Support
If configuration changes do not resolve the issue, enterprise support may be necessary to identify deeper network or environment problems.
Simplify Your Workflow with WPS Office
Avoid complex deployment configurations and XML errors. WPS Office is a lightweight, highly compatible alternative to Microsoft 365 that installs quickly without complicated network path setups.
Frequently Asked Questions
Why does the Office Deployment Tool use the CDN when AllowCdnFallback is false?
This typically happens if the Office source files are missing, corrupted, or incompatible (wrong architecture/channel) in the specified local SourcePath, or if there is a syntax error in the XML configuration file.
How do I download the Office installation files to my local path?
You must run the Office Deployment Tool with the /download switch (e.g., setup.exe /download configuration.xml) to pull the files from the CDN to your local network share before attempting to deploy them.
Where can I find the Office Deployment Tool error logs?
By default, the Office Deployment Tool writes its log files to the %temp% directory on the machine where the deployment was executed. Reviewing these logs can reveal specific error codes regarding why the SourcePath was rejected.
