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 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+110added
Lines−126removed
From line
47
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits8to this page, all time
The whole hunk
from line 47, old and new numbered
/
from line 47
4747differ depending on whether your organization uses the Anthropic API
4848directly (1P) or a third-party platform (3P).
4949
50<Note>
51 In all configurations, prompts and responses travel only to your chosen
52 inference provider. Domains pointing to Anthropic (such as
53 `pivot.claude.ai`) serve the add-in's interface, feature configuration,
54 and operational telemetry, not prompt or response content.
55</Note>
50> [!NOTE]
51>
52> In all configurations, prompts and responses travel only to your chosen
53> inference provider. Domains pointing to Anthropic (such as
54> `pivot.claude.ai`) serve the add-in's interface, feature configuration,
55> and operational telemetry, not prompt or response content.
5656
5757### Anthropic API (1P)
5858
from line 180
180180
181181When complete, the add-in is ready for tenant-wide deployment.
182182
183<Note>
184 Bedrock and Vertex AI paths require Node.js for manifest generation and
185 validation. The wizard checks for it and prompts installation if
186 missing.
187</Note>
183> [!NOTE]
184>
185> Bedrock and Vertex AI paths require Node.js for manifest generation and
186> validation. The wizard checks for it and prompts installation if
187> missing.
188188
189189### Available commands
190190
from line 231
231231manifest defaults, so one deployed manifest can serve teams with
232232different settings.
233233
234<Frame caption="Configuration resolution at add-in load: bootstrap, Entra ID attributes, then manifest parameters.">
235 <img src="https://mintcdn.com/claude-ai/-4jzPa4NasvobarI/images/office-agents/architecture/config-discovery.png?fit=max&auto=format&n=-4jzPa4NasvobarI&q=85&s=b6c750272cf3ad9765ec2563af436806" alt="The add-in resolves each configuration key from a bootstrap endpoint, then Entra ID extension attributes, then manifest parameters." width="2398" height="1670" data-path="images/office-agents/architecture/config-discovery.png" />
236</Frame>
234
237235
238236### Keep credentials out of the manifest URL query string
239237
from line 311
313311client ID to the setup wizard as `graph_client_id`. See
314312[Use your own Entra app instead](/docs/office-agents/outlook#use-your-own-entra-app-instead).
315313
316<Note>
317 Claude for Outlook on third-party platforms supports Claude Opus 4.7 and
318 later and Claude Sonnet 5 and later. Earlier model generations are not
319 available on the Outlook surface.
320</Note>
314> [!NOTE]
315>
316> Claude for Outlook on third-party platforms supports Claude Opus 4.7 and
317> later and Claude Sonnet 5 and later. Earlier model generations are not
318> available on the Outlook surface.
321319
322320### Deploy to Microsoft 365
323321
324322After the wizard generates your manifest files:
325323
326<Steps>
327 <Step title="Upload the manifest">
328 Open the Microsoft 365 Admin Center and go to Settings, Integrated
329 apps, Upload custom apps. Select "Office Add-in" as the app type,
330 then upload the `manifest.xml` file. If you are deploying Outlook,
331 repeat this step with `manifest-outlook.xml` as a second custom app.
332 </Step>
324**1. Upload the manifest**
333325
334 <Step title="Choose who gets the add-in">
335 If all users share the same configuration, select "Entire
336 organization". If you wrote per-user attributes, assign to "Specific
337 users/groups" matching exactly who was configured. Others would open
338 the add-in with no configuration.
339 </Step>
326Open the Microsoft 365 Admin Center and go to Settings, Integrated
327apps, Upload custom apps. Select "Office Add-in" as the app type,
328then upload the `manifest.xml` file. If you are deploying Outlook,
329repeat this step with `manifest-outlook.xml` as a second custom app.
340330
341 <Step title="Finish deployment">
342 Accept permissions and finish deployment.
343 </Step>
344</Steps>
331**2. Choose who gets the add-in**
345332
333If all users share the same configuration, select "Entire
334organization". If you wrote per-user attributes, assign to "Specific
335users/groups" matching exactly who was configured. Others would open
336the add-in with no configuration.
337
338**3. Finish deployment**
339
340Accept permissions and finish deployment.
341
346342Propagation to users takes up to 24 hours, usually faster. The add-in
347343appears under Tools, Add-ins on Mac or Home, Add-ins on Windows in
348344Excel, PowerPoint, and Word once deployed. In Outlook it appears in the
from line 349
353349fails. Run `/claude-for-msft-365-install:debug` to diagnose these, or to
354350sideload and validate a manifest locally before a tenant-wide upload.
355351
356<Note>
357 Start with a pilot group to confirm functionality, then widen
358 assignment. You can change assignment later without redeploying.
359</Note>
352> [!NOTE]
353>
354> Start with a pilot group to confirm functionality, then widen
355> assignment. You can change assignment later without redeploying.
360356
361357## Serve add-in settings from your Claude organization
362358
from line 460
464460Use these steps if your IT team told you to sign in with your Claude
465461account and your organization's settings are served by Anthropic.
466462
467<Steps>
468 <Step title="Open the add-in">
469 Open Excel, PowerPoint, Word, or Outlook and launch the Claude add-in.
470 </Step>
463**1. Open the add-in**
471464
472 <Step title="Log in with your Claude account">
473 On the sign-in screen, select "Log in", then approve the sign-in in
474 the browser window that opens. The task pane reloads when the
475 sign-in is accepted.
476 </Step>
465Open Excel, PowerPoint, Word, or Outlook and launch the Claude add-in.
477466
478 <Step title="Review the connection and connect">
479 The connection screen opens with your organization's values filled
480 in. If a field such as the gateway token is empty, enter the value
481 your IT team provided, then connect. If every value was served, the
482 add-in connects on its own.
483 </Step>
484</Steps>
467**2. Log in with your Claude account**
485468
469On the sign-in screen, select "Log in", then approve the sign-in in
470the browser window that opens. The task pane reloads when the
471sign-in is accepted.
472
473**3. Review the connection and connect**
474
475The connection screen opens with your organization's values filled
476in. If a field such as the gateway token is empty, enter the value
477your IT team provided, then connect. If every value was served, the
478add-in connects on its own.
479
486480If another Claude task pane was already open, it shows "Reload to finish
487481signing in". Select Reload in that pane.
488482
489483### LLM gateway
490484
491<Steps>
492 <Step title="Open the add-in">
493 Open Excel, PowerPoint, Word, or Outlook and launch the Claude add-in.
494 </Step>
485**1. Open the add-in**
495486
496 <Step title="Select your connection mode">
497 On the sign-in screen, select "Cloud provider or gateway". Then
498 choose your connection: Gateway, Vertex, Bedrock, or Azure. Contact
499 your IT team for connection details if you're unsure which one to
500 select.
501 </Step>
487Open Excel, PowerPoint, Word, or Outlook and launch the Claude add-in.
502488
503 <Step title="Enter your credentials">
504 For Gateway, enter the gateway URL (HTTPS base URL of your LLM
505 proxy, for example
506 `https://llm-gateway.example.com`) and the API token your IT team
507 provided. By default the add-in sends the token in the `x-api-key`
508 header with every request. If your admin set
509 `gateway_auth_header: authorization` in the manifest, the add-in
510 sends `Authorization: Bearer <token>` instead.
511 </Step>
489**2. Select your connection mode**
512490
513 <Step title="Connect">
514 The add-in checks the connection by sending a test request to the
515 gateway. On success, you see the main add-in experience.
516 </Step>
517</Steps>
491On the sign-in screen, select "Cloud provider or gateway". Then
492choose your connection: Gateway, Vertex, Bedrock, or Azure. Contact
493your IT team for connection details if you're unsure which one to
494select.
518495
496**3. Enter your credentials**
497
498For Gateway, enter the gateway URL (HTTPS base URL of your LLM
499proxy, for example
500`https://llm-gateway.example.com`) and the API token your IT team
501provided. By default the add-in sends the token in the `x-api-key`
502header with every request. If your admin set
503`gateway_auth_header: authorization` in the manifest, the add-in
504sends `Authorization: Bearer <token>` instead.
505
506**4. Connect**
507
508The add-in checks the connection by sending a test request to the
509gateway. On success, you see the main add-in experience.
510
519511Your credentials are stored locally in your browser's localStorage
520512within the add-in's sandboxed iframe and are not synced to Anthropic's
521513servers. Because the Office add-in runs in a sandboxed iframe within
from line 518
526518In this path, every request travels from the add-in to your gateway,
527519which forwards it to the provider you configured.
528520
529<Frame caption="LLM gateway request flow: the add-in calls your gateway, which routes to your chosen provider.">
530 <img src="https://mintcdn.com/claude-ai/-4jzPa4NasvobarI/images/office-agents/architecture/gateway.png?fit=max&auto=format&n=-4jzPa4NasvobarI&q=85&s=287ef25266391992109b8673f97e3f93" alt="Requests flow from the add-in to your LLM gateway, which forwards them to the configured model provider." width="2540" height="1030" data-path="images/office-agents/architecture/gateway.png" />
531</Frame>
521
532522
533523### Bedrock, Vertex AI, or Foundry direct
534524
535<Steps>
536 <Step title="Open the add-in">
537 Open Excel, PowerPoint, Word, or Outlook and launch the Claude add-in.
538 </Step>
525**1. Open the add-in**
539526
540 <Step title="Authenticate">
541 For Bedrock (Excel, PowerPoint, and Word only), sign in with your
542 Microsoft work account. The add-in uses your Entra ID token to
543 assume the AWS role your admin
544 configured, so no separate AWS credentials are needed.
545 For Vertex AI, sign in with the Google account your admin authorized
546 via the Google OAuth client created during setup.
547 For Foundry, the add-in connects automatically if your admin
548 pre-filled the Azure resource name and API key. If your admin enabled
549 keyless sign-in, the add-in uses your Microsoft work account and no
550 key is involved. Otherwise, enter the values your IT team provided
551 and select Connect.
552 </Step>
527Open Excel, PowerPoint, Word, or Outlook and launch the Claude add-in.
553528
554 <Step title="Start working">
555 The add-in reads the configuration your admin provisioned and
556 connects to Bedrock, Vertex AI, or Foundry directly.
557 </Step>
558</Steps>
529**2. Authenticate**
559530
531For Bedrock (Excel, PowerPoint, and Word only), sign in with your
532Microsoft work account. The add-in uses your Entra ID token to
533assume the AWS role your admin
534configured, so no separate AWS credentials are needed.
535For Vertex AI, sign in with the Google account your admin authorized
536via the Google OAuth client created during setup.
537For Foundry, the add-in connects automatically if your admin
538pre-filled the Azure resource name and API key. If your admin enabled
539keyless sign-in, the add-in uses your Microsoft work account and no
540key is involved. Otherwise, enter the values your IT team provided
541and select Connect.
542
543**3. Start working**
544
545The add-in reads the configuration your admin provisioned and
546connects to Bedrock, Vertex AI, or Foundry directly.
547
560548If you see an error at sign-in, confirm with your IT team that your
561549account is in the group assigned to the add-in.
562550
from line 555
567555Bedrock direct uses your Microsoft Entra ID token to assume an AWS role,
568556then calls Amazon Bedrock.
569557
570<Frame caption="Bedrock direct flow: the add-in exchanges an Entra ID token for an AWS role, then calls Bedrock.">
571 <img src="https://mintcdn.com/claude-ai/-4jzPa4NasvobarI/images/office-agents/architecture/bedrock-direct.png?fit=max&auto=format&n=-4jzPa4NasvobarI&q=85&s=51c8233f704717f0ff1c3897356621cd" alt="The add-in uses a Microsoft Entra ID token to assume an AWS role and call Amazon Bedrock directly." width="2540" height="1030" data-path="images/office-agents/architecture/bedrock-direct.png" />
572</Frame>
558
573559
574560Vertex AI direct authenticates through Google OAuth, then calls Vertex
575561AI.
576562
577<Frame caption="Vertex AI direct flow: the add-in authenticates with Google OAuth, then calls Vertex AI.">
578 <img src="https://mintcdn.com/claude-ai/-4jzPa4NasvobarI/images/office-agents/architecture/vertex-direct.png?fit=max&auto=format&n=-4jzPa4NasvobarI&q=85&s=a33063abcecbfc36e346621f735453ef" alt="The add-in authenticates through Google OAuth and calls Google Cloud Vertex AI directly." width="2540" height="1030" data-path="images/office-agents/architecture/vertex-direct.png" />
579</Frame>
563
580564
581565### Foundry direct without an API key
582566
from line 790
806790
807791## Example gateway configuration with LiteLLM
808792
809<Warning>
810 LiteLLM PyPI versions 1.82.7 and 1.82.8 contained credential-stealing
811 malware. Do not install those versions. If already installed, remove the
812 package, rotate all credentials on affected systems, and follow
813 remediation steps in [BerriAI/litellm#24518](https://github.com/BerriAI/litellm/issues/24518).
814</Warning>
793> [!WARNING]
794>
795> LiteLLM PyPI versions 1.82.7 and 1.82.8 contained credential-stealing
796> malware. Do not install those versions. If already installed, remove the
797> package, rotate all credentials on affected systems, and follow
798> remediation steps in [BerriAI/litellm#24518](https://github.com/BerriAI/litellm/issues/24518).
815799
816800LiteLLM is a third-party proxy service. Anthropic does not endorse,
817801maintain, or audit LiteLLM's security or functionality. This section is
No line in this hunk matches that.