The entry is still marked In development. Its general availability target is November 2026, which means the target month has already started but the feature has not been confirmed as shipped. Here is what the roadmap says, what Copilot Studio documentation shows about the current Agent node, and what is still unknown.
What the roadmap entry says
Roadmap item 580865 describes the feature as follows:
- File outputs from the Agent node: Files the agent generates become workflow outputs. The listed examples are PDF, Word, Excel, PowerPoint and CSV.
- Both agent types: It works with inline agents (agents defined inside the workflow) and existing, published agents.
- Output shape: Generated files appear as an ordered files output. Each file has a name, content type and content, and later workflow steps can use it.
- Downstream use: Files can be passed to connectors to email them, save them to SharePoint or OneDrive, or attach them to records.
- Scope: Microsoft Copilot Studio, Web platform, Worldwide (Standard Multi-Tenant) cloud. The release ring is listed as General Availability.
Microsoft's roadmap page includes its usual warning: it provides estimated release dates and descriptions for commercial features, and all information is subject to change. Treat November 2026 as a target, not a promise.
Section summary: The Agent node is expected to return generated Office, PDF and CSV files as a structured list that later workflow steps can send or store. The feature is still in development.
Why this matters: the current Agent node returns text and data, not files
Microsoft's current Copilot Studio documentation explains why this change is useful. It says makers use the Output dropdown to control the shape of what the agent returns. A text response output is exposed as a single agent response variable. A structured output is a predefined object with named fields. Microsoft's example triage agent returns a structured output with category, priority, suggested_owner, and draft_reply.
That is useful for classification and routing. It is not a document. WindowsForum's earlier coverage of the Agent node (roadmap item 562222, which reached general availability in September 2026) noted that output can be text, named structured fields, or a custom JSON-schema object; structured fields become downstream dynamic-content tokens.
Builders have already hit this limit. In a thread on Microsoft's Q&A forum, a team described a Copilot Studio agent with skills that run Python scripts to generate Word documents (.docx). They found the generated file could not be passed onward when the agent ran from a workflow Agent node. The answer in that thread was blunt. When asked whether the Agent node can return created files, it said: Not as a documented Agent-node output. It also explained that the separate "Files the agent creates" preview surfaces files as downloadable cards in conversational experiences and stores them with the conversation. That covers files in chat, not files handed to an unattended workflow.
Roadmap item 580865 appears aimed directly at that gap: getting generated files out of the agent and into the rest of the automation.
Section summary: Today the Agent node returns text or structured data. Files an agent creates in a workflow run have had no documented route to later steps, and this roadmap item targets that.
Files have been able to go into the Agent node for a while
Getting files into an agent has been supported for some time. Microsoft's documentation lists two common scenarios: Outlook email attachments and SharePoint files. For SharePoint, you can retrieve files using a SharePoint "Get file content" node and pass the files to the agent node, which can extract data from documents stored in the SharePoint site.
The roadmap item adds the opposite direction. A workflow could plausibly bring in an attachment, have an agent analyse it, and send out a finished document in one run. That is our reading of the roadmap's examples, not a design Microsoft has documented.
What the workflows could look like
Based on the examples Microsoft lists, these patterns become realistic once the feature ships:
- Generated report, then email: An agent drafts a PDF or Word summary and an email connector step attaches it.
- Generated spreadsheet, then SharePoint or OneDrive: An agent writes an Excel workbook or CSV and a later step saves it to a document library.
- Generated document, then a business record: The file is attached to a record. The roadmap says "attach to records" without naming which systems.
The ordered files output detail matters for builders. A list of files with name and content type means a later step could, in principle, route a CSV one way and a PowerPoint deck another. The roadmap does not say how the order is decided, so test before relying on a particular file sitting in a particular position.
What's still unknown
The roadmap entry is short, and we found no Microsoft documentation for this specific capability yet. Several questions remain open:
| Question | What's known |
|---|---|
| Content encoding (binary vs. base64, etc.) | Not specified |
| File-size or file-count limits | Not specified |
| Full list of supported formats | Only the examples given (PDF, Word, Excel, PowerPoint, CSV) |
| Which connectors accept the files | Only the examples given (email, SharePoint/OneDrive, records) |
| Licensing, permissions, admin controls | Not specified |
| Differences between inline and published agents | Not specified; both are listed as supported |
| GCC / sovereign clouds | Only Worldwide Standard Multi-Tenant is listed |
Section summary: The overall purpose is clear. File handling details, limits and governance controls have not been documented, so don't plan production work around guesses.
Advice for admins and makers
This is our analysis, based on the roadmap and current documentation:
- Keep current workarounds until the feature is in your tenant. "In development" with a November target does not mean it is live. Microsoft's roadmap defines "Launched" separately as fully released and generally available.
- Choose inline or published agents deliberately. As WindowsForum previously reported, inline agents belong to their workflow and cannot be reused elsewhere, while a published agent is the appropriate option when several workflows need the same capability. The same reasoning applies if one document-generating agent will serve several workflows.
- Test the node on its own before connecting real actions. Microsoft notes you can use the Test pane in the agent's side panel to run the agent node and inspect its output. Do this before a generated file reaches a real customer's inbox.
- Review governance. An agent that can write a file to SharePoint or email it externally can also leak data. Check data loss prevention (DLP) policies and connector permissions now, not after the first misfire.
The bottom line
AI-generated documents in Copilot Studio have often stayed inside the conversation that produced them. Roadmap item 580865 would let the Agent node pass PDFs, Word documents, spreadsheets, decks and CSVs to later workflow steps, which would make document generation part of the automation itself. The idea is sound and fixes a gap builders have run into. Until Microsoft publishes documentation and the status changes from In development, treat it as a roadmap entry and keep your existing approach in place.
References
- Microsoft Copilot Studio: Generate documents from the Agent node in workflows Microsoft 365 Roadmap · 2026-11-19T21:30:10.359329Z
- Add an agent node to a workflow (GitHub Copilot) - Microsoft Copilot Studio learn.microsoft.com
- GitHub Copilot harness: agent-created file can’t be passed to an agent-flow tool when the agent runs from a workflow Agent node - Microsoft Q&A learn.microsoft.com