Use Claude for M365 with third-party platforms changedoffice-agents/third-party-platforms
Nearest release: v2.1.299, published 9 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 13 Oct 2026 14:49 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 13 Oct 2026 15:07 UTC.
Upstream edited
Recorded here
Lines+49added
Lines−4removed
From line
63
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits8to this page, all time
### Route Vertex AI direct through your own gateway
The whole hunk
from line 63, old and new numbered
/
from line 63
6363| - | - | - |
6464| `pivot.claude.ai` | Always | Add-in host serving task pane UI, analytics, icon search, skill downloads, and telemetry. |
6565| `claude.ai` | Always | Anthropic OAuth sign-in and feature-flag evaluation. |
66| `hcaptcha.com`, `*.hcaptcha.com` | Always | hCaptcha browser check on the `claude.ai` sign-in and approval pages, which open in the user's web browser. If these domains are blocked, the sign-in approval can fail with a message that the browser couldn't be verified. |
6667| `api.anthropic.com` | Always | Claude inference API, file uploads, code-execution containers, and MCP connector registry. |
6768| `appsforoffice.microsoft.com` | Always | Microsoft Office.js runtime script (required by all Office add-ins). |
6869| `login.microsoftonline.com` | If using Outlook | Microsoft Entra ID sign-in via Nested App Auth for the Graph token. |
from line 110
109110| `aiplatform.googleapis.com` | If using Vertex AI direct | Vertex AI global inference endpoint. |
110111| `<region>-aiplatform.googleapis.com` | If using Vertex AI direct | Vertex AI regional inference endpoint; replace `<region>` with your GCP region. |
111112| `<resource>.services.ai.azure.com` | If using Foundry direct | Azure AI Foundry inference endpoint; replace `<resource>` with your resource name. |
113| Your Vertex AI gateway URL | If using Vertex AI direct through your own gateway | The gateway or proxy set in `gcp_base_url`. Connections made while it is set do not call `aiplatform.googleapis.com` or `<region>-aiplatform.googleapis.com`. Google sign-in still uses `accounts.google.com` and `oauth2.googleapis.com`. |
112114| Your Foundry gateway URL | If using Foundry direct through your own gateway | The gateway or proxy set in `azure_base_url`. Connections made while it is set do not call `<resource>.services.ai.azure.com`. |
113115| `graph.microsoft.com` | If using Outlook | Microsoft Graph mailbox and calendar API. |
114116
from line 117
115117If Anthropic serves your add-in settings from your Claude organization,
116118as described in
117119[Serve add-in settings from your Claude organization](#serve-add-in-settings-from-your-claude-organization),
118also allow `claude.ai` and `api.anthropic.com`. Members sign in with
119their Claude account at `claude.ai`, and the add-in reads your
120organization's settings from `api.anthropic.com`. Inference still goes
121only to the gateway or cloud provider those settings name.
120also allow `claude.ai`, `api.anthropic.com`, `hcaptcha.com`, and
121`*.hcaptcha.com`. Members sign in with their Claude account at
122`claude.ai`, and the add-in reads your organization's settings from
123`api.anthropic.com`. The `claude.ai` sign-in and approval pages run an
124hCaptcha browser check. Inference still goes only to the gateway or cloud
125provider those settings name.
122126
123127## Deploy the add-in for your organization
124128
from line 271
267271| `addin.access` | Kill switch: the add-in refuses to run. |
268272| `file.upload` | Blocks attaching files to the conversation. |
269273| `web_search` | Removes the built-in web search and web fetch tools, whose queries are served by Anthropic's search provider, along with the user-facing web search toggle. Code execution is unaffected. |
274| `permission_mode.accept_all_edits` | Keeps users in "Ask before edits": "Accept all edits" and "Skip all permissions" can't be turned on, and users already in either mode go back to "Ask before edits". Connector "Always allow" choices are unaffected. |
275| `permission_mode.dangerously_always_allow` | Removes the "Dangerously always allow" button from approval cards. It switches users to the mode shown as "Skip all permissions"; users already in that mode are moved to "Accept all edits". |
270276
271277Unknown slugs are ignored, so setting a slug from a newer add-in version
272278on an older deployment is safe.
from line 648
642648| `azure_resource_name` | Your Foundry resource name. |
643649| `azure_base_url` | The gateway base URL, for example `https://ai-gateway.example.com/foundry/anthropic`. |
644650| `azure_api_key` | The key the gateway expects as `x-api-key`. Omit it with keyless sign-in. |
651
652### Route Vertex AI direct through your own gateway
653
654If your organization reaches Vertex AI through a gateway or proxy it
655operates, set `gcp_base_url` to that gateway's base URL, API version
656included. Each user still signs in with Google, and the add-in keeps the
657Vertex AI request format, but it sends every request to
658`<gcp_base_url>/projects/<project>/locations/<region>/publishers/anthropic/models/<model>:rawPredict`,
659or `:streamRawPredict` for streaming responses, instead of
660`https://<region>-aiplatform.googleapis.com/v1/...`, with the user's
661Google access token as `Authorization: Bearer`. Google sign-in and token
662refresh still go to `accounts.google.com` and `oauth2.googleapis.com`.
663`gcp_project_id`, `google_client_id`, and `google_client_secret` are
664still required, and `gcp_region` still names the region in the request
665path.
666
667Use the same value you would set as Claude Code's
668`ANTHROPIC_VERTEX_BASE_URL`. The URL must use HTTPS. Because the add-in
669calls the gateway from the browser, the gateway must meet the
670[CORS requirements](#cors-requirements), and your network must allow its
671domain as listed in the [network allowlist](#network-allowlist). On this
672path the add-in sends the same headers it sends to Vertex AI:
673`authorization`, `content-type`, `accept`, and `user-agent`. The token
674the gateway receives is the user's Google OAuth token with the
675`cloud-platform` scope, so the gateway should forward it to Vertex AI
676and not store it.
677
678Users who connected before you set `gcp_base_url` keep their direct
679connection until they log out and sign in again, as described in
680[Change or update your gateway connection](#change-or-update-your-gateway-connection).
681Until the setup wizard accepts this key, add `gcp_base_url` to the
682generated manifest URL by hand, or deliver it per user through Microsoft
683Entra ID extension attributes or a bootstrap endpoint.
684
685| Parameter | Value |
686| - | - |
687| `gcp_project_id` | Your Google Cloud project ID. |
688| `gcp_region` | The Vertex AI region, or `global`. |
689| `gcp_base_url` | The gateway base URL, for example `https://ai-gateway.example.com/vertex/v1`. |
645690
646691### Change or update your gateway connection
647692
No line in this hunk matches that.