Connecting employee survey data to Microsoft 365 Copilot
Survey data can reach Microsoft 365 Copilot as a file, a Copilot connector, or a declarative agent using MCP. Each route sets who can see what employees said.
AI HR Skills Editorial TeamYou can connect employee survey data to Microsoft 365 Copilot in four ways. You can put a results file where Copilot can already read it, index the data with a synced Copilot connector, fetch it live through a federated connector, or build a declarative agent that calls the survey system through the Model Context Protocol (MCP). Each route changes who can ask Copilot about what employees said.
That last point is the one HR has to own. Survey comments are sensitive, and Copilot answers from whatever the person asking is allowed to see. Here’s how each route works, according to Microsoft’s documentation, and what to decide first.
Key takeaways
- Microsoft 365 Copilot only shows people data they already have permission to see, so the permissions on survey data decide who can ask about it.
- Synced Copilot connectors copy data into Microsoft Graph with an access list on each item, while federated connectors fetch it live through MCP with each person’s own permissions.
- A declarative agent can connect to a survey system’s MCP server or API, and Microsoft documents OAuth and Microsoft Entra sign-in options for that link.
- Our advice: decide what level of survey data belongs in Copilot before you connect anything, since team-level results carry less risk than raw comments.
Route 1: A file Copilot can already read
The simplest route needs no building. A survey export saved in SharePoint or OneDrive is already Microsoft 365 data. Microsoft’s privacy documentation says Copilot presents only data each person can access, using the same controls as the rest of Microsoft 365.
So the file’s sharing settings are the safeguard. Say a results workbook with raw comments sits in a folder the whole department can open. Then anyone in that department can ask Copilot to summarize it.
Route 2: A synced Copilot connector
Copilot connectors bring data from outside Microsoft 365 into Copilot. Microsoft renamed them from Microsoft Graph connectors, and older pages still use that name. A synced connector copies content from another system into Microsoft Graph and indexes it so Copilot can search and summarize it.
For survey data, the important detail is the access list. According to Microsoft’s Graph documentation, every item a synced connector adds carries an access control list. That list grants or denies access to specific users, groups, or everyone in the organization.
Whoever builds the connector sets that list. If survey comments go in marked for everyone, everyone can find them.
Route 3: A federated connector over MCP
A federated connector doesn’t copy anything. It uses MCP to fetch data live from the source system, using each person’s own identity and permissions in that system. The data stays where it is.
According to Microsoft, admins manage federated connectors in the Microsoft 365 admin center. Microsoft publishes some, and partners submit others for Microsoft to approve. Where a connector offers the tools, Copilot can also create, update, or delete data in the source system with the user’s approval.
A survey platform would need to offer one before this route exists for you. Check Microsoft’s connector gallery rather than assuming it does.
Route 4: A declarative agent with an MCP or API action
A declarative agent is Microsoft 365 Copilot set up for a specific scenario, with its own instructions, knowledge, and actions. Microsoft’s documentation describes adding an MCP server to a declarative agent as a plugin. The agent connects to a remote MCP server for the survey system, which it points to but doesn’t host. Sign-in options include OAuth and Microsoft Entra single sign-on.
This route suits a dedicated tool, such as an agent that answers managers’ questions about their own team’s results. It also means a third party’s server receives requests. Microsoft says organizations should only enable declarative agents that use trusted knowledge sources and trusted APIs. It also says externally hosted services stay responsible for their own permissions and privacy.
Route 1
A file in SharePoint or OneDrive
- Where the data lives
- In Microsoft 365, as a file
- Who can ask about it
- Anyone the file is shared with
Route 2
Synced Copilot connector
- Where the data lives
- Copied and indexed in Microsoft Graph
- Who can ask about it
- Whoever the connector's access list allows
Route 3
Federated connector over MCP
- Where the data lives
- Stays in the survey system, fetched live
- Who can ask about it
- People with access in the survey system itself
Route 4
Declarative agent with an MCP or API action
- Where the data lives
- In the survey system, reached through the provider's server
- Who can ask about it
- Agent users, within the survey system's own permissions
What to decide before any survey data goes in
Microsoft’s documentation explains the mechanics. The decisions below are our recommendations for HR teams, not Microsoft’s.
- Choose the level of detail. Aggregated scores by team are one thing. Raw comments are another, because a single comment can point to the person who wrote it.
- Keep your small-group rule. If your survey tool holds back results for groups below a set size, make sure the data you connect follows the same rule. A synced connector copies what you give it.
- Match access to who needs it. Managers may need their own team’s themes. They rarely need every comment from every team.
- Tell employees. If survey results become searchable in Copilot, say so in the survey’s privacy note.
A hypothetical example
Imagine a hypothetical people analytics lead at a 1,500-person company who wants managers to ask Copilot about their engagement results. She starts with Route 1 and saves a workbook with every raw comment in a shared HR folder.
Before launch, she checks who can open that folder and finds it includes every people manager. She replaces the workbook with team-level summaries, each shared only with that team’s manager, and keeps the raw comments in the survey system.
Where survey tools fit
Connecting existing data is different from running the survey. For running surveys inside Microsoft 365, including Copilot in Forms and Copilot in Viva Glint, see how Copilot in Forms compares with employee listening.
Check which assistants a survey tool says it works in before you plan a route. For example, the FeedbackPulse eNPS Survey Builder listing describes a plugin that helps design an eNPS or pulse survey in ChatGPT, and it lists ChatGPT as its runtime, not Microsoft 365 Copilot. Any tool you connect should pass the same bar we set in how listings are reviewed.
FAQ
Can Microsoft 365 Copilot read our employee survey results?
Yes, if the results are somewhere Copilot can reach, such as a file in SharePoint or data brought in through a Copilot connector. It only shows each person what they already have permission to see.
What’s the difference between a synced and a federated Copilot connector?
A synced connector copies data into Microsoft Graph and indexes it. A federated connector fetches data live through MCP and leaves it in the source system.
Is a Copilot connector the same as a Graph connector?
Yes. Microsoft renamed Microsoft Graph connectors to Microsoft 365 Copilot connectors, and older documentation still uses the earlier name.
Do survey comments stay anonymous in Copilot?
Copilot doesn’t make data anonymous. It follows the permissions on the data. If raw comments are visible to someone, Copilot can summarize them for that person.
What to do next
Start by deciding what level of survey data belongs in Copilot and who should be able to ask about it. Then pick the simplest route that respects that. For many teams, that’s a summary file with tight sharing, not a connector. Bring in IT before you set up a connector or agent, since both need an admin to set them up or allow them.
To find tools for the rest of your listening work, browse the full library of HR skills and plugins or see other guides in the resources section.
Sources
- Source: Data, Privacy, and Security for Microsoft Copilot, Microsoft Learn
- Source: Microsoft 365 Copilot connectors overview, Microsoft Learn
- Source: Create, update, and delete items in a Microsoft Graph connection, Microsoft Learn
- Source: Federated connectors overview, Microsoft Learn
- Source: Build a plugin for a declarative agent from an MCP server, Microsoft Learn
- Source: Compare declarative and custom engine agents, Microsoft Learn
- Source: Plan Data, Privacy, and Security for Microsoft 365 Copilot Extensibility, Microsoft Learn