Connect Gem to Microsoft 365 Copilot
Give Microsoft 365 Copilot governed access to Gem’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gem 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 Gem to Runlayer
Gem 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 Gem’s 15 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Microsoft 365 Copilot setup guide - 3
Sign in to Gem
Sign in the way Gem requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Gem from Microsoft 365 Copilot
Gem’s approved tools appear in Microsoft 365 Copilot. Every call is checked against policy and recorded.
Tools
15 Gem tools in Microsoft 365 Copilot
Runlayer policy decides which of these Microsoft 365 Copilot users can call.
Get application
Look up one application (a candidate on a specific job) by ext_id — status, stage, stage_entry, gem_status (the Talent Pipeline's computed next-step status and SLA health, e.g. NEEDS_DECISION /…
Get job
Look up one job by ext_id — title, status, requisition id, ATS, department/office, and link.
Get metrics catalog
List the metrics and dimensions this team can report on with query_metrics.
Get person
Look up one candidate by ext_id — name, current title, company, school, emails, phone numbers, and links, plus optional fields (full work history, education, custom fields, applications, activity…
Get project
Look up one project by ext_id — name, description, owner, link, type, privacy, archived status, and people_count (candidates in the project).
Get saved report
Look up one saved analytics report (Pipeline Analytics or Outreach) by ext_id — its name, type, owner, link, and a ready-to-run query_metrics payload translated from the report's saved configuration.
Get sequence
Look up one outreach sequence by ext_id — name, status, whether it is a reusable template (is_template) and whether it is archived (is_archived), owner, link, a version (the sequence's edit version —…
Get sequence tokens
List the merge tokens available for writing a sequence stage's subject or body on this team.
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 Gem 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