Dataflow gen 2 not able to access SQL endpoint of Lakehouse

[suidino2]

Hello community. I have built a dataflow as recommended in official website "pattern to incrementally amass data with dataflow gen 2".  (Pattern to incrementally amass data with Dataflow Gen2 - Microsoft Fabric | Microsoft Learn)

I was able to build this dataflow by following the step described in the URL. it was working well until last month.

But probably from last week? One of the query which is basically get the max value from SQL endpoint of lakehouse no longer able to access the SQL endpoint. Company probably changed the tenant policy, but I havent checked with them yet.

My question is, does anyone know what could possibly cause this problem?

The error I am getting right now is as below. I think something is blocking the dataflow gen2 to access SQL endpoint. But if I simply go to the endpoint from Fabric, I can see the table there and I can also query the table without any problem. 

So it seems only the dataflow gen2 can not access the SQL endpoint in lakehouse.

Help please.

[suidino2]

@miguel  thank you for your reply.

If i go to eddit the dataflow, it can list all lakehouse, but it cannot go into the Data column.

Below is the list of Lakehouse, as you can see, the Data column seems not accessable.

# If I go to those lakehouse from the Fabric UI, I can see those table and I can query those table without problem.

[v-cboorla-msft]

Hi @suidino2 

Thanks for uisng Microsoft Fabric Community.

Apologies for the delay in repsonse and inconvenience that you are facing.

Just following up to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

Thanks

[miguel]

please raise a support ticket so an engineer can take a closer look at this.

https://support.fabric.microsoft.com/support

[miguel]

Hi!

What happens when you try to go into the dataflow and edit it? does your query load in there? if not, are there previous steps where the query connects to that endpoint and doesn't fail?

I'd recommend raising a support ticket as it might be something directly happening with your specific Lakehouse