How to Deploy a Customized Word Template to Users via Intune
Question details
An organization wants to distribute a custom corporate Word template containing approved fonts and settings to replace the default blank document for all users via Microsoft Intune.

- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- Corporate template standardization and endpoint deployment
- Observed behavior
- Seeking the correct Intune policy, script, or configuration method to successfully replace the default Normal.dotm or push a custom template across an organization's managed devices.
Ensure you have administrative access to your organization's Microsoft Intune admin center and that the target devices are successfully enrolled and synced with your tenant.
Deploy Templates via Intune PowerShell Script
Use a Microsoft Intune PowerShell script policy to copy your corporate template directly to the users' default template directory.
Because Microsoft Word does not have a native Intune configuration profile specifically for replacing the default blank document, deploying a PowerShell script is the standard approach. This script will copy your custom Normal.dotm or .dotx file to the target devices.
It is crucial that the script is configured to run in the user's context so the template is placed in the correct AppData folder for the logged-in user.
Create your corporate template in Microsoft Word with the approved fonts and layouts, and save it as Normal.dotm (to replace the blank document) or as a custom .dotx file.
Create a .ps1 script that securely downloads or copies your custom template file from a central network location or Azure Blob storage into the local %appdata%\Microsoft\Templates directory.
Log in to the Microsoft Intune Admin Center. Navigate to Devices > Scripts, click on 'Add', and select 'Windows 10 and later'. Upload your newly created .ps1 file.
Under the script settings, ensure you set 'Run this script using the logged on credentials' to 'Yes'. This step is mandatory to ensure the template reaches the specific user's AppData folder.
Assign the script to the appropriate User Groups (rather than Device Groups) and finalize the deployment policy.

Simplify Document Management with WPS Office
If managing complex deployment configurations in Microsoft Word is slowing your IT team down, consider WPS Office. It provides robust enterprise capabilities, highly familiar interfaces, and a lightweight footprint without the heavy administrative overhead.
- 1. Download the Installer: Get the lightweight WPS Office installation package directly from the official website.
- 2. Deploy Across Devices: Distribute the installer across your organization using your preferred endpoint management tool.
- 3. Enjoy Seamless Compatibility: Instantly open, edit, and standardize all legacy Microsoft Word formats and templates with perfect fidelity.

Frequently Asked Questions
Where are default Word templates stored locally on Windows?
By default, Microsoft Word stores custom user templates in 'C:\Users\[Username]\Documents\Custom Office Templates' and the default blank document template (Normal.dotm) in the '%appdata%\Microsoft\Templates' folder.
Why are my deployed Word templates not showing up for users?
This usually happens if the Intune deployment script runs in the 'System' context instead of the 'User' context. If it runs as System, the files are placed in the system profile rather than the actual employee's AppData folder.
Can I use Group Policy (GPO) instead of Intune to manage Word templates?
Yes, if your devices are joined to a local Active Directory, you can use Group Policy Administrative Templates for Microsoft Office to specify the 'Enterprise template path' or 'Workgroup templates path', which is often simpler than pushing files via Intune.




