Copilot in Word Cannot Use Company Template: Fix

When you try to use Copilot in Word to draft a document based on your company template, Copilot may ignore the template entirely or generate content that does not follow the template formatting. This problem typically occurs because Copilot does not have access to the template file path or because the template is stored in a location Copilot cannot read. This article explains why Copilot cannot apply a company template and provides the steps to fix the issue so Copilot respects your template structure.

Why Copilot in Word Cannot Use a Company Template

Copilot in Word generates content by reading the current document context and any connected data sources. When you ask Copilot to create a document using a company template, it attempts to locate the template file. If the template is stored on a local network drive, in a personal folder, or in a location that Microsoft 365 cannot index, Copilot cannot find it.

The root cause is that Copilot relies on Microsoft Graph to access files. Microsoft Graph indexes content stored in SharePoint Online, OneDrive for Business, and Teams. Local file servers, mapped drives, and on-premises template folders are not indexed. Even if the template is in SharePoint, the folder must have the correct permission settings for the Copilot service to read the file.

Another common cause is that the template is not registered as an organizational template. Word can use a template stored in the default user templates folder on a local machine, but Copilot cannot access that folder. The template must be uploaded to a SharePoint document library and then set as the default organizational template through the SharePoint template gallery or the Microsoft 365 admin center.

Steps to Enable Copilot to Use a Company Template

Follow these steps to move your company template to a location Copilot can access and configure it properly.

Step 1: Upload the Template to SharePoint

1. Open the SharePoint document library
   Go to the SharePoint site where you want to store the template. Open the document library that contains templates for your team or organization. If you do not have a dedicated template library, create a new document library named “Templates” or “Office Templates.”
2. Upload the template file
   Click the Upload button and select your company template file. The file must be a .dotx or .dotm format. After upload, the file appears in the library with a link that Copilot can access.
3. Copy the file URL
   Right-click the uploaded template and choose Details. Copy the file URL from the details pane. You will need this URL in the next step.

Step 2: Set the Template as the Organizational Default

1. Open the SharePoint Template Gallery
   Navigate to your SharePoint site. In the left navigation, select Site contents > Site templates. If you do not see Site templates, click Add an app and choose Template Gallery.
2. Add the template to the gallery
   Click Add template. Paste the URL you copied from the document library. Give the template a name that matches your company standard. Click Save.
3. Set the template as default
   In the template gallery, select the template you just added. Click the three dots (More options) and choose Set as default. This action tells Word and Copilot to use this template when creating new documents for the site.

Step 3: Verify Copilot Permissions on the Template Folder

1. Open the SharePoint document library permissions
   Go back to the document library where you uploaded the template. Click the gear icon and choose Library settings. Then click Permissions for this document library.
2. Add the Copilot service account
   Click Grant permissions. In the People field, type Copilot or Microsoft Copilot Service. The exact name depends on your tenant. If you cannot find the service account, add the Microsoft 365 group called Everyone except external users and ensure it has at least Read access.
3. Test the access
   Open a new browser session and navigate directly to the template file URL. If you can view the file without signing in again, Copilot can also access it.

Step 4: Restart Word and Test Copilot

1. Close and reopen Word
   This step forces Word to refresh the list of available templates from SharePoint.
2. Create a new document with Copilot
   Open a blank document. In the Copilot pane, type a prompt such as “Create a project proposal using the company template.” Copilot should now generate content that follows the template structure.

If Copilot Still Ignores the Template After the Fix

Copilot Returns Plain Text Without Template Formatting

If Copilot generates content but does not apply the template formatting, the template may not be saved in a Copilot-compatible format. Save the template as a .dotx file (Word Template) and re-upload it. Do not use .dotm files that contain macros unless you have verified that your organization allows macro-enabled templates in SharePoint.

Copilot Cannot Find Any Templates at All

If Copilot says it cannot find templates, check the SharePoint site collection settings. Go to SharePoint admin center > Active sites > select your site > Settings > Site collection features. Ensure the feature “SharePoint Server Publishing Infrastructure” is activated. This feature enables the template gallery.

Template Appears in Word but Not in Copilot

Word can display templates from the local user templates folder, but Copilot cannot. Remove any local copies of the template from the user templates folder. The only copy of the template should be in SharePoint. Then restart Word and test again.

Local Template vs SharePoint Template: Key Differences for Copilot

Item	Local Template	SharePoint Template
Storage location	User's local drive under AppData\Microsoft\Templates	SharePoint document library or template gallery
Copilot access	No access	Full access if permissions are set
Required permissions	None	Read permission for Copilot service account
Indexing by Microsoft Graph	Not indexed	Indexed automatically
Organizational default	Cannot be set	Can be set in SharePoint template gallery
Updates	Must be manually pushed to each user	Centralized, updates apply to all users

After you move the template to SharePoint and set it as the organizational default, Copilot can access and apply the template. Test by creating a new document with a prompt that references the template by name. If the template still does not load, verify that the SharePoint site where the template is stored is active and that the Copilot service account has at least Read permissions on the document library. You can also check the Microsoft 365 admin center under Copilot settings to confirm that SharePoint is enabled as a data source.