Microsoft 365 Copilot previously accessed my GitHub repository but can no longer access it #213315
Replies: 2 comments
|
Start with the GitHub-side authorisations: go to https://github.com/settings/applications and check whether the Microsoft 365 Copilot / GitHub connector is still listed, then re-authorise it. Also check your org's Settings → Applications → Installed GitHub Apps and any OAuth app allowlist, since an admin change there would revoke access without touching your repo. If it was connected through the M365 admin center, the connection may need to be re-approved there too. Entra token lifetime or consent expiry is a common cause when nothing changed on the GitHub side. Happy to connect at https://github.com/P-r-e-m-i-u-m. |
|
One detail in your description stands out: Copilot is reportedly unable to discover the GitHub retrieval capability itself, rather than returning an authentication or repository permission error. That distinction could help narrow down the investigation. I'd approach this in three layers:
One useful diagnostic experiment would be to test the same repository integration with another supported Microsoft 365 Copilot account, if available. This could help distinguish an account-specific configuration issue from a broader integration problem. My main suspicion would be somewhere in the connector discovery or integration configuration layer, rather than the repository itself. However, without request logs from both sides, it's difficult to establish exactly where the failure occurs. It would be particularly useful if Microsoft could confirm whether the GitHub connector is being exposed to your Copilot session at all, and whether any requests are subsequently reaching GitHub. That would give you a much clearer starting point than repeatedly reconnecting the integration. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
Body
Hi,
I'm trying to diagnose a problem between Microsoft 365 Copilot and GitHub and would appreciate help determining what I can check from the GitHub side.
What previously worked
Microsoft 365 Copilot previously had direct access to my GitHub repositories. I regularly used Copilot to retrieve and review current files from that repository.
This subsequently stopped working without any intentional change to the repository or its access settings on my part.
Current behaviour
When I ask Microsoft 365 Copilot to retrieve a known file or simply list the contents of the repository, it can no longer access it.
The significant diagnostic detail is that this does not appear to be a normal repository access-denied error.
During repeated testing, Microsoft 365 Copilot reports that its connector/tool discovery does not expose a GitHub repository retrieval capability at all. The apparent failure therefore occurs before Copilot can attempt the repository operation.
I have:
The problem persists.
Support history
I opened a support case with Microsoft. Microsoft Support directed me to GitHub Support.
I then opened GitHub Support ticket #5015854. GitHub Support explained that the support resources available to my account are GitHub Community Discussions, GitHub Docs and GitHub Skills, and closed the ticket without investigating the technical issue.
So I'm bringing the question here as suggested.
What I'm trying to establish
I'm not assuming that this is a GitHub fault. I'm trying to establish where the failure occurs.
Is there anything I can inspect from the GitHub side to determine:
I'm particularly interested in diagnostic steps that can establish whether requests are actually reaching GitHub, rather than simply trying another disconnect/reconnect.
If I can establish that the GitHub side is healthy, that would also be useful evidence to take back to Microsoft Support.
Thanks, Bruce
All reactions