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!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hello,
I am currently running the following configuration in Azure:
PowerBI -> VM with PowerBI Gateway in vnetA -> VM with SQL Server in vnetB
VnetA and VnetB are peered
The VnetA and VnetB have inbound and outbound rules set to AllowAllVnetInbound\AllowAllVnetOutbound
Once I set this up I can see the gateway in my PowerBI instance. When I try to add a datasource to the SQL server in vnetB, however, it is unable to connect.
I can make it connect by adding the IP address of the Gateway VM directly to the inbound rules of the VnetB Network Security Group, but due to scale this is not a good solution.
Anyone have an idea why the network peering in this case is not allowing the connection?
Thanks.
Solved! Go to Solution.
I figured it out:
The problem was that the domain name of the SQL server in VnetB was being resolved to the external IP by the gateway. Switching it to the internal IP when adding the data source resolved the issue
I figured it out:
The problem was that the domain name of the SQL server in VnetB was being resolved to the external IP by the gateway. Switching it to the internal IP when adding the data source resolved the issue
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.