Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
I have a mysql database I need to read in using a Dataflow Gen1 on my Power BI service. We are US based organization (WA state if that matters).
I've seen a few different questions point to this link for IP Addresses: Download Azure IP Ranges and Service Tags – Public Cloud from Official Microsoft Download Center
I downloaded that file and pulled out the IP Addresses from the "addressPrefixes" section for every object that had a name "PowerBI.*US" (basically pulling out the Power BI objects for US based servers).
When adding these IP Addresses to my firewall, I still get an error and can't connect. The error is just a generic one saying it is having trouble connecting.
I know the connection in general works, since I can allow all IP Addresses through and succesfully connect.
Am I pulling out the IP Addresses incorrectly from that url of addresses? Is there a different file I should be looking at?
Note: My setup doesn't use an on prem data gateway. I'm hoping to have a Dataflow Gen 1 talk directly to the MySQL database which is hosted on an AWS EC2 instance.
Solved! Go to Solution.
Hi @jeremyt,
I had assumed that. I knew that there were some endpoints other than powerbi.com ones that were required for dataflows, and the easiest place to find them was the gateway documentation.
I think if you allow the gateway ports on your EC2 server, it should allow everything for full communication.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi @jeremyt,
I think you need more than just the PowerBI address range.
On the on prem data gateway docs, they specific that these endpoints are also required for dataflow gen 1 and 2:
*.core.windows.net | 443 | Used by Dataflow Gen1 to write data to Azure Data Lake. |
*.dfs.fabric.microsoft.com | 443 | Endpoint used by Dataflow Gen1 and Gen2 to connect to OneLake. Learn more |
Adjust communication settings for the on-premises data gateway | Microsoft Learn
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Thanks @tayloramy for the pointers. One thing I should have mentioned in my question (and I'll add it now) is that I don't have an on prem data gateway, and am hopoing to have my dataflow to talk to my MySQL database on an EC2 server directly.
Hi @jeremyt,
I had assumed that. I knew that there were some endpoints other than powerbi.com ones that were required for dataflows, and the easiest place to find them was the gateway documentation.
I think if you allow the gateway ports on your EC2 server, it should allow everything for full communication.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
WINNER WINNER CHICKEN DINNER!
That worked perfectly! I added the IP Addresses for all the GatewayManager.*US objects and things worked perfectly.
THank you for all your help!