Skip to main content
Book a demo

Connect Microsoft 365 Copilot Search to Hermes

Give Hermes governed access to Microsoft 365 Copilot Search’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Hermes setup guide

Set up

Add Microsoft 365 Copilot Search to Hermes in four steps

Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.

  1. 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. 2

    Connect Hermes to Runlayer

    Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Microsoft 365 Copilot Search’s 1 tool through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Hermes setup guide
  3. 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. 4

    Use Microsoft 365 Copilot Search from Hermes

    Microsoft 365 Copilot Search’s approved tools appear in Hermes. Every call is checked against policy and recorded.

Tools

1 Microsoft 365 Copilot Search tools in Hermes

Runlayer policy decides which of these Hermes 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 Hermes

Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.

  • Gateway policy (available)

    Every Microsoft 365 Copilot Search call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Hermes as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Hermes runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output in Hermes and show a message in its place.

  • Redact output in place (not available)

    Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Hermes

  • Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.

Frequently asked questions

Connect more

Find another combination