This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
When I go to connect to a datasource in a dataflow, the next button is greyed out and it won't let me connect.
This happens with SQL sources and also when try to add a destination to the Lakehouse. I have tried different connections in the connection drop down and different servers and databases and I get the same error. This is for dataflows that are already set up and running. I can connect to a source if I created a new dataflow but then after the flow is saved I can't add a new source.
Solved! Go to Solution.
Hi @erichardison ,
we have tried from our end its working as expected , for your reference i am attaching the screenshot:
can you check with below trouble shooting steps :
Clear browser cache and cookies.
Try incognito/private mode or a different browser.
Sign out and sign in again to Microsoft Fabric.
Ensure the connection has valid credentials and necessary permissions.
Delete and recreate the connection if it’s not working in existing dataflow.
Export the existing dataflow as JSON.
Create a new dataflow and import the JSON file.
Add the new source or destination in the newly created dataflow.
Check for any console errors using F12 developer tools in the browser.
Avoid editing old dataflows created before workspace migration or updates.
Confirm your workspace is not restricted by trial limitations or capacity issues.
If issue still persists, raise a support ticket with Microsoft through the below link :
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Hope this helps !!
If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily.
If you continue to face issues, feel free to reach out to us for further assistance!
Is it a on-premise SQL Database?
If it is, did you set a gateway ?
Because without a gateway, you won't be able to establish a connection between your sql database and Dataflow (you need a bridge between your infrastructure and the cloud)
Hi
Gateway has been set and have tried multiple different gateways. I also run into this same issue when trying to point tables from a gen 2 dataflow to a lakehouse. Lakehouse will show up fine and then the next button is greyed out.
Hi @erichardison ,
we have tried from our end its working as expected , for your reference i am attaching the screenshot:
can you check with below trouble shooting steps :
Clear browser cache and cookies.
Try incognito/private mode or a different browser.
Sign out and sign in again to Microsoft Fabric.
Ensure the connection has valid credentials and necessary permissions.
Delete and recreate the connection if it’s not working in existing dataflow.
Export the existing dataflow as JSON.
Create a new dataflow and import the JSON file.
Add the new source or destination in the newly created dataflow.
Check for any console errors using F12 developer tools in the browser.
Avoid editing old dataflows created before workspace migration or updates.
Confirm your workspace is not restricted by trial limitations or capacity issues.
If issue still persists, raise a support ticket with Microsoft through the below link :
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Hope this helps !!
If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily.
If you continue to face issues, feel free to reach out to us for further assistance!
Hi @erichardison ,
Just checking in on this thread we noticed your issue where the "Next" button remains greyed out when trying to connect to a data source in a Dataflow.
As previously mentioned, this behavior can sometimes be caused if the source database is locked or in exclusive-use mode. If you've already validated that the data source is accessible and you're still facing this issue, we’d recommend raising a support ticket so the backend team can help with deeper diagnostics.
If you're still encountering the problem or need any additional help, feel free to reply here with further details we’re happy to continue assisting.
If we don’t hear back, we may go ahead and close this thread in accordance with our community guidelines. That said, you’re always welcome to reopen the discussion or create a new post if the issue persists in the future.
Thanks again for being an active part of the Microsoft Fabric Community!
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 8 | |
| 8 | |
| 6 | |
| 6 |
| User | Count |
|---|---|
| 24 | |
| 24 | |
| 23 | |
| 19 | |
| 16 |