Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Yesterday I tried to delete some old test Lakehouses and was met with the error "This item couldn't be deleted. Please try again later." I'm able to delete other objects as normal. As a test I created a brand new Lakehouse using one of the sample datasets and I cannot delete this one either. I also tried this in my personal Fabric trial tenant where I'm a full admin. Again, I can't delete a Lakehouse.
The two different tenants are in West US and South Central US(Texas).
Is anyone else having this issue?
Solved! Go to Solution.
Update: If I first delete the one-time pipeline used to populate the Lakehouse, I'm able to delete the Lakehouse. It's like Fabric sees that something is connected to the Lakehouse and won't let me delete it. Is this expected behavior?
I tested again by creating a Lakehouse with a copy data pipeline, and a completely blank Lakehouse. The blank Lakehouse deleted with no problem. The other lakehouse would not delete until I deleted the associated pipeline first.
Hi @Anonymous ,
We have a bug filed, to delete the LH & WH upon deletion of the last.
Ideal workaround is to create a new Workspace as we cannot delete the stagging artifacts manually.
If in your case if that will not work, I request you create a support ticket so the team will be looking into this issue more closely.
Once you have a SR# , please do share that here, so that we can keep an eye on the same.
Hope it is helpful.
Hi, thanks for the answer.
Unfurtunately, for us it wouldn't be an option to delete the workspace, we would have downtime for our PowerBI reports and this wouldn't be accepted. Right now, we created one "Test Flow" to somehow mitigated the 3 artificats that show up, if no other objects are created, it's the best of the worst of what I could come up with.
Where can I follow along this ticket, that would fix this? And would it be fixed also for users that have this issue or only those that will encounter this in the future?
Hi @Anonymous ,
I suggest you create a support ticket so the team will be looking into this issue more closely.
Once you have a SR# , please do share that here, so that we can keep an eye on the same.
Hi
Same problem here : cannot delete Lakehouse and cannot understand how to delete dependencies
How can I fix this issue ?
Thanks
Update: If I first delete the one-time pipeline used to populate the Lakehouse, I'm able to delete the Lakehouse. It's like Fabric sees that something is connected to the Lakehouse and won't let me delete it. Is this expected behavior?
I tested again by creating a Lakehouse with a copy data pipeline, and a completely blank Lakehouse. The blank Lakehouse deleted with no problem. The other lakehouse would not delete until I deleted the associated pipeline first.
Hi @Anonymous ,
Thanks for using Fabric Community.
Yes it is as per design in order to prevent the deletion of services when there are dependent items.
Hope this is helpful. Please let me know incase of any queries.
I have the same issue, can't delete lakehouse but there is no active dataflows for it.
Same issue for me too. I removed all lakehouses in my notebooks and then I was able to delete the renamed lakhouse.
Hi @Anonymous ,
We haven’t heard from you on the last response and was just checking back to see whether my response provided some insights. Otherwise, will respond back with the more details and we will try to help .
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
66 | |
36 | |
15 | |
14 | |
5 |
User | Count |
---|---|
71 | |
65 | |
26 | |
8 | |
7 |