Proxaradocs
Guides/Proxara Connect

Connect quickstart

The shortest real path to Proxara Connect: one admin consent, the connector added in Claude, and the first brief. Nothing installs.

Updated July 2026

The shortest real path to Proxara Connect. Three steps: one consent, one connector address, and everyone signs in from inside Claude. Nothing installs on any device, and no device management is involved.

ClaudeProxara
Use Proxara to prepare me for this afternoon’s client review.
proxara_microsoft_prepare_briefreading the workspace
Outlook mail and calendar, Teams, OneDrive and SharePoint files, and tasks
The first employeeAsks for something real.
Signs in with their own Microsoft account.
Inside the firm’s own Microsoft tenant
A current employee in the firm’s own records
The full approved permission set
One live calendar read. The result is discarded.
The sign-in is what makes it live. Not the approval before it.
A real sign-in proves the connection
One consent, one paste, one sign-in, and the first brief

Before starting

Onboarding provisions two things for the firm: a dedicated, single-tenant environment of its own, and the firm's connector address for Claude. Adding a connector for a whole organization is a Claude administrator action; if the firm is unsure whether its Claude plan supports that, the Claude admin settings page answers it directly.

A firm evaluating first runs this exact path under the evaluation. The setup is the same either way.

A Microsoft tenant administrator opens the consent link Proxara provides and approves the Proxara Connect application once, for the tenant. Every permission requested is delegated and read-only, and every read Proxara makes carries the signed-in employee's own credential and nothing else.

For the Microsoft administrator shows what the screen says and what it never asks for. Proxara Connect for IT is the one-page version to hand whoever approves it.

Step 2: the connector

A Claude administrator adds the firm's connector address in Claude's admin settings. It is a single web address ending in /mcp, and Claude registers itself the first time it connects, so there is no client ID, secret, or token for anyone to copy or store.

For the firm owner covers that step, and the decision that follows it about Claude's own built-in connectors.

Step 3: everyone connects

Each employee's first request that touches the firm's systems asks them to sign in with their own Microsoft account, the same sign-in the firm already uses, multi-factor included. From then on their requests run under their own identity, and a connection lasts thirty days before it is made again.

The consent does not switch anything on by itself. The connection goes live once the first employee has signed in and one real calendar read has succeeded on that account. That is the whole rollout, and what employees do is the page to circulate.

Confirm it works

Ask Claude for something real: "Prepare me for my next client meeting." The brief comes back with stand-ins in the model's text and the real records in the Proxara view inside the conversation. In the console, Activity shows the plain-language record: which sources the brief drew on, and how many client details were replaced before the model.

Where to go next

To understandRead
What Proxara Connect isWhat Proxara Connect is
What the model receives, and never receivesWhat the model sees
How an action is proposed and approvedHow actions work
How access ends, on either sideEnding access
When something stops workingTroubleshooting
The review path for the security ownerThe Connect security review