Hello @Harsh Bhavsar
Since this connection used to work but started failing around September 7, first determine which GitHub connection type is failing before taking further action.
If this is an Azure Pipelines connection, go to:
Azure DevOps > Project settings > Service connections
Check the GitHub connection to see whether it uses the Azure Pipelines GitHub App, OAuth, or a Personal Access Token (PAT); Microsoft provides different troubleshooting procedures based on the authentication type.
When setting up a connection with a GitHub App, you should go to the GitHub organization under Settings > GitHub Apps/Installed GitHub Apps and verify that Azure Pipelines is still installed and authorized for the repository in question. If repository access has changed, the app may still be installed but will no longer have access to that specific repository.
When using OAuth or a Personal Access Token, verify that the authorization/token is still valid and has the required repository permissions. Microsoft states that GitHub connections based on a Personal Access Token need the relevant scopes, such as repo, user, and admin:repo_hook, depending on the situation.
Also check the affected GitHub repository under:
Settings > Webhooks
For Azure Pipelines integrations that use OAuth or a PAT, verify that the expected webhooks are still there and check Recent Deliveries for any failed requests, since a failed delivery will include the HTTP response or error that the Azure DevOps UI isn't showing.
It's important to clarify one term: you've referred to GitHub Enterprise Cloud. Could you confirm whether this is the standard GitHub Enterprise Cloud available on github.com or an Enterprise Cloud organization using a dedicated *.ghe.com environment? Don't use the connection instructions for Azure DevOps GitHub Enterprise Server unless you actually have GitHub Enterprise Server; that requires a different integration.
Since the failure is said to have begun on a particular date, also check the Azure DevOps and GitHub service status/history pages to identify the exact time period when the failure occurred. However, don't conclude this is a Microsoft-side outage unless you see an error message or evidence of a service incident.
Could you provide:
- whether this is an Azure Pipelines or Azure Boards GitHub connection
- the connection/authentication type (GitHub App, OAuth, or PAT)
- the exact error message displayed when the connection fails
- whether the Azure Pipelines GitHub App still has access to the affected repository
- whether this affects all repositories or only one
- When using OAuth or a Personal Access Token, does GitHub's webhook display an HTTP error in its Recent Deliveries?
Please remove the organization and repository names, as well as the tokens and any other identifying information.
With those details, we can distinguish between an expired or revoked authorization, a change to the GitHub App's access to a repository, a webhook problem, and a service-side issue.
References:
Build GitHub repositories with Azure Pipelines - Troubleshooting GitHub integration
Manage Azure DevOps service connections
Connect Azure Boards/Azure DevOps to GitHub
=============================================================================
Help make this community better for everyone: if the answer below assisted you/resolved your issue, please accept it or upvote it. This helps others in the community find similar solutions.