Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Compete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.

Reply
xyrodriguez
Frequent Visitor

Unable to connect to github repo

I'm trying to connect my GitHub repository to Power BI for data visualization purposes, but I'm running into an issue. Here’s the error message I’m seeing:

Details: "The GitHub owner/repository provided could not be found or you do not have sufficient access. Please check the values and try again."

Some context:

  • My organization recently accepted my access request to the repository.
  • I've double-checked the owner/repository name for accuracy, so it should be correct.

Despite this, Power BI isn’t recognizing my access. Has anyone else encountered this issue or have suggestions on how to resolve it?

 

xyrodriguez_0-1730850800542.png

xyrodriguez_1-1730851088717.png

 

1 ACCEPTED SOLUTION
VahidDM
Super User
Super User

Hi @xyrodriguez 

Here are some steps and suggestions that might help you resolve the problem:

  1. Verify Repository Access Permissions:

    • Confirm Access Level: Ensure that you have at least read access to the repository. Sometimes, after being granted access, there might be a delay before all services recognize the change.
    • Accept Invites: Check if there's an invitation email from GitHub that you need to accept to confirm your access.
  2. Personal Access Token (PAT):

    • Generate a PAT: Since you're accessing a repository that might be private, you may need to authenticate using a Personal Access Token.
      • Go to your GitHub Settings > Developer settings > Personal access tokens.
      • Click on Generate new token.
      • Select scopes like repo (for full control of private repositories) and any others that are necessary.
    • Use PAT in Power BI: When prompted for credentials in Power BI, use your username and the generated PAT as the password.
  3. Double-Check Repository Details:

    • Owner and Repository Name: Make sure that the owner (which could be an organization or username) and the repository name are correct and case-sensitive.
    • Correct Format: Input the repository details exactly as required by Power BI, without any extra spaces or characters.
  4. Clear Cached Credentials in Power BI:

    • Remove Previous Credentials:
      • Go to File > Options and settings > Data source settings.
      • Find any GitHub-related entries and clear the permissions.
    • Restart Power BI: Close and reopen Power BI to ensure the changes take effect.
  5. Network and Firewall Settings:

    • Corporate Firewall: If you're on a corporate network, firewall settings might block Power BI from accessing external sites like GitHub.
    • Proxy Settings: Ensure that Power BI is configured to use the correct proxy settings if your network requires it.
  6. Update Power BI:

    • Latest Version: Make sure you're using the latest version of Power BI Desktop, as updates often include fixes for connectivity issues.
  7. Test with a Public Repository:

    • Isolate the Issue: Try connecting to a public GitHub repository to see if the problem persists. This can help determine if the issue is with your access or with Power BI itself.
  8. GitHub Enterprise Considerations:

    • Enterprise Account: If your organization uses GitHub Enterprise, the URL and access methods might differ.
    • Check with Admins: Consult your GitHub Enterprise administrators for the correct connection details.
  9. Time Lag After Access Grant:

    • Propagation Delay: Sometimes, after being granted access to a repository, it may take some time for permissions to propagate fully.
    • Wait and Retry: If access was granted very recently, try waiting for a few hours before attempting to connect again.

If this post helps, please consider accepting it as the solution to help the other members find it more quickly.

Appreciate your Kudos!! 

 

LinkedIn|Twitter|Blog |YouTube 

View solution in original post

1 REPLY 1
VahidDM
Super User
Super User

Hi @xyrodriguez 

Here are some steps and suggestions that might help you resolve the problem:

  1. Verify Repository Access Permissions:

    • Confirm Access Level: Ensure that you have at least read access to the repository. Sometimes, after being granted access, there might be a delay before all services recognize the change.
    • Accept Invites: Check if there's an invitation email from GitHub that you need to accept to confirm your access.
  2. Personal Access Token (PAT):

    • Generate a PAT: Since you're accessing a repository that might be private, you may need to authenticate using a Personal Access Token.
      • Go to your GitHub Settings > Developer settings > Personal access tokens.
      • Click on Generate new token.
      • Select scopes like repo (for full control of private repositories) and any others that are necessary.
    • Use PAT in Power BI: When prompted for credentials in Power BI, use your username and the generated PAT as the password.
  3. Double-Check Repository Details:

    • Owner and Repository Name: Make sure that the owner (which could be an organization or username) and the repository name are correct and case-sensitive.
    • Correct Format: Input the repository details exactly as required by Power BI, without any extra spaces or characters.
  4. Clear Cached Credentials in Power BI:

    • Remove Previous Credentials:
      • Go to File > Options and settings > Data source settings.
      • Find any GitHub-related entries and clear the permissions.
    • Restart Power BI: Close and reopen Power BI to ensure the changes take effect.
  5. Network and Firewall Settings:

    • Corporate Firewall: If you're on a corporate network, firewall settings might block Power BI from accessing external sites like GitHub.
    • Proxy Settings: Ensure that Power BI is configured to use the correct proxy settings if your network requires it.
  6. Update Power BI:

    • Latest Version: Make sure you're using the latest version of Power BI Desktop, as updates often include fixes for connectivity issues.
  7. Test with a Public Repository:

    • Isolate the Issue: Try connecting to a public GitHub repository to see if the problem persists. This can help determine if the issue is with your access or with Power BI itself.
  8. GitHub Enterprise Considerations:

    • Enterprise Account: If your organization uses GitHub Enterprise, the URL and access methods might differ.
    • Check with Admins: Consult your GitHub Enterprise administrators for the correct connection details.
  9. Time Lag After Access Grant:

    • Propagation Delay: Sometimes, after being granted access to a repository, it may take some time for permissions to propagate fully.
    • Wait and Retry: If access was granted very recently, try waiting for a few hours before attempting to connect again.

If this post helps, please consider accepting it as the solution to help the other members find it more quickly.

Appreciate your Kudos!! 

 

LinkedIn|Twitter|Blog |YouTube 

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors