Forum Discussion

Padmashri's avatar
Padmashri
New Member
9 months ago
Solved

Authentication Method for lakehouse

In connection type, if lakehouse choosen, OAuth 2.0 is the only available Authentication method. While connection type warehouse have OAuth 2.0 and service principle option in authentication method, why is that?

Is it the case in production environment as well? Does it have OAuth 2.0 only for lakehouse?

 

  • Thankyou, tayloramy, for your response.

    Hi Padmashri,

    We appreciate your inquiry submitted through the Microsoft Fabric Community Forum.

    Based on my understanding, the Lakehouse connector in Power Query or Dataflow Gen2 currently supports only OAuth 2.0 (Organizational Account). This connector surface is designed for interactive authoring, and service principal authentication is not yet available in this user interface. For this reason, you will observe a difference compared with the Warehouse connector, which already supports both OAuth 2.0 and Service Principal authentication. This behaviour is consistent across both development and production environments.

    In other Fabric or Azure Data Factory scenarios, service principals can be used with Lakehouse, but not through the Dataflow (Power Query) Lakehouse UI.

    Please follow the supported Service Principal (SPN) or Managed Identity paths listed below:

    1. Azure Data Factory or Fabric Pipelines → Microsoft Fabric Lakehouse connector. Supports Service Principal and Managed Identity.
    2. Lakehouse SQL Analytics Endpoint or Warehouse SQL Endpoint. Supports Service Principals for SQL based access.

    Additionally, please refer to the links provided below:
    Warehouse Connectivity - Microsoft Fabric | Microsoft Learn
    Copy and transform data in Microsoft Fabric Lakehouse - Azure Data Factory & Azure Synapse | Microsoft Learn

    We hope the information above helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

    Thank you.

5 Replies

  • Thankyou, tayloramy, for your response.

    Hi Padmashri,

    We appreciate your inquiry submitted through the Microsoft Fabric Community Forum.

    Based on my understanding, the Lakehouse connector in Power Query or Dataflow Gen2 currently supports only OAuth 2.0 (Organizational Account). This connector surface is designed for interactive authoring, and service principal authentication is not yet available in this user interface. For this reason, you will observe a difference compared with the Warehouse connector, which already supports both OAuth 2.0 and Service Principal authentication. This behaviour is consistent across both development and production environments.

    In other Fabric or Azure Data Factory scenarios, service principals can be used with Lakehouse, but not through the Dataflow (Power Query) Lakehouse UI.

    Please follow the supported Service Principal (SPN) or Managed Identity paths listed below:

    1. Azure Data Factory or Fabric Pipelines → Microsoft Fabric Lakehouse connector. Supports Service Principal and Managed Identity.
    2. Lakehouse SQL Analytics Endpoint or Warehouse SQL Endpoint. Supports Service Principals for SQL based access.

    Additionally, please refer to the links provided below:
    Warehouse Connectivity - Microsoft Fabric | Microsoft Learn
    Copy and transform data in Microsoft Fabric Lakehouse - Azure Data Factory & Azure Synapse | Microsoft Learn

    We hope the information above helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

    Thank you.

  • Hi Padmashri,

    We would like to follow up and see whether the details we shared have resolved your problem. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.

    Thank you.

    • Padmashri's avatar
      Padmashri
      New Member

      Hi,

      This answers my question and my problem is resolved.

      Thank you! 

       

  • Hi Padmashri,

    Thank you for the update. We are glad the issue has been resolved.

    Please continue to use the Microsoft Fabric community for any further queries.

    Thank you.