Forum Discussion
Destination Connection dropdown changed
Hi epfingsten,
Service Principal authentication is not supported for Lakehouse connections today. Only OAuth (user identity) is available. Service Principal is supported for Warehouse connections, not Lakehouse.
If you want a “generic” connection, your only current option is to create it under a shared user account (not a Service Principal) and use that connection in pipelines.
Thanks & Regards,
Prasanna Kumar
Hi epfingsten,
As lbendlin mentioned, this was a recent service change. You can now explicitly set the connection to use, previously it used a default connection tied to your account in the backend. Now you cna make an explicit connection using a sesrvice account or service principal, so that it is no longer tied directly to your user.
Overall this is a very good change, being able to map this to a specific connection isntead of always mapping it to your credentials is a great feature.
If you found this helpful, cosnider giving Kudos. If I solved your problem or answered your question, mark this post as a solution.
Does anyone know how to do this using a service account or service Principal? I still can't find anything
Hi epfingsten,
My apologies, it looks like Lakehouse connections only support oauth right now. I was confusing them with warehouse connections that support both.
Hopefully service principal support for lakehouse connections will come eventually.
If you found this helpful, cosnider giving Kudos. If I solved your problem or answered your question, mark this post as a solution.
Hi epfingsten,
Service Principal authentication is not supported for Lakehouse connections today. Only OAuth (user identity) is available. Service Principal is supported for Warehouse connections, not Lakehouse.
If you want a “generic” connection, your only current option is to create it under a shared user account (not a Service Principal) and use that connection in pipelines.
Thanks & Regards,
Prasanna Kumar
