When you use Copilot in Microsoft Word, you may notice it sometimes fails to reference content from linked files such as Excel charts, PowerPoint slides, or embedded documents. This happens because Copilot reads the text and structure of the open Word document but does not automatically traverse file links to pull data from external sources. Understanding how Copilot handles linked files helps you avoid unexpected gaps in generated summaries, drafts, or insights. This article explains the technical behavior, shows you how to configure your documents for accurate references, and outlines common pitfalls to avoid.
Key Takeaways: Copilot and Linked File References in Word
- Copilot > Draft with Copilot > Reference settings: Controls whether Copilot can access linked file content — set to “Files in this document” only, not external paths.
- Insert > Object > Text from File: Embeds the full content of an external file into the Word document so Copilot can read it directly.
- Copilot pane > Settings > Data sources: Shows which Microsoft Graph data Copilot can use — linked files outside the tenant or with restricted permissions are excluded.
How Copilot Reads Content in Word Documents
Copilot in Word uses the same underlying AI model as other Microsoft 365 Copilot features. It processes the text, tables, headings, and structural elements of the active document. However, it does not automatically follow external file links to retrieve content from other files. A linked file is an object or a hyperlink that points to data stored in a separate file, such as an Excel spreadsheet or a PowerPoint presentation. When Copilot encounters a linked object, it sees only the placeholder or the link path, not the actual data.
The root cause is security and permission boundaries. Copilot respects the same access controls that apply to the user running the session. If the linked file resides outside the current tenant, requires different authentication, or contains sensitive data that the user does not have explicit permission to read, Copilot cannot access it. This is by design to prevent data leakage across organizational boundaries.
Linked Objects vs Embedded Objects
A linked object stores only a reference to the source file. When you double-click the object, Word opens the source file. An embedded object stores a copy of the source file inside the Word document. Copilot can read embedded objects because the data is part of the document content. Linked objects are invisible to Copilot unless the source file is also open in the same Microsoft 365 session and the user has granted Copilot access to that file.
Hyperlinks to External Files
Hyperlinks in Word that point to other files, such as file://server/share/data.xlsx, are treated as navigation elements. Copilot does not follow these links to extract content. If you want Copilot to reference data from an external file, you must either embed the file content or copy the relevant text directly into the Word document.
Steps to Ensure Copilot Can Reference Linked File Content
To make sure Copilot reads content from files you reference, use one of the following methods. Each method works for a different scenario.
Method 1: Embed the File Content Directly
- Open the Word document
Navigate to the location where you want the external content to appear. - Go to Insert > Object > Text from File
Select the source file — Excel, PowerPoint, PDF, or another Word document. Word inserts the content as editable text within the current document. - Save the Word document
Copilot now sees the inserted text as part of the document. When you use Draft with Copilot or Ask Copilot, it can reference this content.
Method 2: Open the Source File in the Same Session
- Open the linked source file
Launch the Excel workbook, PowerPoint file, or other source in the same Microsoft 365 desktop app or browser session. - Grant Copilot access to the source file
If the file is stored in OneDrive or SharePoint, ensure the file has been opened at least once by the user. Copilot requires that the file be in the user’s recent files list or in a SharePoint site the user has visited. - Use the Copilot pane in Word
Type a prompt that references the source file by name, such as “Summarize the data from the Q3 sales file.” Copilot may retrieve content from the source file if it is in the same Microsoft 365 context.
Method 3: Copy and Paste the Relevant Data
- Open the source file
Copy the specific cells, slides, or paragraphs you need. - Paste into the Word document
Use Paste Special > Keep Source Formatting or Merge Formatting to preserve structure. - Verify Copilot can see the pasted content
Highlight the pasted content and ask Copilot to summarize it. If Copilot responds correctly, the content is accessible.
Common Issues When Copilot Cannot Reference Linked Files
Copilot Returns Generic Output Instead of Tenant-Specific Data
If Copilot generates a vague response that does not include data from your linked file, the file is likely not embedded or opened in the same session. Re-embed the content using Insert > Object > Text from File. After embedding, run the same prompt again.
Copilot Shows a Permission Denied Message
The linked file may be in a SharePoint site or OneDrive folder where the user does not have read access. Check the file permissions by opening the file in a browser. If you cannot read the file manually, Copilot cannot read it either. Ask the file owner to grant at least read access.
Copilot Ignores Linked Excel Charts
Linked Excel charts are OLE objects. Copilot does not parse OLE objects for text or data. To make chart data available, copy the chart and paste it as a picture or embed the underlying data table. Alternatively, paste the chart as a linked picture — Copilot can read the picture caption if you add one, but not the chart data itself.
File Path Contains Special Characters or Spaces
Copilot may fail to resolve linked files when the file path includes characters like &, %, or non-ASCII letters. Rename the source file to use only alphanumeric characters, hyphens, and underscores. Then re-link the object in Word.
Copilot in Word: Linked File Access vs Embedded Content
| Item | Linked Object | Embedded Content |
|---|---|---|
| Description | Reference to an external file stored separately | Copy of the external file stored inside the Word document |
| Copilot access | No — Copilot sees only the link placeholder | Yes — Copilot reads the embedded text and data |
| File size impact | Minimal — only the link path adds size | Larger — the full source content is duplicated |
| Permission requirement | User must have access to the external file location | No external permission needed after embedding |
| Update behavior | Reflects changes in the source file automatically | Does not update unless the user re-embeds the content |
Use embedded content when you need Copilot to reference the data reliably. Use linked objects when you need the data to stay current with the source file and you do not need Copilot to read it.
Now you know that Copilot in Word cannot follow file links to read external data. To make linked content visible to Copilot, embed the file content using Insert > Object > Text from File, or copy and paste the relevant data directly into the document. For files you must keep linked, open the source file in the same Microsoft 365 session and verify permissions are set to read access. As a next step, test Copilot with a document that contains both embedded and linked content to see the difference in response accuracy. A practical tip: before a Copilot session, use the Copilot pane to check which files it has indexed by typing “What files can you access?”