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
Dynamic Batch Count in Data Factory Pipelines (FOREACH ACTIVITY)
Currently, in Data Factory, the ForEach activity requires a static batch count when executing in parallel mode. However, this fixed value does not always align with dynamic workloads, leading to inef...raym8538 minutes agoAdvocate INew1.4KViews10likes2CommentsDeployment Pipelines: preserve/override schedules per environment (no overwrite on deploy)
When deploying from Dev/Non-Prod to Prod, the target’s pipeline schedule is overwritten. Please add deployment rules (or an opt-out) so schedules can be environment-specific without showing as drift ...JP89913 hours agoKudo CommanderUnder Review4KViews66likes22CommentsSupport Power BI connection with Salesforce community URL
Before Salesforce changed customer links to my.site.com our customers were able to connect salesforce with power bi and use their own logins in Power BI and maintain the security from Salesforce. No...gilmore_staci8 hours agoHelper IIINew4Views0likes0CommentsShow all email recipients when sending subscription
When a subscription is sent out, the recipients can only see themselves and not everyone who received that subscription. We would like the subscription to show everyone who received that subscription...jhawkfan9 hours agoNew MemberNew4Views0likes0CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen9 hours agoAdvocate IVNew429Views72likes4Comments