Azure Data Factory GitHub Integration in a Private Endpoint Restricted Environment

Parasi, Vijay (Contractor) 0 Reputation points
2026-08-06T15:19:17.98+00:00

Description

We are planning to migrate Azure Data Factory (ADF) source control integration from Azure DevOps Repos to GitHub Enterprise.

Current setup:

  • Azure Data Factory is deployed in Azure.
  • ADF source control is currently connected to Azure DevOps.
  • We intend to switch source control to a GitHub Enterprise repository.
  • GitHub organization uses OAuth App approval restrictions, and the AzureDataFactory application requires organization-level approval.
  • ADF linked services use System Assigned Managed Identity for authentication.
  • No credentials or secrets are stored in source control.
  • GitHub Secret Scanning and Push Protection are enabled.

Our security team has raised concerns regarding Private Endpoint requirements.

Question

Microsoft documentation confirms that:

  1. Azure Data Factory supports GitHub as a native source control provider.
  2. Managed Virtual Networks and Managed Private Endpoints are used for secure connectivity between ADF and supported Azure services (such as Azure Storage, Azure SQL Database, Synapse, Key Vault, etc.).

However, we could not find documentation that clearly explains how ADF GitHub source control integration operates when organizations enforce Private Endpoint-only access standards.

We would like clarification on the following:

  1. How does Azure Data Factory communicate with GitHub for source control integration?
  2. Does ADF GitHub integration use a Microsoft-managed control plane, or is there a customer-configurable networking path?
  3. Is Private Endpoint connectivity supported or required for GitHub integration with ADF?
  4. If ADF is deployed in an environment where public access is restricted and Private Endpoints are mandated, what is Microsoft's recommended architecture for GitHub source control integration?
  5. Are there any documented limitations, prerequisites, or security considerations for using GitHub integration in such environments?

Any Microsoft documentation, architecture guidance, or best practices would be greatly appreciated.

References

  • ADF Source Control: https://learn.microsoft.com/azure/data-factory/source-control
  • Managed Virtual Network and Managed Private Endpoints: https://learn.microsoft.com/azure/data-factory/managed-virtual-network-private-endpoint

    Description

    We are planning to migrate Azure Data Factory (ADF) source control integration from Azure DevOps Repos to GitHub Enterprise. Current setup:
    • Azure Data Factory is deployed in Azure.
    • ADF source control is currently connected to Azure DevOps.
    • We intend to switch source control to a GitHub Enterprise repository.
    • GitHub organization uses OAuth App approval restrictions, and the AzureDataFactory application requires organization-level approval.
    • ADF linked services use System Assigned Managed Identity for authentication.
    • No credentials or secrets are stored in source control.
    • GitHub Secret Scanning and Push Protection are enabled.
    Our security team has raised concerns regarding Private Endpoint requirements.

    Question

    Microsoft documentation confirms that:
    1. Azure Data Factory supports GitHub as a native source control provider.
    2. Managed Virtual Networks and Managed Private Endpoints are used for secure connectivity between ADF and supported Azure services (such as Azure Storage, Azure SQL Database, Synapse, Key Vault, etc.).
    However, we could not find documentation that clearly explains how ADF GitHub source control integration operates when organizations enforce Private Endpoint-only access standards. We would like clarification on the following:
    1. How does Azure Data Factory communicate with GitHub for source control integration?
    2. Does ADF GitHub integration use a Microsoft-managed control plane, or is there a customer-configurable networking path?
    3. Is Private Endpoint connectivity supported or required for GitHub integration with ADF?
    4. If ADF is deployed in an environment where public access is restricted and Private Endpoints are mandated, what is Microsoft's recommended architecture for GitHub source control integration?
    5. Are there any documented limitations, prerequisites, or security considerations for using GitHub integration in such environments?
    Any Microsoft documentation, architecture guidance, or best practices would be greatly appreciated.

    References

Azure Private Link
Azure Private Link

An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Allan Solomon Mejia 8,840 Reputation points
    2026-08-07T01:09:11.1366667+00:00

    Hello @Parasi, Vijay (Contractor)

    Azure Data Factory’s Git integration should be treated separately from its data-plane networking.

    Managed Virtual Network and managed private endpoints don’t carry ADF source-control traffic to GitHub. Those features are designed primarily for Integration Runtime connectivity from pipelines to supported data stores and compute services. ADF’s Git integration is part of the authoring/control-plane experience.

    For GitHub, ADF currently supports:

    • GitHub.com
    • GitHub Enterprise Cloud
    • GitHub Enterprise Server
    • Public and private repositories, provided the user has read/write repository permissions

    For repositories owned by a GitHub organization, an organization administrator must authorize the Azure Data Factory application. ADF then accesses repositories on behalf of the signed-in user according to that user’s GitHub permissions.

    Private Endpoint requirement

    There is no documented Azure Private Endpoint that you can create between an ADF managed virtual network and GitHub.com or GitHub Enterprise Cloud for the native ADF Git integration.

    Therefore, enabling private endpoints for the ADF resource and its linked services does not make the GitHub connection private, nor does it route GitHub traffic through the ADF managed virtual network.

    For GitHub Enterprise Server, Microsoft documents that the server must use HTTPS and that the customer is responsible for its firewall, VPN, and network policies. Authentication uses a GitHub personal access token rather than the GitHub.com OAuth flow.

    However, Microsoft doesn’t document a customer-configurable VNet injection, private endpoint, self-hosted Integration Runtime, proxy, or ExpressRoute path for the native ADF source-control service to reach an internally isolated GitHub Enterprise Server.

    Recommended architecture

    1. If your policy allows approved public SaaS control-plane traffic, the typical design is:
    2. Keep ADF datasets, linked services, and Integration Runtime traffic private through managed private endpoints.
    3. Approve the Azure Data Factory GitHub application at the GitHub organization level.
    4. Restrict repository access using GitHub permissions, branch protection, OAuth application policies, secret scanning, and push protection.
    5. Configure Git integration only on the development factory. Promote changes to test and production through CI/CD rather than enabling Git integration on every factory. Microsoft’s ADF policy guidance also recommends Git integration only for development factories.

    If your security standard requires all source-control communication to remain on private network paths, native ADF-to-GitHub integration may not meet that requirement. A practical alternative is to:

    • Keep the repository in GitHub Enterprise Server.
    • Use self-hosted GitHub Actions runners or another privately hosted build agent with access to the repository and Azure.
    • Generate and deploy the ADF ARM templates through CI/CD using a managed identity or workload identity federation.
    • Use ADF live mode or another approved repository option for authoring, depending on your governance requirements.

    One important clarification: the System Assigned Managed Identity used by your ADF linked services is unrelated to GitHub authentication. GitHub.com integration uses GitHub authorization, while GitHub Enterprise Server uses a personal access token.

    In summary, Private Endpoint-only access for ADF data services and native GitHub integration are separate concerns. The ADF documentation supports GitHub as a source-control provider, but it doesn’t document a private endpoint or customer-managed private networking path for that Git control-plane integration.

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

    Was this answer helpful?

    0 comments

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.