The states you will meet, and the fix for each.
Updated August 2026
Most Connect issues have one of a few causes, and most resolve with a reconnect.
A grant has an explicit lifetime and is made again when it ends, used or not. It also ends whenever Microsoft refuses to renew the stored credential: a changed password, a sign-in policy, an administrator action. The fix is the sign-in itself.
If it will not complete, the firm's connection is off or waiting on approval, which only a firm owner restores.
A blocked source never produces a quiet success. The work returns what is known, names the missing source, and resumes when authority returns. The usual causes, in order:
The cause is on the assistant's side: removed or disabled in its admin settings, or never made available to that person. The setting lives there, not in Proxara: Claude, ChatGPT, Microsoft Copilot, Gemini.
Not a fault. Under firm policy some classes of information do not leave in any form, and a request also stops when its purpose is not one the firm authorized, or when part of the payload could not be accounted for.
The outcome is named: clarification required, confirmation required, blocked, or completed with the omissions listed, and it reaches the firm's record.
The cause is firm-level, and the two differ. The console's off switch is immediate; a consent revoked in Entra is not observed by Proxara, so the console shows the connection live until the next use fails. Ending access covers both, and Connect Microsoft 365 covers the consent.
The console's activity surface shows each request's outcome, the sources it reached, and how many records each contributed, never what was asked or read. Anything unresolved: support@proxara.ai.