Copilot in Word handles Excel reports

Key insights

• Daniel Anderson shows a Word-based way to answer a common Copilot request.
• Copilot in Word can reference an Excel workbook with a forward slash.
• The demo fills a report table from several worksheets and rewrites the executive summary.
• He says no agent, instructions, or maintenance are needed for this task.
• The whole workflow is shown as taking under three minutes.

Daniel Anderson [MVP] recently published a video asking whether you really need a Copilot agent for routine document work. His example shows Copilot in Word pulling data from an Excel workbook, filling a report table, and rewriting the executive summary inside the same document. The takeaway is simple: for some everyday tasks, Word itself may already do the job without building a separate agent.

The video is framed around a question many users already ask: “Can Copilot or an agent fill out this Word doc for me?” Anderson’s answer is to start in the document you already have open, point Copilot at the spreadsheet, and let it work on the file in front of you. He says the process needs no agent to build, no instructions to write, and nothing to maintain.

What's new

The key point in the demo is that Copilot in Word can work with an Excel workbook as a source and use that data to complete a report. Anderson shows Copilot filling in a table from data spread across several worksheets, then updating the executive summary so it matches the new figures. That makes the feature useful for document updates that are tied to a live spreadsheet rather than a free-form chat answer.

He also highlights the difference between simply asking Copilot questions and allowing it to edit the document. In his workflow, the user opens Word, references the spreadsheet with a forward slash, turns on editing, and lets Copilot carry out the changes. The whole task is shown without cuts or time lapse, and he says it takes under three minutes.

Why it matters

This matters most for people who already work inside Word and Excel every day. For admins and makers, it is a reminder that not every AI-assisted workflow needs a separate agent or custom build. If the task lives inside one document and reads from another file you can point to, Word may already provide enough automation for the job.

For end users, the practical value is speed and less setup. Instead of defining an agent, writing instructions, and maintaining it over time, the user can stay in the document and ask Copilot to use a spreadsheet as context. Anderson also suggests asking a few simple questions before building an agent: whether the work stays in an open file, whether the needed information sits in another file, whether the task must run without the user, and whether it happens often enough to justify maintenance.

The material does not say anything about licensing or a staged rollout for this specific workflow. It does, however, position agents as useful in some cases, while showing that direct use of Copilot in Word can be enough for straightforward report updates. For readers planning Word and Excel work, that is the main decision point.

How it works

Anderson describes a simple workflow rather than a complex build. The user opens the Word document, references the Excel workbook with a forward slash, enables editing, and then asks Copilot to fill the report. Copilot uses the spreadsheet as the source, populates the table, and rewrites the summary to match the updated figures.

1. Open the Word document you want to complete.
2. Point Copilot to the Excel workbook using the forward slash.
3. Turn on editing so Copilot can change the file.
4. Ask Copilot to fill the report from the spreadsheet data.
5. Let Copilot rewrite the executive summary with the new numbers.

He also uses this example to show the choice point between chat and editing. Chat alone can help with answers and drafting ideas, but the demonstrated use case depends on Copilot making direct changes to the document. That is why the editing step matters in his workflow.

Limitations and open questions

The video focuses on one practical scenario, so it does not show broader agent features or more complex automation. It also does not explain whether the workbook must be structured in a particular way, or how Copilot decides which data to use when several worksheets are involved. Those details are not verified in the source material.

Anderson says agents still have a place, especially if the work must run without the user or be reused by other people. He also asks whether the task happens often enough to justify building and maintaining something. That leaves the boundary clear: this is a good fit for a one-off or repeatable in-document task, but not a full replacement for every agent scenario.

The material also does not confirm tenant-wide availability, supported license levels, or any rollout status for this exact behaviour. The research notes mention agentic capabilities in Word, Excel, and PowerPoint, but the video itself stays focused on the practical demo rather than on product packaging. For readers comparing options, the message is to start with the document workflow before moving to a custom agent.

Sources

• Daniel Anderson [MVP] video: Do You Really Need a Copilot Agent? Copilot in Word Does This
• Daniel Anderson [MVP] LinkedIn profile

Frequently asked questions

What is Daniel Anderson showing in this video?

He shows Copilot in Word filling a report from an Excel workbook, then rewriting the executive summary so it matches the new data.

Does the workflow require building a Copilot agent?

No. Anderson’s point is that for this kind of document task, you can use Copilot inside Word without building an agent.

How does Copilot get the spreadsheet data?

He says to point Copilot at the spreadsheet with the forward slash, then turn on editing and let it work in the document.

Is this meant to replace agents completely?

No. Anderson says agents still have a place when work must run without you, be reused by others, or justify ongoing maintenance.