Skip to main content
Book a demo

Connect Microsoft Word to Claude Cowork

Give Claude Cowork governed access to Microsoft Word’s 4 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Cowork setup guide

Set up

Add Microsoft Word to Claude Cowork in four steps

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

  1. 1

    Approve Microsoft Word in Runlayer

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

  2. 2

    Connect Claude Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Microsoft Word’s 4 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to Microsoft Word

    Each user signs in to Microsoft Word with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Microsoft Word from Claude Cowork

    Microsoft Word’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.

Tools

4 Microsoft Word tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork users can call.

  • Add comment

    Add a new comment in the Word document.

  • Create document

    Create a new Word document in the root of the user's OneDrive.

  • Get document content

    Fetch the raw Word document (DOCX) content from OneDrive/SharePoint given its SharePoint sharing URL.

  • Reply to comment

    Reply to a comment in the Word document.

Control

What Runlayer can see and stop in Claude Cowork

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

  • Gateway policy (available)

    Every Microsoft Word call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination