Can you do a walk-through to connect GitHub repos to Fabric?

Wesley 0 Reputation points
2025-11-19T21:08:25.3+00:00

Have an E3 license with BI Pro. CoPilot indicates connection with GitHub personal account can be done even while in trial on Fabric. The connection is necessary for CI/CD.

Azure Data Lake Storage
Azure Data Lake Storage
An Azure service that provides an enterprise-wide hyper-scale repository for big data analytic workloads and is integrated with Azure Blob Storage.
{count} votes

2 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-11-19T21:08:43.9133333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To connect your GitHub repository to Microsoft Fabric, follow these steps:

    1. Authorize Your GitHub Account: If it's your first time connecting, you need to authorize your GitHub user. Provide the following information:
      • Display name: Must be unique for each GitHub user.
      • Personal access token: This can be your classic or fine-grained personal access token from GitHub.
      • Repository URL (optional): If you don't enter a URL, you can connect to any repo you have access to. If you enter a URL, you can only connect to that specific repository.
    2. Connect to a Workspace: Once you have authorized your GitHub account, you need to connect it to your Fabric workspace. Fill in the details about the workspace and branch you want to use:
      • Repository URL: The URL of your GitHub repository.
      • Branch name: The branch you want to connect to.
      • Folder name: Specify the folder name where you want to sync your items (optional).
      • Select Connect and sync to establish the connection.
    3. Verify Connection: After connecting, you can check the Source control section in your workspace for information about the linked branch, the status of each item, and when it last synced.

    By following these steps, you can successfully connect your GitHub repository to Microsoft Fabric for CI/CD processes.


    References:

    0 comments No comments

  2. Wesley 0 Reputation points
    2025-11-20T01:23:38.7333333+00:00

    This was in the right direction, but the necessary point is that the Fabric Tenant Setting has to be changed. This is not in the Workspace Settings. It is in the overall settings for Fabric. And the scroll down is quite long. Here is what CoPilot showed. This worked. The geographic setting also has to be enabled.

    Steps to Apply GitHub Integration

    1. In the Admin Portal → Tenant Settings → Git integration, locate:
      • Users can sync workspace items with GitHub repositories.
      1. Ensure the toggle is set to Enabled.
      2. Under Apply to, select:
        • The entire organization (or specific security groups if needed).
        1. Click Apply at the bottom of the page.
        2. Wait for propagation (usually a few minutes).

    After Applying

    • Go back to Workspace Settings → Git integration.
    • You should now see a Provider dropdown with Azure DevOps and GitHub.
    • Select GitHub, then enter:
    • Display Name
    • Personal Access Token (PAT)
      • Optional Repository URL.

        Steps to Apply GitHub Integration

        1. In the Admin Portal → Tenant Settings → Git integration, locate:
          • Users can sync workspace items with GitHub repositories.
        2. Ensure the toggle is set to Enabled.
        3. Under Apply to, select:
          • The entire organization (or specific security groups if needed).
        4. Click Apply at the bottom of the page.
        5. Wait for propagation (usually a few minutes).

        After Applying

        • Go back to Workspace Settings → Git integration.
        • You should now see a Provider dropdown with Azure DevOps and GitHub.
        • Select GitHub, then enter:
          • Display Name
          • Personal Access Token (PAT)
          • Optional Repository URL.
    0 comments No 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.