This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Currently, the Lakehouse destination only supports Organizational account authentication.
This means the destination connection is depending on a specific user's account.
Please make it possible to use Service Principal authentication instead.
By going through the destination settings inside the Dataflow Gen2, I can see that the options for connecting to the various destinations are:
* **Lakehouse**
* Organizational account
* **Warehouse**
* Organizational account
* Service Principal
* **Fabric SQL Database**
* Organizational account
* Service Principal
* **Azure SQL Database**
* Basic (username/password)
* Organizational account
* Service Principal
* Workspace identity
* Note: Basic and Service Principal options can use Azure Key Vault references in this connector.
* **Azure Data Explorer**
* Organizational account
* Service Principal
* **SharePoint**
* Anonymous
* Organizational account
* Service Principal
* Workspace identity
* **Azure Data Lake Storage Gen2**
* Account key
* Organizational account
* Shared Access Signature (SAS)
* Service Principal
* Workspace identity
(Sorry about the bad formatting).
The Lakehouse destination only supports Organizational account - why?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.