Forum Discussion
Unable To connect MS Fabric Data Warehouse using SSMS
Hi,
I am using 60 days trail plan of Microsoft Fabric and in it I have created a new Data Warehouse and I want to access it using SQL Server Management Studio (SSMS) tool present on my VM.
When I try to access it is giving me below error. I don't understand how to fix this issue?
I added the port in the inbound port rule as well in the azure VM but still not able to connect the Fabric data warehouse using SSMS. Am i missing anything?
Hi @AndyDDC and Yang,
I checked with our IT and Networking team and got to know that the IP range needs to be added and whitelisted in our VPN network.
They have added the below range, which they think is bit risky becuase it involes entire range and when they tried the specific range it didn't work as per them.
NetRange: 40.74.0.0 - 40.125.127.255
CIDR: 40.125.0.0/17Post adding the above range, i was able to access the data warehouse thorugh SSMS.
Generally, what should be whitelisted as per MS guidelines?
7 Replies
Hi @AndyDDC and Yang,
I checked with our IT and Networking team and got to know that the IP range needs to be added and whitelisted in our VPN network.
They have added the below range, which they think is bit risky becuase it involes entire range and when they tried the specific range it didn't work as per them.
NetRange: 40.74.0.0 - 40.125.127.255
CIDR: 40.125.0.0/17Post adding the above range, i was able to access the data warehouse thorugh SSMS.
Generally, what should be whitelisted as per MS guidelines?
Hi surajpardeshi ,
If IT teams are concerned about whitelisting large ranges, they can refer to the specific IP ranges that Microsoft provides for Azure services.
You can follow this document here:
Gateway IP addresses - Azure Synapse Analytics | Microsoft Learn
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi surajpardeshi ,
I can't find your authentication method. I used MFA authentication when I tested it and it worked well.
Regarding your error, you can consider the following points:
Make sure the server name and port number are correct. In my VM, I configured inbound rules in the following interface:
Open SQL Server Configuration Manager and make sure TCP/IP and named pipes are enabled.
Make sure the SQL Server Browser service is running. This service helps resolve the port number of the named instance.
Restart the SQL Server service.
Make sure the username you entered is in the correct format.
Please contact me after trying the above steps.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!Hi Yang,
I was using standalone SSMS tool v19.1 and I didn't had Microsoft Entra MFA authentication type, I installed latest version of SSMS i.e. V20.2 and it has Microsoft Entra MFA authentication type. I tried with suggested authentication type but still I am getting the error.
- AndyDDC
Most Valuable Professional
Hi surajpardeshi if you're connecting from an Azure VM, does the VM allow outbound traffic? Have you configured an outbound rule on the VM to allow port 1433.
Hi @AndyDDC , Yes i have added the port 1433 in outbound rule as well on portal along with within VM but still i am getting the error.
