Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Microsoft 365 Copilot node lets a workflow hand a step over to Microsoft 365 Copilot, grounded in the running user's mail, files, calendar, chats, and other Microsoft 365 content. Use it whenever a step needs an answer or to create content that depends on the user's day-to-day work in Microsoft 365.
The node can also call specific Microsoft 365 agents. Select from Microsoft-built agents like Researcher and Analyst, or agents your team builds in Agent Builder.
By using the Microsoft 365 Copilot node, you can:
- Send a prompt to Microsoft 365 Copilot and use the response in later steps.
- Target a specific Microsoft 365 agent, such as Researcher, Analyst, or an Agent Builder agent.
- Pass dynamic content from earlier steps into the prompt.
Add a Microsoft 365 Copilot node
In Copilot Studio, go to Flows and open an existing workflow, or create a new one.
- New workflow: You land on the designer to configure a trigger.
- Existing workflow: Open the workflow and go to the Build tab.
Select the M365 Copilot icon on the Add panel.
The configuration panel opens for the Microsoft 365 Copilot node.
Sign in with a Microsoft 365 account
The node runs on behalf of a Microsoft 365 user. The response is grounded in that user's mail, files, calendar, and other Microsoft 365 content.
Write the message
In the Message field, write what you want Microsoft 365 Copilot, or the targeted agent, to do for this run. Use the dynamic content picker to insert tokens from earlier steps so the call reasons over real run-time data.
For example, in a workflow that triggers when a sales rep marks a lead as qualified in Dynamics 365, the message might be Summarize all emails, Teams chats, and meeting notes between our team and the contacts at followed by the Account name token from the trigger.
Be specific about the task and the format of the response you want back. If you need a list, ask for a list. If you need a one-paragraph summary, say so.
Target a specific agent
By default, the node calls Microsoft 365 Copilot. To call a specific agent instead, select Advanced parameters > Agent. An Agent dropdown appears with a list of available Microsoft 365 Copilot agents. The list includes:
- Researcher: For deep, multi-source research that pulls together information from across the web and your Microsoft 365 content.
- Analyst: For working with data, including cleaning, summarizing, and reasoning over numbers from spreadsheets and other sources.
- Agents your team built in Agent Builder: Your tenant's custom agents appear in the list and can be called directly from the workflow.
When you select an agent, the Message field is the prompt sent to that agent for this run. The agent's own instructions, knowledge, and tools are already configured wherever the agent was built.
Leave Agent empty when you want the general Microsoft 365 Copilot experience and don't need a specialized agent.
Set the time zone
Under Advanced parameters, the Time Zone field controls how Microsoft 365 Copilot interprets relative times in your message, such as yesterday's meetings or this week's emails. The field is preset to a default. Change it to match the user the workflow runs as so the call resolves the right window.
Use the Microsoft 365 Copilot response in your workflow
When the node finishes, it exposes its result as dynamic content for any downstream step.
Select the next action where you want to use the result (for example, Send an email or Post a message in Teams).
Open the dynamic content picker on the field you want to fill.
Select the response output from the M365 Copilot step.
Common patterns:
- Insert the response into an email body, a Teams message, or a SharePoint list item.
- Save the response to OneNote, OneDrive, or Word as a generated draft.
- Pass the response into a later agent or prompt node for further processing.
Automation scenarios
The Microsoft 365 Copilot node works best as one step in a longer workflow. Earlier steps choose what to ask about, the node calls Microsoft 365 Copilot or a targeted agent, and later steps deliver the result across the systems people actually work in.
Audit response drafting
A workflow triggers when an email arrives in the compliance mailbox with Audit request in the subject line. The Microsoft 365 Copilot node sends the message Search our policy library, controls documentation, and prior audit responses in SharePoint for material relevant to this request: followed by the Body token from the trigger, asking for the relevant policy excerpts and prior citations. Later steps draft a response document in SharePoint with the citations attached and start an approvals action routed to the compliance lead.
Deep research with the Researcher agent
A workflow triggers when a new opportunity is created in Dynamics 365. An earlier step pulls the account name and industry. The Microsoft 365 Copilot node, with Agent set to Researcher, sends Produce a one-page brief on followed by the Account name token, asking for recent news, leadership changes, and likely pain points. Later steps attach the brief to the opportunity record and post a Teams message to the assigned seller.
Data review with the Analyst agent
A workflow triggers when a finance team member uploads a monthly close file to a SharePoint library. The Microsoft 365 Copilot node, with Agent set to Analyst, sends Review the attached close file and call out any line items that look out of line with the prior three months. Later steps post the analyst's findings as comments on the file and start an approvals action if anything is flagged.
Custom Agent Builder agent for company-specific work
A workflow triggers when a customer submits an intake form. An earlier step pulls the customer's tier and recent purchases; the Microsoft 365 Copilot node, with Agent set to a custom Customer success agent built in Agent Builder, sends a prompt asking for a recommended next action grounded in the company's playbooks. Later steps create a task in Planner with the recommendation and notify the assigned account manager.
Frequently asked questions
When should I use the Microsoft 365 Copilot node vs. an agent node?
Both nodes bring AI into a workflow, but they call different things.
| Capability | Microsoft 365 Copilot node | Agent node |
|---|---|---|
| What it calls | Microsoft 365 Copilot, or an existing Microsoft 365 agent (Researcher, Analyst, Agent Builder, non-Microsoft) | An existing custom agent, or a new inline agent built in the node |
| Configuration | Select which agent and write the prompt | Configure instructions, tools, knowledge, and output shape |
| Microsoft 365 grounding | Built in. Runs as the connected Microsoft 365 user | Optional, via Work IQ |
| Best for | Reusing what's already in Microsoft 365 | Building automation-specific agents that travel with the workflow |
Use the Microsoft 365 Copilot node to bring an existing Microsoft 365 capability, such as Microsoft 365 Copilot itself, Researcher, Analyst, or an Agent Builder agent, into the workflow. Use the agent node when the workflow needs a custom agent with specific instructions, tools, and knowledge that you assemble inline.
Does the node have access to my Microsoft 365 content?
Yes. The node runs as the Microsoft 365 user in the Connection field, so it can ground its response in that user's mail, files, calendar, and chats. Select the connection account carefully. Whatever that user can see in Microsoft 365, the workflow can use.
What kinds of agents show up in the Agent dropdown?
Two kinds: Microsoft-built agents like Researcher and Analyst, or agents your team publishes from Agent Builder. Each agent comes preconfigured with its own instructions, knowledge, and tools. The node just sends the message to the agent and returns the response.