Azure DevOps Pipeline Not Triggering for GitHub Pull Request Events Despite Successful Webhook Delivery

Question

Azure DevOps Pipeline Not Triggering for GitHub Pull Request Events Despite Successful Webhook Delivery

Anonymous

An issue is being encountered where pull request (PR) events from a GitHub Enterprise Cloud repository (with data residency in Europe) are not triggering the Azure DevOps pipeline, even though webhook events are successfully delivered with a 200 OK response.

Pipeline Type: YAML-based

Service Connection Used: GitHub Enterprise Server (configured with classic PAT)
PAT Scopes: repo, admin:repo_hook, read:org, workflow
Pipeline Binding: Created using the “New Pipeline” wizard with GitHub Enterprise Server selection and repository integration
Pipeline Permissions: No restrictions; service connection authorized and public key scopes verified

Trigger Settings:

YAML includes:

        trigger:
       branches:
         include:
           - partcopy

     pr:
       branches:
         include:
           - partcopy

Pull request validation is also enabled in the pipeline UI.

Anonymous

2025-06-27T09:44:49.6166667+00:00
Thank you for your guidance.

I tried creating the service connection using the GitHub option (not GitHub Enterprise Server), as suggested. However, I’m encountering the following error when Azure DevOps tries to query the service connection API:

Failed to query service connection API: 'https://api.github.com/user/repos'. Status Code: 'Unauthorized', Response from server: '{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest","status":"401"}'

I have ensured the following:

A classic PAT token was used (not a fine-grained token), with the required scopes: repo, workflow, user, and admin:repo_hook

The token is SSO authorized for my organization

My GitHub instance URL ends withghe.com, confirming this is a GitHub Enterprise Cloud tenant with data residency URL : https://<company name>.ghe.com

Does Azure DevOps support GitHub Enterprise Cloud tenants with custom domains under the "GitHub" connection type?

Appreciate your help on this.
Anonymous

2025-06-27T09:45:06.8666667+00:00
Thank you for your guidance.

I tried creating the service connection using the GitHub option (not GitHub Enterprise Server), as suggested. However, I’m encountering the following error when Azure DevOps tries to query the service connection API:

YAMLCopy

Failed to query service connection API: 'https://api.github.com/user/repos'. Status Code: 'Unauthorized', Response from server: '{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest","status":"401"}'

I have ensured the following:

A classic PAT token was used (not a fine-grained token), with the required scopes: repo, workflow, user, and admin:repo_hook

The token is SSO authorized for my organization

My GitHub instance URL ends withghe.com, confirming this is a GitHub Enterprise Cloud tenant with data residency URL : https://<company name>.ghe.com

Does Azure DevOps support GitHub Enterprise Cloud tenants with custom domains under the "GitHub" connection type?

Appreciate your help on this.
Anonymous

2025-06-27T13:05:24.64+00:00
Thanks for the detailed explanation.

To confirm, I have already created the service connection using the GitHub Enterprise Server option with the custom domain https://<company>.ghe.com. The classic PAT being used:

Is SSO-authorized

Has no organizational restrictions

Has not expired or been revoked

Includes all the required scopes (repo, admin:repo_hook, workflow, read:org, user)

Is authorized for all pipelines

The service connection is fully set up and accessible from Azure DevOps, with no permission issues. Additionally:

The repository is correctly populated from the service connection in the pipeline setup

The YAML file is correctly selected and configured in the pipeline settings

Now, returning to the root issue:

The webhook for both push and pull_request is created in GitHub and returns 200 OK

CI triggers (push events) are working as expected

However, the PR trigger is not firing the pipeline

On further debugging, I observed that the PR webhook response body is:
{"count":0,"value":[]}

The YAML file contains the correct pr trigger configuration

I have also tried overriding the PR trigger from the Azure DevOps pipeline UI under the Triggers section, but the pipeline still does not run for PR events
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-06-27T13:58:25.7733333+00:00
Hi Manoj Rajkumar Chopkar

The "count":0,"value":[] response in the webhook response indicates that Azure DevOps received the PR webhook event but couldn’t associate it with any pipeline subscription.

Make sure your PRs are created from partcopy into the default or target branch (usually main or master).
pr: branches: include: - partcopy

Add source branch filtering to YAML explicitly:
pr: branches: include: - partcopy paths: include: - '*'

Azure DevOps does not trigger PR pipelines for forked repositories due to security concerns.

If the PR is from a fork:

You must manually run the pipeline

Or move the branch into the base repository

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-06-30T08:26:55.84+00:00

Hi Manoj Rajkumar Chopkar

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-01T08:18:07.6666667+00:00

Hi Manoj Rajkumar Chopkar

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Anonymous

2025-07-01T15:36:34.8333333+00:00

The issue still persists despite trying all the solutions mentioned in the comment
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-02T08:58:26.39+00:00
Hi Manoj Rajkumar Chopkar

Thanks for confirming.

Sometimes, the pipeline trigger subscription gets desync from the GitHub repo metadata. To reset this:

Temporarily disable the pr: block in your YAML

Commit & push the change

Re-enable the pr: block and push again

This forces Azure DevOps to rebuild the event subscription.

Try temporarily using:

pr: branches: include: - '*'

In GitHub, go to Organization Settings -> Third-party access -> Authorized OAuth Apps -> Confirm Azure DevOps is authorized.

Recreate pipeline with these steps:

Go to Pipelines -> New pipeline -> Choose: GitHub Enterprise Server -> Select the correct repo from list -> Choose the YAML file -> Save.

This rebinds the pipeline to the GitHub repo properly.

If possible, please share the YAML File in private message.

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-03T07:59:04.5266667+00:00

Hi Manoj Rajkumar Chopkar

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-04T08:21:23.72+00:00

Hi Manoj Rajkumar Chopkar

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Anonymous

2025-07-07T06:48:33.1633333+00:00

The issue still persists despite trying all the solutions mentioned in the comment
Anonymous

2025-07-07T06:49:31.82+00:00

@Durga Reshma Malthi I want to enable PR validation for specific branch adding * will work for all the branches
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-07T09:09:04.9066667+00:00

Hi Manoj Rajkumar Chopkar

Please let me know if this has been worked.

If you are still facing the issue, please raise support ticket in Azure Portal or you can report problem in developer community - https://developercommunity.visualstudio.com/AzureDevOps
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-08T08:28:05.14+00:00

Hi Manoj Rajkumar Chopkar

Please let me know if the above workaround has been worked.

If you are still facing the issue, please raise support ticket in Azure Portal or you can report problem in developer community - https://developercommunity.visualstudio.com/AzureDevOps
kb21692 5 Reputation points

2025-07-22T08:40:06.77+00:00

Were you able to resolve this issue ? @Anonymous
Marcel Wijnands 0 Reputation points

2026-03-05T22:27:29.7233333+00:00

I got the same issue... cost me so many hours just to find out it does not work. Works perfectly in github, but not in github enterprise.

2 answers

Your answer

Anonymous

2025-06-27T09:44:49.6166667+00:00

Thank you for your guidance.

I tried creating the service connection using the GitHub option (not GitHub Enterprise Server), as suggested. However, I’m encountering the following error when Azure DevOps tries to query the service connection API:

Failed to query service connection API: 'https://api.github.com/user/repos'. Status Code: 'Unauthorized', Response from server: '{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest","status":"401"}'

I have ensured the following:

A classic PAT token was used (not a fine-grained token), with the required scopes: repo, workflow, user, and admin:repo_hook

The token is SSO authorized for my organization

My GitHub instance URL ends withghe.com, confirming this is a GitHub Enterprise Cloud tenant with data residency URL : https://<company name>.ghe.com

Does Azure DevOps support GitHub Enterprise Cloud tenants with custom domains under the "GitHub" connection type?

Appreciate your help on this.
Anonymous

2025-06-27T09:45:06.8666667+00:00

Thank you for your guidance.

I tried creating the service connection using the GitHub option (not GitHub Enterprise Server), as suggested. However, I’m encountering the following error when Azure DevOps tries to query the service connection API:

YAMLCopy

Failed to query service connection API: 'https://api.github.com/user/repos'. Status Code: 'Unauthorized', Response from server: '{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest","status":"401"}'

I have ensured the following:

A classic PAT token was used (not a fine-grained token), with the required scopes: repo, workflow, user, and admin:repo_hook

The token is SSO authorized for my organization

My GitHub instance URL ends withghe.com, confirming this is a GitHub Enterprise Cloud tenant with data residency URL : https://<company name>.ghe.com

Does Azure DevOps support GitHub Enterprise Cloud tenants with custom domains under the "GitHub" connection type?

Appreciate your help on this.
Anonymous

2025-06-27T13:05:24.64+00:00

Thanks for the detailed explanation.

To confirm, I have already created the service connection using the GitHub Enterprise Server option with the custom domain https://<company>.ghe.com. The classic PAT being used:

Is SSO-authorized

Has no organizational restrictions

Has not expired or been revoked

Includes all the required scopes (repo, admin:repo_hook, workflow, read:org, user)

Is authorized for all pipelines

The service connection is fully set up and accessible from Azure DevOps, with no permission issues. Additionally:

The repository is correctly populated from the service connection in the pipeline setup

The YAML file is correctly selected and configured in the pipeline settings

Now, returning to the root issue:

The webhook for both push and pull_request is created in GitHub and returns 200 OK

CI triggers (push events) are working as expected

However, the PR trigger is not firing the pipeline

On further debugging, I observed that the PR webhook response body is:
{"count":0,"value":[]}

The YAML file contains the correct pr trigger configuration

I have also tried overriding the PR trigger from the Azure DevOps pipeline UI under the Triggers section, but the pipeline still does not run for PR events
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-06-27T13:58:25.7733333+00:00

Hi Manoj Rajkumar Chopkar

The "count":0,"value":[] response in the webhook response indicates that Azure DevOps received the PR webhook event but couldn’t associate it with any pipeline subscription.

Make sure your PRs are created from partcopy into the default or target branch (usually main or master).
pr: branches: include: - partcopy

Add source branch filtering to YAML explicitly:
pr: branches: include: - partcopy paths: include: - '*'

Azure DevOps does not trigger PR pipelines for forked repositories due to security concerns.

If the PR is from a fork:

You must manually run the pipeline

Or move the branch into the base repository

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-06-30T08:26:55.84+00:00

Hi Manoj Rajkumar Chopkar

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-01T08:18:07.6666667+00:00

Hi Manoj Rajkumar Chopkar

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Anonymous

2025-07-01T15:36:34.8333333+00:00

The issue still persists despite trying all the solutions mentioned in the comment
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-02T08:58:26.39+00:00

Hi Manoj Rajkumar Chopkar

Thanks for confirming.

Sometimes, the pipeline trigger subscription gets desync from the GitHub repo metadata. To reset this:

Temporarily disable the pr: block in your YAML

Commit & push the change

Re-enable the pr: block and push again

This forces Azure DevOps to rebuild the event subscription.

Try temporarily using:

pr: branches: include: - '*'

In GitHub, go to Organization Settings -> Third-party access -> Authorized OAuth Apps -> Confirm Azure DevOps is authorized.

Recreate pipeline with these steps:

Go to Pipelines -> New pipeline -> Choose: GitHub Enterprise Server -> Select the correct repo from list -> Choose the YAML file -> Save.

This rebinds the pipeline to the GitHub repo properly.

If possible, please share the YAML File in private message.

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-03T07:59:04.5266667+00:00

Hi Manoj Rajkumar Chopkar

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-04T08:21:23.72+00:00

Hi Manoj Rajkumar Chopkar

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Anonymous

2025-07-07T06:48:33.1633333+00:00

The issue still persists despite trying all the solutions mentioned in the comment
Anonymous

2025-07-07T06:49:31.82+00:00

@Durga Reshma Malthi I want to enable PR validation for specific branch adding * will work for all the branches
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-07T09:09:04.9066667+00:00

Hi Manoj Rajkumar Chopkar

Please let me know if this has been worked.

If you are still facing the issue, please raise support ticket in Azure Portal or you can report problem in developer community - https://developercommunity.visualstudio.com/AzureDevOps
Durga Reshma Malthi 11,600 Reputation points Microsoft External Staff Moderator

2025-07-08T08:28:05.14+00:00

Hi Manoj Rajkumar Chopkar

Please let me know if the above workaround has been worked.

If you are still facing the issue, please raise support ticket in Azure Portal or you can report problem in developer community - https://developercommunity.visualstudio.com/AzureDevOps
kb21692 5 Reputation points

2025-07-22T08:40:06.77+00:00

Were you able to resolve this issue ? @Anonymous
Marcel Wijnands 0 Reputation points

2026-03-05T22:27:29.7233333+00:00

I got the same issue... cost me so many hours just to find out it does not work. Works perfectly in github, but not in github enterprise.

Answer 1

Hi Manoj Rajkumar Chopkar

Based on your info provide,

Your GitHub instance is hosted at a URL like https://<company>.ghe.com.
You're using GitHub Enterprise Cloud with custom domain URL (ghe.com).

The GitHub connection type does not support GitHub Cloud tenants with custom domains, even though the backend is GitHub Enterprise Cloud.

So, despite being a GitHub Enterprise Cloud instance, your ghe.com-based tenant requires you to use the GitHub Enterprise Server connection type because of the custom domain.

When creating the service connection:

Select GitHub Enterprise Server
Enter your custom domain: https://<company>.ghe.com
Use a classic PAT with the correct scopes: repo, admin:repo_hook, workflow, read:org, user
Ensure:
- The PAT is SSO-authorized
- Your organization does not restrict PAT usage
- The token has not expired or been revoked

In Azure DevOps:

Go to Project Settings -> Service Connections -> GitHub Enterprise Server connection -> Click Manage roles or Security -> Ensure it is authorized for all pipelines or specifically the target pipeline and approve the key if prompted

In your GitHub repository (hosted at *.ghe.com):

Navigate to Settings > Webhooks and Confirm:
- Azure DevOps webhook is registered
- Events like pull_request, push are enabled

Hope this helps!

Please Let me know if you have any queries.

Answer 2

Hi Manoj Rajkumar Chopkar

You're using GitHub Enterprise Cloud with data residency in Europe, but you've configured the service connection as GitHub Enterprise Server.

Azure DevOps treats GitHub Enterprise Cloud and Server as separate endpoint types. If you selected the "GitHub Enterprise Server" option and provided the GitHub Cloud URL, Azure DevOps might not associate the webhook payload correctly. Try re-creating the service connection using the GitHub or GitHub Enterprise Cloud option (not Server), even if the repo is in a separate region.

Go to Azure DevOps -> Project Settings -> Service Connections -> + New service connection -> Select GitHub (not GitHub Enterprise Server)

Authenticate using a GitHub OAuth or PAT with repo, workflow, admin:repo_hook scopes
Select your GitHub Enterprise Cloud repository (EU-hosted)
Authorize the connection properly

Now Go to your pipeline in Azure DevOps -> Edit the pipeline -> Make sure the pipeline is bound to the repository via the new GitHub service connection and Confirm YAML is in the target repo.

Hope this helps!

Please Let me know if you have any queries.