How to Deploy a Custom.dic File to Microsoft Office Users via Intune
Question details
Deploying a custom dictionary file to Microsoft 365 users without overwriting existing configurations.

- Product
- Microsoft 365 Office, Microsoft Intune
- Device & OS
- Windows 10
- Scenario
- An IT administrator needs to distribute a standardized Custom.dic file to existing Office users via Microsoft Intune.
- Observed behavior
- Needs to ensure the deployment adds the new dictionary words without overwriting or deleting users' current spell-check settings.
Ensure you have administrator access to the Microsoft Intune Admin Center and verify the exact file path where Office stores custom dictionaries on the target Windows 10 devices (typically %appdata%\Microsoft\UProof).
Use a PowerShell Script in Intune to Append Dictionary Words
Instead of overwriting the Custom.dic file, use a PowerShell script deployed as a Win32 app to safely append new company words to the existing user dictionary.
Replacing the Custom.dic file completely will wipe out any custom words users have already saved. The safest deployment method is to push a script that reads a central list of words and appends only the new words to each user's local dictionary file.
Write a PowerShell script that targets the '$env:APPDATA\Microsoft\UProof\Custom.dic' file path. The script should compare a provided text file of company words against the existing dictionary and append any missing words.
Use the Microsoft Win32 Content Prep Tool to package your PowerShell script and the source word list into an '.intunewin' format.
Log in to the Microsoft Intune admin center, navigate to Apps > Windows > Add, and select 'Windows app (Win32)'. Upload your compiled '.intunewin' package.
In the Program settings, set the Install command to run your PowerShell script. Crucially, set the Install behavior to 'User' rather than 'System'. This ensures the script correctly identifies and modifies the specific %appdata% folder of the logged-in user.

Deploy a Secondary Dictionary via Office ADMX Policies
Deploy a completely separate dictionary file and use Intune Configuration Profiles to tell Office to load it alongside the user's default Custom.dic.
Experience Hassle-Free Document Management with WPS Office
Looking for an Office suite that is easier to deploy and manage? WPS Office offers a lightweight, highly compatible alternative to Microsoft Office, supporting seamless mass deployments for enterprises without the complex configuration overhead.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package.
- 2. Install the Software: Run the setup file and follow the on-screen prompts to complete the installation.
- 3. Open Your Documents: Instantly open, edit, and save your existing Microsoft Office files without losing any formatting.

Frequently Asked Questions
Where is the Custom.dic file located in Windows 10?
By default, Microsoft Office stores the Custom.dic file in the user profile under the path: C:\Users\<Username>\AppData\Roaming\Microsoft\UProof.
Can I deploy a secondary dictionary instead of modifying the default Custom.dic?
Yes. You can deploy a separate dictionary file (e.g., Company.dic) to a public device folder via Intune, and then use Administrative Templates (ADMX) to add it to the Office roaming dictionaries registry keys.
Why does deploying files via Intune System context fail to update user AppData?
Intune policies running in the System context operate under the local system account, meaning they do not have direct access to individual user AppData folders. Deployments targeting user-specific paths must be configured with 'User' install behavior.
Does WPS Office support custom dictionaries?
Yes, WPS Office includes a robust built-in spell checker and allows users to easily add custom words to their own local dictionaries, ensuring industry-specific terms are not mistakenly marked as misspellings.




