Share
ReportI’m working with Copilot Studio agents (including child agents) and trying to understand whether it’s possible to create or modify a Word file directly from a Copilot agent, without relying on Power Automate or external document APIs.
What I’m trying to do
- Start from an existing Word document (SOW) stored in SharePoint
- Update specific values only (pricing and dates)
- Preserve all original formatting (fonts, styles, tables, headers, layout)
- Return the updated document to the user as a downloadable file in the Copilot chat
- Copilot agents (including child agents) can reason over content and return structured data (JSON, Base64, etc.)
- However, attempts to:
- Generate a file directly from an agent, or
- Recreate a Word file from text/Base64 returned by an agent
result in formatting changes or corrupted documents
- The only reliable solution I’ve found is using Power Automate with Word/Graph-based actions, then returning the file via Respond to Copilot (File output)
Is this limitation expected?
Specifically:
- Are Copilot agents intentionally not designed to create or modify Office files directly?
- Is there any supported way for a Copilot agent alone (without Power Automate) to:
- Create or modify a Word document
- Preserve 100% of formatting
- And return it as a downloadable file?
Or is Power Automate / Microsoft Graph / Word Online the only supported and recommended approach for file creation and modification in this scenario?
Any clarification on the design intent or roadmap would be really helpful.
I have the same question (3)
All responses (
Answers (
12
