Forum Discussion

KGU_16031986's avatar
KGU_16031986
Advocate I
7 months ago

Lakehouse/ warehouse support for SQL Logins

There is a concern that lakehouse/warehouse or any database within Fabric does not support sql logins. So if we need to access database from a webpage or real time dashboards like Grafana, we cannot use Fabric databases.Any solution or workaround to acheive this? 

data engineering

4 Replies

  • deborshi_nag's avatar
    deborshi_nag
    Super User
    7 months ago

    Hi KGU_16031986 

     

    Microsoft Fabric supports Microsoft Entra ID (users, service principals, and managed identities) only! You can use a SPN or a Managed Identity for your use case. 

     

    For Web Apps - 

    • Register an app in Entra ID (or use a managed identity if the app runs on Azure App Service, Functions, Container Apps, AKS, etc.).
    • Grant the app workspace access and database permission (e.g., db_datareader, specific schemas, or securables) using the Fabric SQL role model.
    • The app gets an access token from Entra (OAuth2 client‑credentials flow for SPN or MSI flow for managed identity).
    • Connect via a regular TDS client/driver (ODBC/JDBC/ADO.NET) using the token (no username/password).

     

    For Grafana

    Use Fabric’s Real‑Time Intelligence (Kusto) route and Grafana’s Azure Data Explorer (ADX/Kusto) datasource.

    • Fabric’s Eventhouse / KQL Database stores real‑time data and exposes it through the ADX-compatible endpoint (Kusto). Grafana has a first‑class “Azure Data Explorer” data source supporting Entra auth (Managed Identity, Service Principal, Current User). 
    • This pattern is already documented and used in demos/labs (Managed Grafana ↔ KQL DB).

    fabricrtidemos/grafana_server_telemetry_demo at main · microsoft/fabricrtidemos

     

     

    Hope this helps - please appreciate by leaving a Kudos or accepting it as a Solution! 

  • ssrithar's avatar
    ssrithar
    Super User
    7 months ago

    Hi KGU_16031986 ,

     

    Yes this is a known issue but as a workaround to keep your view logic manageable:

    • Store view definitions in a .sql source control file in a Git repo or notebook.

    • Use deployment pipelines or Fabric Git integration (if enabled) to manage updates consistently across environments.

    If this post helps, then please appreciate giving a Kudos or accepting as a 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!

    • KGU_16031986's avatar
      KGU_16031986
      Advocate I
      7 months ago

      ssrithar ,
      Looks like your reply is not answering the issue that I mentioned. but thanks for your time. 

  • v-echaithra's avatar
    v-echaithra
    Community Support
    7 months ago

    Hi KGU_16031986 ,

    This is a current limitation of Microsoft Fabric. Fabric SQL endpoints support Microsoft Entra ID (Azure AD) authentication only and do not allow traditional SQL logins. As a result, tools such as web applications, Grafana, or custom services that rely on username/password SQL authentication cannot connect directly at this time.
    Microsoft Entra Authentication in Fabric Data Warehouse - Microsoft Fabric | Microsoft Learn

    As a workaround, you can follow the approach suggested by deborshi_nag .
    If this is a requirement for your scenario, you may also consider submitting or upvoting an idea in the Fabric Ideas Forum using the link below.
    Fabric Ideas - Microsoft Fabric Community


    Hope this helps,
    Thank you.