Microsoft Office

• Anthropic’s Claude for Microsoft 365 add-in puts Claude directly inside Excel, PowerPoint, and Word. An organization admin deploys one manifest and employees just open Claude, with usage billed to the organization’s AI Reserve account.
• GPT for Work is a separate third-party add-in for Word and Excel. It accepts an AI Reserve API key and an OpenAI-compatible endpoint.
• Office Scripts and Power Automate are do-it-yourself automation options that call the OpenAI-compatible API.
• Microsoft Copilot is Microsoft’s own product. Its model connection cannot be redirected to AI Reserve.
• The Microsoft 365 connector lets Claude access Outlook, SharePoint, OneDrive, and Teams. It does not install Claude inside Office.

​

Anthropic’s Claude for Microsoft 365 add-in

​

Deploy the default organization-credential manifest

​

What the default manifest configures

• gateway_url=https://api.aireserve.com (or the configured gateway for your environment)
• gateway_api_format=anthropic
• gateway_token=<dedicated-organization-key> in the task-pane URL’s # fragment, not its query string
• gateway_auth_header=authorization
• auto_connect=1
• an Office client marker for usage attribution

​

Optional legacy Entra identity setup

​

Platform setup: Entra application metadata

• Copy Application (client) ID from Overview, not Object ID or Directory (tenant) ID.
• Under Expose an API, set the Application ID URI to api://<application-id> and add the admin-consent-enabled delegated scope access_as_user.
• Configure the resource API to issue v2 access tokens (api.requestedAccessTokenVersion: 2 in the Microsoft Graph-format application manifest).
• Under API permissions, add that exposed scope as a delegated permission.
• Under Authentication → Single-page application, register brk-multihub://pivot.claude.ai and https://pivot.claude.ai/msal-redirect.html.
• Register the admin-consent return URL ${APP_URL}/connect/microsoft-office under Web, matching the web service’s deployed APP_URL exactly. Production deploys use https://portal.aireserve.com/connect/microsoft-office. UAT requires its own exact portal return URL.
• To enable Connect with Microsoft (the one-click admin sign-in that derives and verifies the tenant), register ${APP_URL}/api/office/signin/callback for each environment under Mobile and desktop applications, and turn on Allow public client flows under Authentication → Advanced settings. The flow is a secretless server-side authorization-code + PKCE exchange, so a Web redirect (which expects a client secret) or an SPA redirect (cross-origin only) will be rejected by Microsoft. Then set OFFICE_ENTRA_SIGNIN_ENABLED=true in that environment’s deploy-config/<environment>.env. The sign-in targets the /organizations endpoint, so only workforce (Entra) tenants — not personal Microsoft accounts — can complete it. Leave the flag unset to keep manual entry.

OFFICE_ENTRA_CLIENT_ID=<application-id-guid>
OFFICE_ENTRA_AUDIENCE=<application-id-guid>
OFFICE_ENTRA_REQUIRED_SCOPE=access_as_user

​

Legacy Entra pilot acceptance

• The configured web and gateway revisions are serving traffic in the same environment.
• The pilot tenant is ownership-verified and the employee has an active AI Reserve account in that organization, with a matching Microsoft sign-in email and usable balance.
• Microsoft 365 licenses or a trial provide the Office hosts; an Azure/Entra account alone does not license Excel, Word, or PowerPoint.
• Real Microsoft sign-in yields bootstrap 200 and a non-empty allowed model list.
• A synthetic workbook edit succeeds; repeat with a document and presentation before advertising all three hosts. Verify the resulting employee, organization, and cost attribution.
• Token renewal works and blocked models/integrations or exhausted spending allowances fail as intended.
• AI Reserve MCP, if enabled for the pilot, authorizes separately through OAuth.

​

Manage legacy tenant connections

​

Word and Excel — GPT for Work add-ins

• Bulk models (Excel and Word) — the Chat Completions path, used by bulk prompting and the spreadsheet functions. Add an OpenAI-compatible endpoint (Chat Completions API) with:
  • Endpoint URL: https://api.aireserve.com — host root, no /v1 (unlike most tools in these guides: GPT for Work appends the /v1/models and /v1/chat/completions resource paths itself, so a /v1 suffix here would double up).
  • API key: your aireserve_api_… key.
  • Display name (optional): e.g. AI Reserve — prefixed to model names in the model switcher (custom/ by default).
  Click Check — the add-in validates the connection — then Save. The switcher then lists the gateway’s full catalog under Connected models (/v1/models is the discovery call — it excludes client-exclusive models but does include consent-gated ones, so a model your org hasn’t opted into will list here and refuse at call time with the reason).
• Agent models (Excel only) — the agent sidebar, which drives the workbook. Add an OpenAI-compatible endpoint (Responses API) with the same Endpoint URL and key, plus a model ID copied from the gateway catalog. GPT for Work requires the endpoint to serve /v1/responses over public HTTPS and the model to have at least a 32K-token context — the gateway serves the Responses format for every model, and the flagship models all clear the context bar.

​

Excel — Office Scripts

interface ChatCompletion {
  choices: { message: { content: string } }[];
}

async function main(workbook: ExcelScript.Workbook) {
  const sheet = workbook.getActiveWorksheet();
  const prompt = String(sheet.getRange("A1").getValue());

  const response = await fetch("https://api.aireserve.com/v1/chat/completions", {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      Authorization: "Bearer aireserve_api_...", // your key
    },
    body: JSON.stringify({
      model: "gpt-5.4-mini",
      messages: [{ role: "user", content: prompt }],
    }),
  });

  if (!response.ok) {
    // 401/403/429/402 return an OpenAI error body — surface it instead of
    // failing later on a missing field.
    throw new Error(`Gateway error ${response.status}: ${await response.text()}`);
  }

  const completion: ChatCompletion = (await response.json()) as ChatCompletion;
  sheet.getRange("B1").setValue(completion.choices[0].message.content);
}

​

Power Automate

​

Microsoft 365 connector — separate from the add-in

​

Microsoft Copilot — the boundary