Many business documents are prepared on a regular cycle: monthly, quarterly, or annually. The process often looks like this: a team opens the previous account-review deck, saves a copy, and updates the same fields, such as customer, segment, owner, and highlights. Then it repeats the process for the next set of data.
Slide design is not the problem. The work is populating an approved layout with the correct data. This repetitive, precise task is a good candidate for automation. A Copilot Studio agent can do it with
OfficeAgent.NET, which
duplicates an approved slide for each account, fills shapes named in the
template, and saves the result as a new .pptx file in SharePoint.
The workflow is as follows:
- The brand team designs and owns the PowerPoint template.
- The agent duplicates an approved slide rather than inventing a layout.
- Named shapes are used as reliable fields such as ClientName and Owner.
- The completed deck is saved separately, leaving the template untouched.
What you need
- A hosted OfficeAgent.NET 0.6.0 MCP server connected to the SharePoint library that stores the template.
- A Copilot Studio environment that can add an existing MCP server as a tool. Microsoft documents the current setup flow in Connect your agent to an existing MCP server.
- A PowerPoint template with one reusable account slide.
In previous articles, I described how to deploy the MCP server and how to connect it to a Copilot Studio agent.
You can reuse an existing agent that already uses OfficeAgent.NET for Word files, or create a new one by following those articles. Add a separate SharePoint connection for decks instead of widening the Word connection.
Configure a connection for PowerPoint
Copy the existing SharePoint connection block, keep its tenant and application credentials, and change these values:
OfficeAgent__SharePointConnections__1__ConnectionId=decks
OfficeAgent__SharePointConnections__1__AllowedExtensions__0=.pptx
OfficeAgent__SharePointConnections__1__DefaultChangeMode=Direct
Restart the hosted server and ask the agent to list the available document connections. Confirm that decks appears before working on the template.
Turn template shapes into fields
Create a small template deck with a title slide and one account slide. On the account slide, open PowerPoint's Selection pane and rename the shapes the agent should fill:
- ClientName
- Segment
- Owner
- Highlights
Those names are the contract between the template and the agent. The agent does not need to know the coordinates, font, colour, or size of a field. It asks OfficeAgent.NET to fill ClientName, and the library resolves the named shape.
Save the template in the SharePoint library configured for the decks
connection.
Ask the agent to build the deck
Copy the template's SharePoint URL and give the agent a bounded request. The
customer names and results below are fictional demonstration data.
Use the decks connection and register this presentation:
https://contoso.sharepoint.com/sites/sales/Shared%20Documents/account-review-template.pptx
For the first duplication, use saveMode NewVersion and continue with the
returned output document. Never apply changes directly to the template.
For each customer, duplicate the account slide in a separate plan. After each
duplication, inspect the working copy again. Fill ClientName, Segment, Owner,
and Highlights on the new slide. Preview every plan before applying it. Use
saveMode Replace only for later plans on the working copy.
After all customer slides are filled, remove the original blank account slide
in a separate plan.
Return the completed working-copy file. Do not overwrite the template.
Customer 1
Client name: Northwind Traders
Segment: Enterprise
Owner: Priya Raman
Highlights: Renewed early; two new sites live; NPS increased to 61
Customer 2
Client name: Fabrikam
Segment: Mid-market
Owner: Tom De Vries
Highlights: Migration completed in July; support tickets decreased by one third
Verify the result
After the request is executed, open both the source and the generated file in
PowerPoint.
The template should still contain its original two slides. The generated deck
should contain one account slide per customer, with the template's master,
theme, layout, notes, fonts, colours, and shape positions preserved.
Three safeguards matter in this workflow:
- Scope the decks connection to the required SharePoint library and .pptx files.
- Create a working copy before making changes, and leave the approved template untouched.
- Reinspect after each duplication and preview every plan before applying it.
Conclusion
Agents are useful not only when they create something new. Often, their greater
value is applying an approved pattern reliably at scale.
In this example, PowerPoint remains the design system. Copilot Studio supplies
the intent, and OfficeAgent.NET performs bounded operations on the PowerPoint
file. SharePoint keeps the template and generated deck in the existing document
workflow.
What are recurring documents that you would automate first?
Top comments (0)