Skip to main content
Book a demo

Connect Exa Websets to Microsoft 365 Copilot

Give Microsoft 365 Copilot governed access to Exa Websets’s 23 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Microsoft 365 Copilot setup guide

Set up

Add Exa Websets 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. 1

    Approve Exa Websets in Runlayer

    Add Exa Websets from the catalog and choose who can use it and which of its tools are allowed.

  2. 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 Exa Websets’s 23 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Microsoft 365 Copilot setup guide
  3. 3

    Sign in to Exa Websets

    Sign in the way Exa Websets requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Exa Websets from Microsoft 365 Copilot

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

Tools

23 Exa Websets tools in Microsoft 365 Copilot

Runlayer policy decides which of these Microsoft 365 Copilot users can call.

  • Cancel enrichment

    Cancel a running enrichment operation.

  • Cancel search

    Cancel a running search operation.

  • Create enrichment

    Create a new enrichment for a webset.

  • Create import

    Create a new import to upload your own data (CSV) into Websets.

  • Create search

    Create a new search to find and add items to a webset.

  • Create webhook

    Create a webhook to receive real-time HTTP callbacks when events occur in your websets.

  • Create webset

    Create a new Webset collection.

  • Delete webhook

    Delete a webhook.

See all 23 Exa Websets tools

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 Exa Websets 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

Find another combination