Destination Connection dropdown changed

[epfingsten]

I have several Data Pipelines with multiple Copy Data Activities.

Yesterday afternoon something suddenly changed. On some of my Copy Data Activities, the destination Lakehouse was different than what it should have been, and the option to select it from the Connection Dropdown disappeared. I went to Browse All and found my lakeouse, but then the Destination dialogue changed, now with a Connection and Lakehouse dropdowns.

The Connection now reads "Lakehouse MyFirstName.MyLastName" and my lakehouse shows up in the Lakehouse dropdown.

Questions:
1. Why would it have happened?
2. If I have to change all my Copy Data activities to the new format, fine, but why is it tied to my name?
3. Is there a way to change the connection to something generic, like "Lakehouse Service.Account?"

What it was:

What it changed to (by itself, without me changing it):

What it now looks like after browsing to find my lakehouse:

[v-pgoloju]

Hi @epfingsten,

Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[v-pgoloju]

Hi @epfingsten,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @lbendlin and @tayloramy  for prompt and helpful responses.

Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[tayloramy]

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. 

[epfingsten]

Does anyone know how to do this using a service account or service Principal? I still can't find anything

[tayloramy]

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. 

[lbendlin]

there was a service version change to 13.0.26909.24 that has propagated to your tenant and likely caused this.