Connect Honeycomb to Microsoft 365 Copilot
Give Microsoft 365 Copilot governed access to Honeycomb’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Honeycomb to Microsoft 365 Copilot in four steps
Admins approve the server once. Everyone in Microsoft 365 Copilot then gets it through the same governed connection.
- 1
Add Honeycomb to Runlayer
Honeycomb isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Microsoft 365 Copilot to Runlayer
Users add the Runlayer Plugin to Microsoft 365 Copilot by following Runlayer’s setup guide. Microsoft 365 Copilot reaches Honeycomb’s 38 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Microsoft 365 Copilot setup guide - 3
Sign in to Honeycomb
Sign in the way Honeycomb requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Honeycomb from Microsoft 365 Copilot
Honeycomb’s approved tools appear in Microsoft 365 Copilot. Every call is checked against policy and recorded.
Tools
38 Honeycomb tools in Microsoft 365 Copilot
Runlayer policy decides which of these Microsoft 365 Copilot users can call.
Canvas agent invoke
Kick off a single-turn run of the Honeycomb Canvas agent.
Canvas agent poll response
Poll for the result of a previously-issued canvas_agent_invoke call.
Create board
Create a board (dashboard) with query, SLO, and text panels.
Create burn alert
Create a burn alert on an SLO.
Create marker
Creates a marker (a vertical annotation on charts) to mark a point or window in time, such as a deploy, incident, or config change.
Create recipient
Create a notification recipient (email, Slack, PagerDuty, or webhook) so it can be attached to triggers, SLO burn alerts, and Anomaly Detection.
Create slo
Create an SLO (Service Level Objective) backed by an auto-created SLI derived column.
Create trigger
Create a trigger that fires alerts when a query result crosses a threshold.
Control
What Runlayer can see and stop in Microsoft 365 Copilot
Some controls apply to every client at the gateway. Others depend on what Microsoft 365 Copilot exposes to Runlayer.
Gateway policy (available)
Every Honeycomb call from Microsoft 365 Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Microsoft 365 Copilot as the client, the tool, and the policy and scanner decisions.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Microsoft 365 Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more
