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
Power Query Parameter create/use when connecting to a dataflow
In power query when you connect to a table in a dataflow there are no options to create or use a parameter for that dataflow. When connecting to SQL there is an option when setting up the connection ...ben_holmes57 minutes agoNew MemberNeed Clarification202Views3likes2CommentsMake Copilot Approval status for semantic model available through API
In recent versions fabric allowed to mark a semantic model as approved for copilot to reduce AI adoption friction. However there is no specific way for external governance application to analyse whi...FrançoisD1 hour agoFrequent VisitorNew2Views0likes0CommentsClone a workspace, including its data, to a new workspace
Description: Today there's no way to fully clone a Fabric workspace: git sync and Deployment Pipelines move item definitions only, not the underlying data; Warehouse's zero-copy CREATE TABLE ... AS ...gclements2 hours agoHelper IINew7Views1like0CommentsAllow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara7 hours agoNew MemberNew7Views0likes0CommentsSupport Synonyms in Fabric Warehouse
Microsoft SQL Server has a very powerful feature by the way of "synonyms." It allows users and DBAs to do all sorts of powerful magic such as rewiring objects under the hood (e.g. run the code agains...matthias-bi11 hours agoRegular VisitorNew1.3KViews18likes2Comments