Forum Discussion
Fabric Connection to Azure SQL DB Failing Even After Whitelisting Southeast Asia ADF & PowerBI IPs
Hello BharathKumarS apologies for misreading that. For PaaS services too, your best bet is to use Managed Private Endpoint on Fabric pointing to your Azure SQL instance.
You can try below options.
- On-premises data gateway: install the gateway on a VM/server with a fixed outbound public IP, then add only that IP to the Azure SQL firewall.
- VNet data gateway / private endpoint: use private networking so Fabric reaches Azure SQL through a controlled VNet/private endpoint path.
- Azure SQL firewall rule: allow only the required client/gateway public IP, instead of enabling all Azure services.
As deborshi_nag mentioned you can upvote on the same feature requested. Please consider this as an accepted soltuon if helps or give some kudos.
BharathKumarS, Were you able to connect the same DB into SSMS or in the Azure? Please try to connect same DB with same credentials (Which you have used to create connection...). Please let me know what you found?
yes, I used SQL User auth and via SSMS I am able to connect to db.
Sql user is also a db_owner.
I am even able to create the connection when I enable "Allow Azure services and resources to access this server"
But i am looking for ways to connect without enabling that option.You can try below options.
- On-premises data gateway: install the gateway on a VM/server with a fixed outbound public IP, then add only that IP to the Azure SQL firewall.
- VNet data gateway / private endpoint: use private networking so Fabric reaches Azure SQL through a controlled VNet/private endpoint path.
- Azure SQL firewall rule: allow only the required client/gateway public IP, instead of enabling all Azure services.
As deborshi_nag mentioned you can upvote on the same feature requested. Please consider this as an accepted soltuon if helps or give some kudos.
