Issue connecting Azure Sentinel GitHub app to Sentinel Instance when IP allow list is enabled

Hi everyone,

I’m running into an issue connecting the Azure Sentinel GitHub app to my Sentinel workspace in order to create our CI/CD pipelines for our detection rules, and I’m hoping someone can point me in the right direction.

Symptoms:

When configuring the GitHub connection in Sentinel, the repository dropdown does not populate.

There are no explicit errors, but the connection clearly isn’t completing.

If I disable my organization’s IP allow list, everything works as expected and the repos appear immediately.

I’ve seen that some GitHub Apps automatically add the IP ranges they require to an organization’s allow list. However, from what I can tell, the Azure Sentinel GitHub app does not seem to have this capability, and requires manual allow listing instead.

What I’ve tried / researched:

Reviewed Microsoft documentation for Sentinel ↔ GitHub integrations

Looked through Azure IP range and Service Tag documentation

I’ve seen recommendations to allow list the IP ranges published at //api.github.com/meta, as many GitHub apps rely on these ranges

I’ve already tried allow listing multiple ranges from the GitHub meta endpoint, but the issue persists

My questions:

Does anyone know which IP ranges are used by the Azure Sentinel GitHub app specifically?

Is there an official or recommended approach for using this integration in environments with strict IP allow lists?

Has anyone successfully configured this integration without fully disabling IP restrictions?

Any insight, references, or firsthand experience would be greatly appreciated. Thanks in advance!