Connect Microsoft 365 Copilot Search to ECA
Give ECA governed access to Microsoft 365 Copilot Search’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft 365 Copilot Search to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Microsoft 365 Copilot Search in Runlayer
Add Microsoft 365 Copilot Search from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Microsoft 365 Copilot Search’s 1 tool through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to Microsoft 365 Copilot Search
Each user signs in to Microsoft 365 Copilot Search with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Microsoft 365 Copilot Search from ECA
Microsoft 365 Copilot Search’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
1 Microsoft 365 Copilot Search tools in ECA
Runlayer policy decides which of these ECA users can call.
Chat
Search internal Microsoft 365 content (documents, emails, chats, sites, files) when the specific workload is unclear or spans multiple areas, but always prefer workload-specific tools (SharePoint,…
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Microsoft 365 Copilot Search call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more