IT deploys it once. It appears in Copilot on its own.
Updated August 2026
If your firm uses Copilot, there is nothing to set up. Proxara is already in Copilot's agent list, under the Microsoft work sign-in you use there. Nothing installs, and there is no second account.
Proxara arrives as one ZIP holding the manifest files and icons. The working logic stays hosted by Proxara and is reached over HTTPS, so the firm runs nothing inside Microsoft and patches nothing later.
In the Microsoft 365 admin center, inside the Copilot Control System:
Deploying installs the agent on behalf of the people selected, accepting its Microsoft Entra permissions for them: no invitation to forward, no setup note to write. From the same page, admins can pin it high in the list, narrow who has it, remove it, or block it, at any time.
Access follows Microsoft Entra. Remove a person there and their access ends in Copilot and in every other assistant at the same time.
Agents in full call for Microsoft 365 Copilot licences; Microsoft 365 Copilot Chat, included with Microsoft 365, has more limited agent capabilities.
The one Microsoft consent behind every sign-in: Connect Microsoft 365.
Open Proxara Connect and ask about work in progress:
More first requests: What to ask for.
Copilot's answers carry stand-ins in place of client names, never client figures. Real names live in the private view, which opens under your own sign-in.
Anything you type into Copilot is Microsoft's to retain, like any Copilot conversation. That is why the clear material stays in the private view.
Ask where one of your engagements stands. A right answer that uses a stand-in for the client name means it is working.
| To understand | Read |
|---|---|
| Where real names live, and what the model sees | How Proxara works |
| The same environment in other assistants | Claude, ChatGPT, Gemini |