Forum Discussion
Unable to connect to SQL server in Power bi desktop
- 10 months ago
Hi Shivakumarh ,
we need more information on this to help you further.can you follow below checklist and see if it works?
- Use Azure Synapse Analytics connector
Get Data > Azure > Azure Synapse Analytics - Enter correct server name
yourworkspace.sql.azuresynapse.net (for dedicated pool)
yourworkspace-ondemand.sql.azuresynapse.net (for serverless pool) - Choose authentication method
- Azure Active Directory - Organizational Account
- Basic (SQL username/password)
- Windows (if domain-joined) - Clear cached credentials
File > Options and settings > Data source settings > Clear Permissions - Test port connectivity.try below command in power shell.
Test-NetConnection -ComputerName yourworkspace.sql.azuresynapse.net -Port 1433- Test-NetConnection -ComputerName yourworkspace.sql.azuresynapse.net -Port 1433
- Ping server to verify DNS resolution try below command in command prompt.
ping yourworkspace.sql.azuresynapse.net- Check Synapse firewall settings
Enable public network access
Add your client IP to allowed list
Enable “Allow Azure services to access this workspace” - Try Azure Data Studio for connection test
- Download Azure Data Studio
- Use .pbids file to force correct connector
Create .pbids with server and connector settings - Verify workspace type and database context
- Check for private endpoint configuration
- Ensure you're on same VNet or using VPN
- Configure private DNS zone if needed - Inspect Conditional Access Policies
Confirm AAD policies aren’t blocking Power BI Desktop - Monitor Synapse logs for failed login attempts
Use Azure Monitor or Diagnostic Settings in Synapse workspace
Please give kudos or mark it as solution if it helps.
Thanks and Regards,
Praful
- Use Azure Synapse Analytics connector
Hey, Shivakumarh ,
can be a lot of things, but most likely your device does not have access to the server you entered, or you misspelt the server name. It can happen, for example, if you're connecting to an On-premise server, while you don't have an active VPN, for example. Or if you're on virtual machine, that virtual machine doesn't have direct access allowerd to the server.
- danextian11 months ago
Super User
This is very common scenario. Just because one has the address and the credentials doesn't mean the server would allow connection to it. My company's are in the cloud and even with the correct credentials I can't just connect directly.