Azure DevOps: GitHub App triggers stopped for all repositories on ghe.com since Nov 13, 2026

Andy Stevenson 5 Reputation points
2026-11-17T15:28:35.4633333+00:00

Problem description

I am experiencing an issue where GitHub App triggers for Azure Pipelines have stopped working for all repositories on ghe.com since approximately 13 November 2026 at 21:15 UTC. The expected behavior was that pushes, pull requests, and comment commands would trigger CI/CD pipelines, but none of these events are now causing pipeline runs to queue. Manual runs still work and post check results back to GitHub, indicating that outbound communication is functional. The problem seems to affect inbound GitHub events into Azure DevOps, specifically those related to trigger evaluation.

Environment

Azure DevOps Services organization and project using YAML pipelines; repositories hosted in GitHub Enterprise Cloud with EU data residency on ghe.com; GitHub identity model: Enterprise Managed Users; Azure Pipelines connected through a GitHub App-based service connection of type GitHub Enterprise Cloud with data residency; GitHub App installation configured for all repositories, reported as active, with no pending permission requests; shared service connection used by approximately 259 YAML pipelines.

What I've already tried

I established a timeline indicating the last known automatic pipeline run was queued on 13 November 2026 at 21:14 UTC, after which GitHub events no longer triggered pipelines. I verified that scope is not limited to one trigger type and confirmed that manual runs still function and post check results. I reviewed the GitHub App installation details and found it active and covering all repositories. No changes to GitHub org settings, app installation, permissions, webhooks, IP allowlist, or EMU occurred around the time the issue started. I tested manual execution of pipelines, which succeeded. I checked the trigger YAML configurations, which have not changed around the incident date, and confirmed that the repositories are referenced correctly. I attempted to create new service connections and test pipelines using a fresh connection, but Azure DevOps does not allow creating the new connection, which supports the hypothesis of a service-side issue.

Current status

Currently, GitHub events are not triggering pipelines automatically, while manual runs continue to work and post check results. I suspect a problem in the inbound event processing path between GitHub and Azure DevOps. I am seeking guidance on how to further diagnose whether GitHub is delivering events properly, whether Azure DevOps is receiving and processing these events correctly, or if there is a broader issue with the GitHub App installation or its association. Any steps to verify the event delivery logs, webhook statuses, or installation associations would be appreciated.

Azure DevOps
0 comments No comments

1 answer

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.