Unable to connect to Github Account using Github connections from ADO

Hi @Krishna P G ,

Thank you for reaching out to Microsoft Q & A!

@Allan Solomon Mejia has covered the main repository-permission and application-access checks.

For the Project Settings → GitHub connections connection flow, please verify the following:

1. Verify the GitHub account used for authorization

The GitHub account used to create the connection should have the required administrator access to the repository you want to connect. Confirm that you are authenticating with the intended GitHub account and organization.

1. Verify the GitHub organization and repository access

Since the GitHub organization is visible but the repository isn't available for selection, have the GitHub organization owner verify that the Azure Boards/GitHub integration is approved for the organization and that the required repository is included in the application's repository access.

1. Check the existing GitHub connection in Azure DevOps

In Azure DevOps → Project Settings → GitHub connections, review the existing connection before removing or recreating it. If the repository is already included in the connection, it won't be available as another repository to add.

1. If you're using a PAT and the GitHub organization uses SAML SSO

Verify that the PAT is authorized for SSO before using it to access repositories in that organization.

After correcting any permission or organization-access issue, retry adding the repository, save the connection, and confirm that the repository appears under Project Settings → GitHub connections.

Microsoft documentation:

Connect an Azure Boards or Azure DevOps project to a GitHub repository

If the repository still doesn't appear, please let us know whether you're authenticating with GitHub credentials or a PAT, and whether the repository is already displayed under an existing GitHub connection.

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

Hi @Krishna P G

Since Azure DevOps already displays your GitHub organization, the GitHub connection is at least partially working. The message "You've already added all the repositories you have permission to" usually means Azure DevOps cannot see any additional repositories that the current GitHub authorization/app installation is permitted to access.

Check the GitHub side first.

If you're using the Azure DevOps/Azure Boards GitHub App, ask a GitHub organization owner to open the organization's Settings → GitHub Apps / Installed GitHub Apps, select the relevant Azure DevOps app, and check its Repository access. GitHub Apps can be installed for either all repositories or only selected repositories, and an organization owner can modify which repositories the app can access.

Make sure the repository you're trying to connect is included there.

Also, verify that your GitHub account itself has sufficient access to that repository. This is important because granting an integration access doesn't automatically grant the signed-in user additional repository permissions. For Azure Boards connections, the account creating the connection needs administrator access to the repositories being connected so Azure DevOps can manage the required webhooks.

If you're configuring this for Azure Pipelines, insufficient GitHub permissions can prevent the repository from appearing in the repository selection list.

Another thing to check is whether that GitHub repository is already connected to another Azure DevOps organization/project. GitHub App mappings have restrictions, so it is best to check the existing connection when a repository doesn't behave as expected.

So check, in this order:

1. GitHub organization → installed Azure DevOps/Azure Boards/Azure Pipelines app → confirm the repository is included.
2. GitHub repository → Settings → Collaborators and teams → confirm your GitHub account has the required access.
3. Azure DevOps → Project Settings → GitHub connections → check whether the repository is already connected.
4. If your organization uses GitHub app restrictions or requires organization-owner approval, have the GitHub organization owner verify/approve the integration. GitHub organizations can restrict app installations and access requests.

Don't create a PAT as the first workaround. Use more secure authentication mechanisms where possible, and the existing GitHub App connection should work once the repository and user permissions are correct.

If it still doesn't appear, could you confirm whether you're connecting it for Azure Boards or Azure Pipelines, whether the repository is private or public, and whether the GitHub App is configured for All repositories or Only select repositories? Those details should narrow down exactly where the permission is missing.

References:

Connect Azure Boards/Azure DevOps to GitHub repositories

Build GitHub repositories with Azure Pipelines

GitHub - Review GitHub Apps installed in an organization

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.