Forum Discussion
Connect to Data Source bug or change?
- 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.
Hi caseybks,
Thank you for reaching out to the Microsoft Fabric Community Forum and for sharing those screenshots that really helps clarify what’s happening. Also, thanks to spaceman127, tayloramy, for those inputs on this thread.
From what you have described, it looks like the connection experience for One Lake and Data Warehouse artifacts in Fabric pipelines has slightly changed. Previously, you could select the artifact directly, but now you’re being prompted to create or select a connection (linked service) first even for items that live inside your One Lake workspace.
This isn’t an issue with your setup it is part of a recent update in Fabric where data pipeline activities now require an explicit connection reference for all data sources, including internal Fabric artifacts. The change helps improve connection reusability, manage permissions consistently, and simplify deployment across workspaces.
To fix or proceed: Open the pipeline and select the Source tab. In the Connection dropdown, either choose your existing linked service (e.g., uk_da_datawarehouse) or create a new one pointing to your Fabric Warehouse. Once connected, you can continue to select your table or use a query as before.
Refer these links:
1. https://learn.microsoft.com/en-us/fabric/data-factory/copy-data-activity
2. https://learn.microsoft.com/en-us/fabric/data-warehouse/ingest-data-pipelines
Hope that clarifies. Let us know if you have any doubts regarding this. We will be happy to help.
Thank you for using the Microsoft Fabric Community Forum.