SQL End point connection through SSMS

[PraveenVeli]

Hi All,

I can connect to Fabric from SSMS successfully when I'm at home, but when I attempt to connect to Fabric from SSMS when at office, it fails to work with below error.

[v-lgarikapat]

Hi @PraveenVeli , 

Thanks for reaching out to the Microsoft fabric community forum.

@rohit1991 , @shashiPaul1570_ 

I wanted to follow up and confirm whether you’ve had the opportunity to review the information  provided by @rohit1991 , @shashiPaul1570_  . If you have any questions or need further clarification, please don’t hesitate to reach out.

We appreciate your collaboration and support!

Best regards,
Lakshmi.

[v-lgarikapat]

Hi @PraveenVeli ,

We’d like to confirm whether your issue has been successfully resolved. If you still have any questions or need further assistance, please don’t hesitate to reach out. We’re more than happy to continue supporting you.

We appreciate your engagement and thank you for being an active part of the community.

Best Regards,
Lakshmi.

[PraveenVeli]

Hi @v-lgarikapat ,

This didn't resolve yet. It is due to the fact that connections from my office are going through firewall and security  team are working through them. Looks like Fabric got too many IPs that goes through part of it's connection.

[v-lgarikapat]

Hi  @PraveenVeli,

We’d like to confirm whether your issue has been successfully resolved. If you still have any questions or need further assistance, please don’t hesitate to reach out. We’re more than happy to continue supporting you.

We appreciate your engagement and thank you for being an active part of the community.

Best Regards,
Lakshmi.

[rohit1991]

Hi @PraveenVeli 

Since the connection works fine from home, it shows your Fabric SQL endpoint and login details are correct. The problem is with the office network. Most likely, your company firewall or proxy is blocking the SQL traffic (usually port 1433) or only allows access through a VPN. That’s why SSMS cannot reach the endpoint when you’re at work. The easiest next step is to check with your IT/network team and ask if outbound connections to the Fabric SQL endpoint are allowed. Once the right rule or VPN is in place, the same connection that works at home should also work at the office.

[shashiPaul1570_]

Hi @PraveenVeli,

If SSMS works from home but not at the office, it’s almost always a network/firewall restriction on the corporate side.

• Ensure you’re using SSMS 19+ with Microsoft Entra – Universal with MFA authentication.

• Fabric SQL endpoints require outbound TCP 1433 to *.sql.fabric.microsoft.com and TCP 443 to AAD login endpoints (e.g., login.microsoftonline.com).

• Many offices block 1433, which explains why it works on home networks but not on office internet.

• If Conditional Access is in place, check AAD sign-in logs to confirm if location/device restrictions are blocking SSMS.

👉 Ask IT to allow these endpoints/ports, then retry — it should connect as expected.

You can follow below mentioned links for more details.

Reddit-- Firewall & SQL Endpoint Connectivity
https://www.reddit.com/r/MicrosoftFabric/comments/1luwk4z/how_to_configure_firewall_to_allow_avs_sys...

Fabric SQL endpoints use TDS over TCP port 1433, which must be open outbound on your office network.

https://community.fabric.microsoft.com/t5/Data-Warehouse/Connecting-to-SQL-end-point-in-Fabric-from-...

Hope this clarifies 🙌 If it helps, please give a Kudos 👍 and mark as Accepted Solution ✅.

Best regards,
Shashi Paul