Troubleshooting

Most Connect issues have one of a few causes, and most resolve with a reconnect. This page lists the states an employee or an administrator will meet, and the fix.

"Reconnect Proxara" keeps appearing

A person's connection lasts thirty days and then has to be made again, used or not. It also ends whenever Microsoft refuses to renew the stored credential: a changed password, a sign-in policy the firm enforces, or an administrator action. The fix is the sign-in itself, one step.

If the sign-in will not complete, the firm's connection is usually off or waiting on a fresh administrator approval. Only a firm owner can restore it, from the console.

A source shows unavailable

When mail, Teams, files, or tasks cannot be reached, work that needs that source says so rather than answering from a partial picture. The usual causes, in order:

1. The permission behind that source was not granted, so the read is reported unavailable rather than attempted. The granted list is under Enterprise applications.
2. The person's credential needs a reconnect.
3. Microsoft answered slowly or with a temporary error. Those are treated as temporary, and nobody's access is withdrawn for them.

A source can also come back partial rather than unavailable: a brief has ceilings on how much it may read, and passing one marks that source partial with a named reason.

The connector is missing in Claude

If employees do not see the firm's systems in Claude at all, the cause is on Claude's side: the connector was removed or disabled in Claude's admin settings, or never added for that person. Proxara has no workspace or group concept of its own and cannot change what Claude displays. Whether the firm's Claude plan supports an organization-wide custom connector is settled in Claude's own admin settings, which is also where it is confirmed.

A request is refused

That is not a fault. Under firm policy some classes of information do not go out in any form, and the request stops rather than going out reduced.

A request also stops when no single meeting matches what was described, or when a real name would still have been visible in what the model was about to receive. The outcome and its reason reach the firm's signed record either way.

Everything is refused

If every request for every person is refused, the cause is firm-level: consent revoked in Entra, or the connector turned off in the console.

They behave differently. Turning the connector off takes effect immediately. A revocation in Entra is not observed by Proxara, so the console keeps showing the connection as live until the next use fails. Ending access covers both.

Where to look

The console's activity surface shows each request's outcome, which sources it reached and with what status, and how many records each contributed. It does not show what was asked or what was read. Every row is re-checked against its signature before display, and one that fails is reported as unavailable.

For anything this page does not resolve: support@proxara.ai.