Forum Discussion

caseybks's avatar
caseybks
Advocate III
9 months ago
Solved

Connect to Data Source bug or change?

Hi, just since yesterday, I'm now being asked to create a new connection to artifacts within my OneLake.       Where as previously, you'd just select the artifact.   both ...
data engineering
Data Pipeline
Environment
Lakehouse
  • tayloramy's avatar
    tayloramy
    9 months ago

    Hi caseybks, 

     

    I believe this is a recent service change. I very much like this change as it allows us to create a connection using a service account or service principal, meaning that it is not tied to an individual's credentials, and won't break if that individual leaves the org. 

     

    If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

spaceman127's avatar
spaceman127
Super User
9 months ago

Hi,

 

Same thing happened to me.

 

Best regards 

caseybks's avatar
caseybks
Advocate III
9 months ago

I think it's as tayloramy said, with the recent introduction of being able to use service account OAuth authentication or service principals in connections to OneLake artifacts. Which I did see in the updates, but I either missed or it wasn't explained enough what the impact or change would be to how we connect to OneLake artifacts in pipeline activities. 

 

I went through every pipeline/ activity last night and updated them to use a connection authenticated by a service account 😅

 

In the long run this has actually helped when using git integration, and branching from develop branch. We were having rendering issues in branched workspaces, with OneLake Artifacts not being found errors, but now that seems to have sorted it out.