Created this message here after having a call with microsoft support. The behaviour inside a fabric pipeline has recently updated when defining a lakehouse connection. This new approach does not...
Thank you for your reponse. The prior behaviour was that I could use the "Lakehouse ID" inside the Connection field via dynamic content. Now I have to use the "Lakehouse Connection ID", but that works via Oauth / my personal credentials. How does the relation ship work, that this connection is Oauth, and other permissions set inside the lakehouse / workspace?
