Use Claude for M365 with third-party platforms changedoffice-agents/third-party-platforms
Nearest release: v2.1.314, published 6 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 29 Oct 2026 17:15 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 29 Oct 2026 17:37 UTC.
Upstream edited
Recorded here
Lines+95added
Lines−25removed
From line
5
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits14to this page, all time
### Skill limits for a bootstrap endpoint
The whole hunk
from line 5, old and new numbered
/
from line 5
55Organizations using Amazon Bedrock, Google Cloud Vertex AI, Azure AI
66Foundry, or an LLM gateway can deploy Claude's Office add-ins without
77requiring individual Claude accounts. The add-in connects through your
8organization's infrastructure, keeping prompts and responses within your
9trust boundary.
8organization's infrastructure, sends prompts to the provider your
9organization chooses, and receives Claude's responses from it. See
10[What Anthropic collects](#what-anthropic-collects) for what reaches
11Anthropic on Amazon Bedrock, Google Cloud Vertex AI, and Azure AI
12Foundry.
1013
1114## Connection paths
1215
from line 112
109112| `oauth2.googleapis.com` | If using Vertex AI direct | Google OAuth token exchange and refresh. |
110113| `aiplatform.googleapis.com` | If using Vertex AI direct | Vertex AI global inference endpoint. |
111114| `<region>-aiplatform.googleapis.com` | If using Vertex AI direct | Vertex AI regional inference endpoint; replace `<region>` with your GCP region. |
115| `aiplatform.us.rep.googleapis.com`, `aiplatform.eu.rep.googleapis.com` | If using Vertex AI direct with region `us` or `eu` | Vertex AI multi-region inference endpoints. |
112116| `<resource>.services.ai.azure.com` | If using Foundry direct | Azure AI Foundry inference endpoint; replace `<resource>` with your resource name. |
113117| 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`. |
114118| 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`. |
from line 126
122126`claude.ai`, and the add-in reads your organization's settings from
123127`api.anthropic.com`. The `claude.ai` sign-in and approval pages run an
124128hCaptcha browser check. Inference still goes only to the gateway or cloud
125provider those settings name.
129provider the add-in connects to.
126130
127131## Deploy the add-in for your organization
128132
from line 294
290294`/claude-for-msft-365-install:access-policies` commands document both
291295keys in full.
292296
297### Skill limits for a bootstrap endpoint
298
299A bootstrap endpoint can return a `skills` array of admin-provisioned
300skills. The add-in applies these limits to each response.
301
302| Limit | Value |
303| - | - |
304| Skills kept | The first 20 skill names, in array order. No setting changes this number. Uploaded and built-in skills don't count toward it. |
305| Repeated names | One skill for each name: the last entry with that name, in the position of the first. |
306| Skill `url` | HTTPS, no redirects, CORS for `https://pivot.claude.ai`, and 15 seconds for each download. |
307| Bootstrap call | 10 seconds in total to get the user's Microsoft Entra token, when the add-in uses one, and to receive the response. This limit applies to each bootstrap call, except the call made when the add-in sets up a new connection, for example at first use or after a sign-out. |
308
309If a skill fails to load, the add-in doesn't replace it with a later
310skill. To see which skills failed to load, select the + button at the
311bottom of the chat pane, and then select Skills. A note at the top of the
312list names up to three of those skills and gives the number of any others.
313
314If a bootstrap call takes more than 10 seconds when the add-in
315loads with an existing connection, the add-in has no admin-provisioned
316skills until a later bootstrap call succeeds.
317
318To stay within these limits:
319
320* Put the most important skills first.
321* Return a different list for each app. The `X-Claude-User-Agent` header
322 on each bootstrap call starts with `claude-word`, `claude-excel`,
323 `claude-powerpoint`, or `claude-outlook`.
324* Use `url` instead of inline `content` for large skills. Inline content
325 is part of the bootstrap response, so it counts toward the 10 seconds.
326 The add-in downloads skill URLs after the bootstrap call, and only for
327 the skills that it keeps.
328
329If a response holds more than 20 different skill names, the add-in sends
330the warning log record `Bootstrap skill count exceeds cap — truncating`
331to your [OpenTelemetry collector](https://claude.com/docs/office-agents/opentelemetry.md) at
332`{your_url}/v1/logs`. Your collector might not receive this record for
333the bootstrap call made when the add-in sets up a new connection. On that
334record, `count` is the number of different skill names in the response,
335and `cap` is the limit, 20.
336
293337### Deploy to Outlook
294338
295339Outlook requires a separate manifest file from Excel, PowerPoint, and
from line 406
362406Claude organization directly, in place of manifest parameters, Microsoft
363407Entra ID attributes, or a bootstrap endpoint. Members sign in with the
364408add-in's standard "Log in" button and their Claude account. The add-in
365then reads the organization's settings from Anthropic and connects to
366the gateway or cloud provider those settings name. Prompts and responses
367still travel only to that provider, never to Anthropic.
409then reads the organization's settings from Anthropic and fills in the
410connection screen with them. Prompts and responses still travel only to
411the gateway or cloud provider the add-in connects to. What reaches
412Anthropic then depends on the provider, as
413[What Anthropic collects](#what-anthropic-collects) describes.
368414
369415This option is in preview. It works in Anthropic's preview environments
370416and is not yet enabled for production organizations. Members need the
from line 432
386432 verify your organization's sign-in."
3874333. After the reload, the add-in reads the organization's settings from
388434 `api.anthropic.com` and opens the connection screen with the served
389 values filled in, such as the gateway URL, API format, authorization
390 header, and available models. When the served settings include every
391 value the connection needs, the add-in connects without further
392 input. Otherwise the member enters the missing value, typically the
393 gateway token from your IT team, and connects.
435 values filled in, such as the gateway URL. When the served settings
436 include every value the connection needs, the add-in connects without
437 further input. Otherwise the member enters the missing value,
438 typically the gateway token from your IT team, and connects.
3944394. While the member stays signed in, the add-in reads the served
395440 settings again at each launch and periodically while it runs, so
396441 changes an admin makes apply without redeploying the manifest.
from line 448
403448[Admin feature controls](#admin-feature-controls). A few rules are
404449specific to this path:
405450
406* **Single source**: for a member signed in this way, the served
407 document is the only configuration source. The add-in does not merge
408 it with manifest parameters, Entra ID attributes, or a bootstrap
409 endpoint, and nothing from the task pane URL fills a key the served
410 document leaves out.
451* **Connection values**: for a member signed in this way, the add-in
452 fills in the connection screen from the served settings, not from
453 manifest parameters, Entra ID attributes, or a bootstrap endpoint.
454* **Other connection paths**: on the connection screen, the member can
455 select another [connection path](#connection-paths) and enter their
456 own values. The add-in then sends prompts to the provider the member
457 chose.
458* **Supported providers**: served settings can name an LLM gateway,
459 Bedrock, Vertex AI, or Foundry as the inference provider.
460* **Unsupported settings**: if served settings name Bedrock Mantle or
461 set a Bedrock base URL, the add-in makes no new connection. A member
462 who is already connected keeps that connection until they sign out. A
463 member who isn't connected yet sees the connection screen without its
464 fields, with Try again and Sign out actions. After you change the
465 served settings, the member selects Try again to load them. Until
466 then, the screen shows one of these messages:
467 * Bedrock Mantle: "This add-in can't use your organization's inference
468 provider. Let your IT team know."
469 * Bedrock base URL: "This add-in can't use your organization's Bedrock
470 base URL. Let your IT team know."
411471* **Applied as delivered**: the add-in applies served settings the same
412472 way it applies manifest configuration, with no per-setting consent
413473 prompt. The Claude organization admin who edits served settings can
from line 949
889949add-in experience. They do not transmit your prompts or Claude's
890950responses.
891951
892Anthropic collects information in accordance with Amazon Bedrock, Google
893Cloud Vertex AI, or Microsoft Azure's terms, consistent with Anthropic's
894arrangements with customers. Anthropic does not have access to a
895customer's AWS, Google, or Microsoft instance, including prompts or
896outputs it contains. Anthropic does not train generative models with
897such content or use it for other purposes. Anthropic can access
898metadata such as tool use and token counts, and uses such metadata for
899analytic and product-improvement purposes.
952When the add-in uses Amazon Bedrock or Google Cloud Vertex AI, directly
953or through a gateway, Anthropic collects information in accordance with
954that platform's terms, consistent with Anthropic's arrangements with
955customers. Anthropic does not have access to a customer's AWS or Google
956instance, including prompts or outputs it contains. Anthropic does not
957train generative models with such content or use it for other purposes.
958Anthropic can access metadata such as tool use and token counts, and
959uses such metadata for analytic and product-improvement purposes.
900960
961When the add-in uses Azure AI Foundry, directly or through a gateway,
962Anthropic operates the Claude models as an independent processor for
963Microsoft, and Anthropic's data use terms apply. For deployments hosted
964on Azure, prompts and responses stay within Azure, and only usage
965metadata and content flagged by Anthropic's safety systems reach
966Anthropic. For deployments hosted on Anthropic, prompts and responses are
967processed on Anthropic's infrastructure. See
968[Claude in Microsoft Foundry](https://platform.claude.com/docs/en/build-with-claude/claude-in-microsoft-foundry)
969for details.
970
901971For details on what your organization's gateway or cloud provider logs,
902972contact your IT team.
903973
from line 1115
10451115third-party platforms yet. Support is being added. A member who signs in
10461116with a Claude account to an organization whose settings Anthropic
10471117serves is in the third-party platform column too, because inference
1048goes to the organization's provider.
1118goes to a gateway or cloud provider.
10491119
10501120| Feature | Claude account | Third-party platform |
10511121| - | - | - |
No line in this hunk matches that.