For the firm owner

Proxara Connect asks little of the firm owner. Four steps, then one decision. The Microsoft side belongs to whoever administers Microsoft 365, and every employee connects themselves on first use.

One prerequisite sits ahead of all of it. 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.

The four steps

1. Sign in to the console. Console access for the people named during onboarding is created inside the firm's own environment as part of setup, so there is no invitation email to wait for.
2. Start the Microsoft 365 connection. The console's Connect panel carries three owner-only controls: set the connection up, reconnect it, turn it off. Starting it produces the Microsoft approval link.
3. Send that link to whoever administers Microsoft 365. One approval covers the whole firm. If it expires before anyone opens it, the same panel issues a replacement, which works once and lasts ten minutes. The Entra consent is written to be handed straight to that administrator.
4. Paste the connector address into Claude. Onboarding provisions one thing: the firm's connector address, a single web address ending in /mcp. Claude registers itself the first time it connects, so there is no client ID, secret or token for anyone to copy or store.

Approval alone switches nothing on. The connection goes live only once the first employee has signed in with their own Microsoft account and one real calendar read has succeeded on that account.

Who gets it

How widely the connector appears inside Claude is decided in Claude's own admin settings. Proxara has no concept of a Claude workspace or a group. It recognises individual people, by their Microsoft account.

Making the connector available to someone grants nothing by itself, and the address is not a secret. Each person still signs in with their own Microsoft account inside the firm's own tenant, and access is refused unless that person is a current employee in the firm's own records. The employee guide covers what they see.

The one decision that follows

Where Claude's own built-in connectors reach the same Microsoft 365 systems, the firm decides whether to leave them switched on.

Proxara governs only what arrives at the firm's own connector address. Whatever the assistant fetches by any other route never passes through Proxara, so it is neither checked against the firm's policy nor written into the firm's record.

That setting belongs to the firm and lives in Claude's admin surface. Proxara cannot flip it, which is why it sits in the firm's own runbook rather than in Proxara's.

Not covered here

The Microsoft side, a single tenant-wide approval granted by an administrator, is The Entra consent.

Ending access is Offboarding and revocation. Worth knowing in advance: the console's turn-off control acts on the whole firm at once, and Proxara has no per-person switch.

A connector governs what the assistant fetches from the firm's systems. Anything a person types directly into the chat is visible to the assistant, and a connector does not change that. Connect or Endpoint sets out what each product covers.