Skip to main content
If you manage Claude Desktop from the Enterprise Admin Console, you can manage Claude for Microsoft 365 there too.

How console settings reach the add-in

A member signs in from the add-in with their Claude account. The add-in then gets its connection and its settings from the console. Prompts still go to your gateway or cloud provider. Your settings apply only to members who sign in to this organization. Members can change the connection. Control access at your gateway or provider. For what the add-in sends to Anthropic, see What leaves the device. For the features that members get, see the third-party platform column in Differences from signing in with a Claude account.

Before you start

Ensure that:
  • You’re an Owner or Primary Owner of the organization.
  • Your users are members of the organization.
  • The Connection page under Desktop 3P is saved. Bedrock Mantle and custom Bedrock base URLs aren’t supported.
  • Your provider meets the add-in’s requirements.
  • If you use a gateway, it allows CORS from https://pivot.claude.ai, including the authorization header.
  • Your network allows the third-party platform domains, plus claude.ai, api.anthropic.com, hcaptcha.com, and *.hcaptcha.com.
If your add-in gets gateway or Foundry credentials from Microsoft Entra ID or a bootstrap endpoint, keep that setup and leave sign-in off. A member who signs in to this organization stops using that setup. They need a token or key instead, and it doesn’t renew.

Turn on sign-in

Sign-in from the add-in is off by default.
A member who selects “Log in” can also sign in with another paid Claude account or organization. This is true whether sign-in is on or off. With a personal plan, for example, the add-in sends prompts and document content to Anthropic, and your console settings don’t apply.To block personal plans and organizations that you don’t allow, set up tenant restrictions and include this organization’s ID in the allowed list. Tenant restrictions need a proxy with TLS inspection, and they cover only traffic through that proxy. A member can still authorize the sign-in from a device or network that doesn’t use the proxy, such as a phone or a home network.
1

Open the Office Agents page

On claude.ai, switch to the organization and open Organization settings, Products, Office Agents.
2

Turn on the switch

Turn on “Allow sign-in from the Claude add-in”. If your provider is Bedrock, also enter “IAM role for the Microsoft 365 add-in”. Select “Save changes”.
3

Deploy the add-in

Deploy the add-in from Microsoft AppSource for Excel, PowerPoint, and Word or Outlook. Outlook also needs Microsoft Graph admin consent.Use this deployment in place of any custom manifest, because a custom manifest can hide “Log in”.
4

Give members a credential

Give members the credential for your provider:
  • Gateway: a gateway token
  • Foundry: a Foundry API key
  • Vertex AI: a Google client ID and secret
  • Bedrock: no credential
The add-in can’t use Claude Desktop’s sign-in or helper script for your provider.

Sign in as a member

Send members these steps. Replace <organization name> with the organization’s name as shown on claude.ai. A member whose add-in is already connected logs out first. Logging out deletes their saved Outlook conversations. You can start from this text:

Change settings or turn off sign-in

The Office Agents page controls Office apps, features, document access policies, and skills. The add-in also uses the console’s model list, OpenTelemetry collector, and supported MCP servers. The collector and the servers must allow CORS too.
  • When changes take effect: a change usually reaches an add-in that’s online within about 10 minutes. If it doesn’t, ask the member to restart the Office app.
  • After you change the connection: ask members to select “Logout” and sign in again. Logging out deletes their saved Outlook conversations. A new gateway address or header applies without logging out if their token still works.
  • To turn off sign-in: turn off the switch and select “Save changes”. Members then see “Claude isn’t available for your organization here”.