Skip to main content

Connect dbt to Microsoft 365 Copilot

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

Set up

Add dbt 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 dbt in Runlayer

    Add dbt 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 dbt’s 42 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 dbt

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

  4. 4

    Use dbt from Microsoft 365 Copilot

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

Tools

42 dbt tools in Microsoft 365 Copilot

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

  • Cancel job run

    Cancel a currently running or queued dbt run.

  • Get all macros

    Get the name, description, and package name of all dbt macros in the environment.

  • Get all models

    Get the name and description of all dbt models in the environment.

  • Get all sources

    Get the name, description, and metadata of all dbt sources in the environment.

  • Get dimension values

    Get the distinct values for a given dimension, optionally scoped to specific metrics.

  • Get dimensions

    Get the dimensions for specified metrics

  • Get entities

    Get the entities for specified metrics

  • Get exposure details

    DEPRECATED — use get_node_details instead.

See all 42 dbt 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 dbt 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