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

Question

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

kb21692 5

Created a new YAML pipeline with CI/PR triggers on Azure DevOps with repository hosted on Github Enterprise Server. The CI triggers are working as expected however the PR triggers fail to trigger. I can see a successful webhook but the response body is empty as below.

{"count":0,"value":[]}

I have tried to create a Classic pipeline as well as a YAML pipeline but both of them do not work for PR triggers.

Steps followed:

Create a service connection in Azure DevOps for Github Enterprise with the required permissions.
Create a classic pipeline and modify the triggers from UI.
Create a PR request on Github repo and check for webhooks delivery(shows successful status 200 with the correct request body)
No build trigger at Azure DevOps end.

Tried the same with YAML pipeline but using pr clause in pipeline.

Durga Reshma Malthi 11,595 Reputation points Microsoft External Staff Moderator

2025-07-22T13:42:01.12+00:00
Hi kb21692

Could you please check the following things:

Ensure that the service connection you created in Azure DevOps for GitHub Enterprise has the necessary permissions to access the repository. The service connection should have at least read access to the repository and the ability to read pull requests.

In your YAML pipeline, ensure that the PR trigger is correctly configured.
pr: branches: include: - main # or the branch you want to trigger on

Ensure the pipeline is connected to the correct GitHub Enterprise repo via resources.repositories.
resources: repositories: - repository: self type: githubenterprise name: your-org/your-repo

When creating the service connection:

Select GitHub Enterprise Server

Enter your custom domain

Use a classic PAT with the correct scopes: repo, admin:repo_hook, workflow, read:org, user

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:

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.
kb21692 5 Reputation points

2025-07-22T13:58:15.5866667+00:00
Hi @Durga Reshma Malthi

Thanks for your reply. I have answered the questions inline:

Ensure that the service connection you created in Azure DevOps for GitHub Enterprise has the necessary permissions to access the repository. The service connection should have at least read access to the repository and the ability to read pull requests.

A. Service connection has access to all pipelines on the Project in Azure DevOps. I am able to manually run the build pipeline as well as run builds using CI triggers.

In your YAML pipeline, ensure that the PR trigger is correctly configured

A. Below is my snippet of yaml:

pr: branches: include: - "*"

Ensure the pipeline is connected to the correct GitHub Enterprise repo via resources.repositories.

A. Pipeline is connected since CI trigger works.

When creating the service connection:

Select GitHub Enterprise Server

Enter your custom domain

Use a classic PAT with the correct scopes: repo, admin:repo_hook, workflow, read:org, user

A. Have given complete access to the PAT.

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.

A. Have given permission for all pipelines.

In your GitHub repository:

Navigate to Settings > Webhooks and Confirm:

Azure DevOps webhook is registered

Events like pull_request, push are enabled.

A. Can see both events. However for pull_request events can see response code as 200 but the response body is below:

{"count":0,"value":[]}

Regards,

Kunal
Durga Reshma Malthi 11,595 Reputation points Microsoft External Staff Moderator

2025-07-22T16:44:41.2766667+00:00

Hi kb21692

Ensure that the PR’s target branch (e.g., main, develop, etc.) contains the YAML file at the expected path (azure-pipelines.yml).

Also ensure the PR is coming from the same repo.

Try editing and saving the pipeline again from the Azure DevOps UI. Temporarily remove the pr: block from YAML -> Commit and push. Re-add the pr: block and push again. This forces Azure DevOps to re-register the PR trigger.Hope this helps!

Please Let me know if you have any queries.
kb21692 5 Reputation points

2025-07-23T06:47:58.32+00:00

Hi @Durga Reshma Malthi

I tried all the steps you mentioned, but still no PR builds triggered. Also target branch does contain the expected path.

Regards,

Kunal
Durga Reshma Malthi 11,595 Reputation points Microsoft External Staff Moderator

2025-07-23T08:37:20.03+00:00

Hi kb21692

I would like to suggest you create support request in Azure Portal. Go to Azure Portal -> Help + Support -> Create a support request -> Provide the required details.

Or you can report a problem in Developer Community - https://developercommunity.visualstudio.com/AzureDevOps

Hope this helps!

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

2025-07-24T07:52:44.0933333+00:00

Hi kb21692

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.

1 answer

Your answer

Durga Reshma Malthi 11,595 Reputation points Microsoft External Staff Moderator

2025-07-22T13:42:01.12+00:00

Hi kb21692

Could you please check the following things:

Ensure that the service connection you created in Azure DevOps for GitHub Enterprise has the necessary permissions to access the repository. The service connection should have at least read access to the repository and the ability to read pull requests.

In your YAML pipeline, ensure that the PR trigger is correctly configured.
pr: branches: include: - main # or the branch you want to trigger on

Ensure the pipeline is connected to the correct GitHub Enterprise repo via resources.repositories.
resources: repositories: - repository: self type: githubenterprise name: your-org/your-repo

When creating the service connection:

Select GitHub Enterprise Server

Enter your custom domain

Use a classic PAT with the correct scopes: repo, admin:repo_hook, workflow, read:org, user

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:

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.
kb21692 5 Reputation points

2025-07-22T13:58:15.5866667+00:00

Hi @Durga Reshma Malthi

Thanks for your reply. I have answered the questions inline:

Ensure that the service connection you created in Azure DevOps for GitHub Enterprise has the necessary permissions to access the repository. The service connection should have at least read access to the repository and the ability to read pull requests.

A. Service connection has access to all pipelines on the Project in Azure DevOps. I am able to manually run the build pipeline as well as run builds using CI triggers.

In your YAML pipeline, ensure that the PR trigger is correctly configured

A. Below is my snippet of yaml:

pr: branches: include: - "*"

Ensure the pipeline is connected to the correct GitHub Enterprise repo via resources.repositories.

A. Pipeline is connected since CI trigger works.

When creating the service connection:

Select GitHub Enterprise Server

Enter your custom domain

Use a classic PAT with the correct scopes: repo, admin:repo_hook, workflow, read:org, user

A. Have given complete access to the PAT.

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.

A. Have given permission for all pipelines.

In your GitHub repository:

Navigate to Settings > Webhooks and Confirm:

Azure DevOps webhook is registered

Events like pull_request, push are enabled.

A. Can see both events. However for pull_request events can see response code as 200 but the response body is below:

{"count":0,"value":[]}

Regards,

Kunal
Durga Reshma Malthi 11,595 Reputation points Microsoft External Staff Moderator

2025-07-22T16:44:41.2766667+00:00

Hi kb21692

Ensure that the PR’s target branch (e.g., main, develop, etc.) contains the YAML file at the expected path (azure-pipelines.yml).

Also ensure the PR is coming from the same repo.

Try editing and saving the pipeline again from the Azure DevOps UI. Temporarily remove the pr: block from YAML -> Commit and push. Re-add the pr: block and push again. This forces Azure DevOps to re-register the PR trigger.Hope this helps!

Please Let me know if you have any queries.
kb21692 5 Reputation points

2025-07-23T06:47:58.32+00:00

Hi @Durga Reshma Malthi

I tried all the steps you mentioned, but still no PR builds triggered. Also target branch does contain the expected path.

Regards,

Kunal
Durga Reshma Malthi 11,595 Reputation points Microsoft External Staff Moderator

2025-07-23T08:37:20.03+00:00

Hi kb21692

I would like to suggest you create support request in Azure Portal. Go to Azure Portal -> Help + Support -> Create a support request -> Provide the required details.

Or you can report a problem in Developer Community - https://developercommunity.visualstudio.com/AzureDevOps

Hope this helps!

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

2025-07-24T07:52:44.0933333+00:00

Hi kb21692

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.

Answer 1

kb21692 5

Hi @Durga Reshma Malthi

I have raised a support request with Azure. Will update the resolution if any here.

Regards,

Kunal

Durga Reshma Malthi 11,595 Reputation points Microsoft External Staff Moderator

2025-07-25T06:48:19.1066667+00:00

Hi kb21692

Please update us if you got the response from Azure.

Feel free to reach out if you have any further queries.
Marcel Wijnands 0 Reputation points

2026-03-05T22:20:54.0333333+00:00

This just seems broken. I wasted a whole day on this just to now read here that is does not work. And yes I also tried everything mentioned here. So I am curious about that azure support ticket as well.

Share via

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

1 answer

Your answer