Fix Microsoft 365 Updating from CDN Instead of Local Network Share
Question details
The user needs to configure Microsoft 365 to update from a local or network share using the Office Deployment Tool, but it currently falls back to the Microsoft CDN.

- Product
- Microsoft 365
- Device & OS
- Windows
- Scenario
- Deploying or updating Microsoft 365 in a local environment using ODT XML configurations, where bandwidth needs to be conserved by hosting updates locally.
- Observed behavior
- The system ignores the specified local or network UpdatePath, changes the path back to an Office CDN URL, and expected update files are missing from the designated local folder.
Ensure you have administrative privileges on the target Windows machine and read/write access to the local or network share where the Office installation files are hosted.
Verify Update Files and ODT XML Configuration
Ensure the local folder actually contains the required update files and that the XML configuration correctly points to the path.
If the specified UpdatePath folder is empty or lacks the correct version of the Office installation files, the Office Click-to-Run service will automatically fall back to the Microsoft CDN or display an update error.
Navigate to the folder specified in your UpdatePath and verify that the 'Office' folder containing the correct DAT and CAB files is present.
If the folder is empty, use the Office Deployment Tool command prompt to download the files by running 'setup.exe /download configuration.xml'.
Open your configuration.xml file in a text editor and ensure the Updates element is correctly formatted, for example: <Updates Enabled="TRUE" UpdatePath="\\Server\Share\Updates" />.

Check the Click-to-Run Registry Keys
Manually inspect the Windows Registry to confirm that the UpdateUrl value was correctly applied during deployment.
Simplify Your Office Deployment with WPS Office
Dealing with complex Office Deployment Tool XML files, registry keys, and network share updates can be frustrating and time-consuming. WPS Office provides a lightweight, free alternative with easy offline deployment, native compatibility with Microsoft Office formats, and a familiar user interface that requires zero learning curve.
- 1. Download the Installer: Visit the official WPS website and download the offline installer for your operating system.
- 2. Run the Setup: Double-click the downloaded executable file to begin the straightforward installation process.
- 3. Start Working: Open WPS Office to immediately start creating or editing your documents with full Microsoft format compatibility.

Frequently Asked Questions
Why does Microsoft 365 ignore my local UpdatePath?
Office will fall back to the Microsoft CDN if the specified local or network folder is empty, inaccessible due to network permissions, or lacks the exact matching version of the Office update files required by the client.
How do I download the Office update files to my local network share?
You must use the Office Deployment Tool with the /download switch along with your configuration XML file. This commands the tool to download the necessary installation files from the Microsoft CDN directly to your specified local folder.
How do I check which update source my current Office installation is using?
You can check the active update path by opening the Windows Registry Editor and navigating to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, then checking the data inside the 'UpdateUrl' string value.
Can I prevent Office from ever falling back to the CDN?
While Office is designed to fall back to the CDN to ensure security updates are applied if a local source fails, correctly maintaining the files in your UpdatePath and ensuring network accessibility prevents the fallback from triggering.




