Forum Discussion
Fabric SQL Connection End Point
Hello All,
I am trying to connect a Fabric Data Warehouse to an external application. When I copy the SQL conncetion string (XXXXXX.datawarehouse.fabric.microsoft.com). This external application only accepts basic SQL Server authentication parameters:
- Host/Server
- Port
- User
- Password
Because it does not natively support Service Principal (SPN) or Microsoft Entra ID interactive authentication, I am attempting to create a traditional database user with a password directly within the Fabric SQL frontend.
Issue: When I execute CREATE USER [username] WITH PASSWORD = '...' in the Fabric query console, the command is denied. The system prevents the execution because I am not connected as a SA user.
Is it possible to obtain or configure a Master/Admin (sa) SQL-authenticated account for a Fabric Data Warehouse to manage this authentication.
If traditional SQL authentication (CREATE USER ... WITH PASSWORD) is explicitly blocked or not supported in Fabric Data Warehouses, what is the recommended workaround to connect legacy applications that only accept a standard Port/User/Password connection string?
Thank you,
Venkat
Unfortunately, Fabric SQL endpoints do not support SQL auth.
The way would be to use Service principle auth and upgrade the application.
5 Replies
Hi VNallagatla , completly agree with NandanHegde about this "Fabric SQL endpoints do not support SQL auth" and just want to save you some time & frustration sharing with you that, not even Fabric SQL Databases permits SQL Authenetication (User/Password); it is NOT because you're not connected as a SA user, it's just NOT possible to use SQL-base authentication ANYWHARE ... the idea is to rely completly on Entra ID for authentication.
The only workaround is using another service like for instance Data Factory that serves as a "middle tier" as example, that is, connects to the source via linked services with sql auth. and then sink the data to Fabric using linked services using SPN authentication.
Another option you may want to explore is On-premises Data Gateway 🤔 If the legacy app is on-prem and can't be modified, the Gateway can broker the Entra ID auth to Fabric while the app connects to the Gateway locally.
Well, this is the reality of today's Fabric landscape on this area, hope you find the right option for your case .😁🤞
If you find this informatino useful, give us thumb's up or even better, mark as solution, all the very best
Thank you!
I will try to look at the option suggested
Hello VNallagatla,
Fabric Data Warehouse currently does not support traditional SQL Server authentication (for example, sa, SQL logins, or CREATE USER ... WITH PASSWORD).
Authentication is based on Microsoft Entra ID (Azure AD), so there isn't a master SQL login that can be created or managed like in SQL Server or Azure SQL Database.
If your external application only supports Host + Port + Username + Password (SQL authentication), there isn't a native way to connect it directly to a Fabric Data Warehouse.
Your options are:
- Use Microsoft Entra ID authentication, if the application supports it (interactive login, service principal, or managed identity).
- Introduce an intermediate layer, such as Azure SQL Database, SQL Server, or another supported service that the legacy application can authenticate to, and then synchronize or expose the Fabric data as needed.
- Check whether the application vendor offers a newer connector or driver that supports Microsoft Entra ID authentication for SQL endpoints.
Unfortunately, there isn't a supported way to obtain an sa account or create SQL-authenticated users in Fabric Data Warehouse.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.Thank you Omkar Shinde!
I'm on talks with the other vendor to see if the authentication is possible through Entra ID
Unfortunately, Fabric SQL endpoints do not support SQL auth.
The way would be to use Service principle auth and upgrade the application.
