Allow recovery of artifacts that have been deleted from a workspace; dataflows, pipelines, notebooks, etc.. Have a recycle bin per workspace for quick navigation & recovery.
5 Comments
- nishalitNew Member
When an item gets deleted (Lakehouse, Warehouse, Notebook, Report, Pipeline, etc.) it should go to a recycle bin first.
It should stay there for some days before it gets completely deleted. I suggest 14 days as a good time period. Or it can be adjustable time period.
This way, if someone accidentally deletes an item, it will be possible to recover the item and it's data.
It should also be possible to delete an item from the recycle bin to completely delete the item, in order to avoid unnecessary storage costs.
There should be a recycle bin for each workspace. The workspace members can recover items from the recycle bin.
If a workspace gets deleted, it should be possible for the Fabric Admin or Capacity Admin to recover the workspace.
- sakshi399
Microsoft Employee
We are evaluating this idea and its timeline along with other priorities. Your comments and votes will help us plan and design the feature. Thank you for your feedback! - fbcideas_migusrNew MemberStatus added:Under Review
- SJCuthbertson
Advocate I
A related point (I'm not sure it's worth a separate Idea?) that I saw in r/MicrosoftFabric today, was that the act of deleting items should work like deleting a repo in Azure DevOps or GitHub. Specifically, it's a two step process. You have to click a delete button that is clearly marked as "this is dangerous!" and separated from other things in the UI. THEN you have to type in the name of the thing you want to delete, before you can click to confirm. Deleting things in Fabric UI should be this hard. Perhaps not everything: if git is enabled for the workspace, then deleting code-only objects like pipelines and notebooks could be streamlined. But deleting items in a non-git workspace, and deleting lakehouses/warehouses/eventhouses anywhere, needs this added protection. - yicw
Microsoft Employee
Status changed:Under ReviewtoPlanned
Recent ideas
Support Clustered Columnstore Tables with Nonclustered Primary Keys in Fabric Mirroring
Microsoft Fabric Mirroring should support source tables that use a Clustered Columnstore Index (CCI) when the table has a valid nonclustered primary key that can be used to uniquely identify rows. T...jasonhorner4 hours agoRegular VisitorNew4Views0likes0CommentsRequesting Security Control at Folder Level
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Fabric currently provides security controls at the Workspace and Item le...aravindhkdoss4 hours agoRegular VisitorNew5Views0likes0CommentsSupport Views in Microsoft Fabric Mirroring for Azure SQL Database and SQL Server
Microsoft Fabric Mirroring should support database views as mirrored objects, specifically for Azure SQL Database and SQL Server sources. Today, Fabric Mirroring primarily operates against physical ...jasonhorner5 hours agoRegular VisitorNew4Views0likes0CommentsConvert Classic Lakehouse to Schema-based
I created a lakehouse back in November last year. I believe it was while schema-enabled lakehouses were still in Preview. I understand that currently there isn't a way to convert the classic lakeho...hallmarke147 hours agoFrequent VisitorNew11Views0likes0Comments