Forum Discussion

saharz's avatar
saharz
New Member
8 months ago
Solved

cannot connect to api.powerbi.com

Hello friends, I can not connect to the api.powerbi.com from a Hub/Spoke-VM. I get the errormessage: "errorMsg": "HTTPSConnectionPool(host='api.powerbi.com', port=443): Max retries exceeded with ...
Need Help
  • Zanqueta's avatar
    Zanqueta
    8 months ago

    Hi saharz,

     

    How to fix it

    1. Validate connectivity outside Power BI Run:
     
    Test-NetConnection api.powerbi.com -Port 443
    If this fails, the issue is not Power BI but network routing or firewall.
    2. Check firewall and proxy settings
    • Ensure outbound traffic to api.powerbi.com on port 443 is allowed.
    • If you use a proxy, configure it for the VM:
      • Power BI REST API calls respect system proxy settings.
      • Add proxy exceptions if necessary.
    3. Confirm DNS and routing
    • nslookup works, so DNS is fine.
    • Check if the VM can reach external IPs via HTTPS (e.g., Test-NetConnection google.com -Port 443 works).
    • If Google works but Power BI does not, the domain may be blocked by a security policy.
    4. Whitelist required endpoints Microsoft requires these endpoints for Power BI service:
    • api.powerbi.com
    • login.microsoftonline.com
    • *.analysis.windows.net 
    If the issue persists, try testing from another VM in the same network to confirm if it’s a routing or policy issue.

     

    If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

    Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.

Zanqueta's avatar
Zanqueta
Super User
8 months ago

Hi saharz,

 

How to fix it

1. Validate connectivity outside Power BI Run:
 
Test-NetConnection api.powerbi.com -Port 443
If this fails, the issue is not Power BI but network routing or firewall.
2. Check firewall and proxy settings
  • Ensure outbound traffic to api.powerbi.com on port 443 is allowed.
  • If you use a proxy, configure it for the VM:
    • Power BI REST API calls respect system proxy settings.
    • Add proxy exceptions if necessary.
3. Confirm DNS and routing
  • nslookup works, so DNS is fine.
  • Check if the VM can reach external IPs via HTTPS (e.g., Test-NetConnection google.com -Port 443 works).
  • If Google works but Power BI does not, the domain may be blocked by a security policy.
4. Whitelist required endpoints Microsoft requires these endpoints for Power BI service:
  • api.powerbi.com
  • login.microsoftonline.com
  • *.analysis.windows.net 
If the issue persists, try testing from another VM in the same network to confirm if it’s a routing or policy issue.

 

If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.

saharz's avatar
saharz
New Member
8 months ago

I figured it out. Our environment had an empty Private DNS Entry for Power BI and "Fallback to Internet" was disabled. After enabling "Fallback to Internet" it worked. Thank you