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 theauthorizationheader. - Your network allows the
third-party platform domains,
plus
claude.ai,api.anthropic.com,hcaptcha.com, and*.hcaptcha.com.
Turn on sign-in
Sign-in from the add-in is off by default.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
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”.