Unexpected behavior with Microsoft Fabric Lakehouse shortcut after unlinking Dataverse

[Lado_Kvara]

I encountered unexpected behavior when working with a lakehouse shortcut connected to Dataverse via Power Apps.

Initially, my lakehouse (LH_1) in Fabric wasn’t syncing properly with the source data. To fix this, I unlinked the Microsoft OneLake (Azure Synapse Link for Dataverse) connection in Power Apps, expecting the corresponding LH_1 lakehouse in Fabric to be removed automatically — but it wasn’t.

Then, I created a new OneLake link in Power Apps. As expected, a new Dataverse-linked lakehouse was created in the same workspace. Surprisingly, the original LH_1 lakehouse, which was no longer linked in Power Apps, began showing up-to-date data, even though its Dataverse link no longer exists.

I deleted the newly created lakehouse, but the original LH_1 continues to function and still appears to be syncing data.

Has anyone else experienced this?
Any ideas why LH_1 still works despite the original Dataverse link being removed?

[GilbertQ · Accepted solution]

Hi @Lado_Kvara 

What could happen in this case is when a dataverse link to fabric is created automatically uses the same lake house under the hood, and that is why it is appearing to sink even though you have deleted it. Not only recommendation if this continues is to contact Microsoft support because they'll have to look in their back end. To fix this issue for you.

[v-tejrama · Accepted solution]

Hi @Lado_Kvara,

Thanks for reaching out to the Microsoft fabric community forum.

It seems like what’s happening is that even though you removed the Dataverse link in Power Apps, the lakehouse shortcut in Fabric didn’t get deleted automatically.

That’s why you’re still seeing it there. Also, when you created the new Dataverse link, it probably reused the same storage behind the scenes, which is why the old lakehouse started showing fresh data again even though it looks like it shouldn’t.

Sometimes this happens because of how things connect in the background, or due to a delay in updates between Power Apps and Fabric. The best thing to do is go into Fabric and manually check your lakehouse shortcuts.

If you still see the old one, you can delete it yourself.

And if the issue keeps happening, I’d suggest contacting Microsoft Support. They can check the backend properly and make sure everything is cleaned up.

If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it.

Best Regards,
Tejaswi.
Community Support

[Poojara_D12 · Accepted solution]

Hi @Lado_Kvara 

What you're experiencing with the lakehouse (LH\_1) continuing to sync data from Dataverse even after the Azure Synapse Link was removed in Power Apps is an unusual but not entirely unexpected behavior due to how Microsoft Fabric handles OneLake shortcuts and underlying data caching. When you unlink a Dataverse environment in Power Apps, it typically removes the OneLake connection, but it doesn’t immediately delete or disable the shortcut or cached data in the associated lakehouse within Fabric. In many cases, the underlying delta tables or files in OneLake remain intact and accessible, especially if they were cached or replicated to your region. Furthermore, when you created a new OneLake link, Fabric may have reconnected or refreshed underlying metadata or shortcuts in LH\_1 due to shared resource references or internal identifiers being reused across link sessions. Even after deleting the newly created lakehouse, the persistence of syncing behavior in LH\_1 suggests that the data refresh mechanism (likely a background pipeline or trigger from Dataverse) wasn't fully disconnected at the Fabric end. This may point to a delayed or incomplete cleanup of metadata or linked services by the platform. Other users have occasionally reported similar issues, indicating a need for more transparent lifecycle management and synchronization between Power Apps and Microsoft Fabric lakehouses. Until Microsoft addresses this more robustly, it's a good idea to manually inspect the lakehouse storage (e.g., using OneLake explorer or monitoring pipelines in Fabric) to confirm what processes or links might still be active under the hood.

[v-tejrama · Accepted solution]

Hi @Lado_Kvara,

Thanks for reaching out to the Microsoft fabric community forum.

It seems like what’s happening is that even though you removed the Dataverse link in Power Apps, the lakehouse shortcut in Fabric didn’t get deleted automatically.

That’s why you’re still seeing it there. Also, when you created the new Dataverse link, it probably reused the same storage behind the scenes, which is why the old lakehouse started showing fresh data again even though it looks like it shouldn’t.

Sometimes this happens because of how things connect in the background, or due to a delay in updates between Power Apps and Fabric. The best thing to do is go into Fabric and manually check your lakehouse shortcuts.

If you still see the old one, you can delete it yourself.

And if the issue keeps happening, I’d suggest contacting Microsoft Support. They can check the backend properly and make sure everything is cleaned up.

If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it.

Best Regards,
Tejaswi.
Community Support

[GilbertQ · Accepted solution]

Hi @Lado_Kvara 

What could happen in this case is when a dataverse link to fabric is created automatically uses the same lake house under the hood, and that is why it is appearing to sink even though you have deleted it. Not only recommendation if this continues is to contact Microsoft support because they'll have to look in their back end. To fix this issue for you.