Proxara in Microsoft Teams
IT uploads one small package. The console appears inside Teams.
Updated August 2026
For IT, about five minutes, once. You need one thing: the Proxara Teams package, a small ZIP Proxara hands the firm at onboarding. Uploading it puts the console inside Teams for the people the firm chooses.
Teams does not host the app. The console stays in the firm’s environment, and Teams reaches it over HTTPS.
What the ZIP is
A manifest and the app's two icons, nothing else. Teams does not host the app: the console keeps running in the firm's environment, and Teams reaches it over HTTPS. Proxara builds the package pointed at the firm's own console address before handing it over, so there is nothing to configure inside it.
Step 1. Upload it
In the Teams admin center, open Teams apps, then Manage apps, then Upload new app. On some tenants the same button sits under Actions. Pick the ZIP.
Manage apps
An app an admin uploads joins the firm's own catalog with no further approval step, and Microsoft notes it can take a few hours to reach everyone.
Step 2. There is no step 2
Who sees it is governed on the same Manage apps page, by the app settings and policies the firm already uses for every other Teams app.
You're in Teams
People find Proxara in the Built for your org section of the Teams app store and pin it. It opens the console under the same Microsoft work sign-in as everywhere else, and a Teams notification about a piece of work links back to the private view, carrying no client content itself.
If something doesn't work
- No Upload new app button? Custom apps may be switched off in the org-wide app settings, or the account lacks a Teams admin role.
- Uploaded, but nobody sees it yet? Microsoft allows a few hours. Then check who it is available to, on Manage apps.
- It opens but asks for a sign-in? That is the same Microsoft work sign-in used everywhere else, not a new account.
Copilot, and the one admin family
Microsoft now manages apps and agents that work across Teams, Outlook, and Microsoft 365 Copilot from either the Teams admin center or the Microsoft 365 admin center, and availability stays consistent wherever the change is made.
The Copilot agent is its own, separate upload with its own page: Proxara in Microsoft Copilot. The Microsoft-side controls for agents live in the Microsoft 365 admin center, under Agents, then Settings:
Agent settings
Manage everything related to Agents. These settings include controls for data access, user permissions, integration policies, and customization of agent behavior to align with enterprise standards.
Proxara's own rules for what an agent may do sit with the firm in the console, whichever host it runs in: Running agents across the firm.
Where to go next
| To do this | Read |
|---|---|
| Deploy the Copilot agent | Proxara in Microsoft Copilot |
| See where this sits in the whole rollout | What happens when you deploy |
| First requests that work on day one | What to ask for |