Cole Tramp's Microsoft Insights

Microsoft Fabric Item Recovery (Soft Delete): What You Need to Know

Written by Cole Tramp | Apr 6, 2026 11:30:00 AM

Overview

As Microsoft Fabric environments mature and become more collaborative, the risk of accidental deletion increases. A data engineer cleaning up a workspace, an analyst removing unused assets, or a contributor misunderstanding dependencies can easily delete the wrong item. Until recently, that deletion was permanent.

Microsoft Fabric now introduces item-level recovery through soft delete, providing a critical safety net for supported Fabric items. This capability complements existing workspace retention and adds fine-grained protection at the item level.

Item recovery allows deleted items to be retained for a configurable period, during which authorized users can restore them or permanently delete them. This feature is currently available in preview and must be explicitly enabled at the tenant level.

Prerequisites and Configuration

Item recovery is disabled by default and requires explicit tenant-level configuration.

To enable item recovery:

    • You must be a Tenant Admin
    • Navigate to Admin portal → Tenant settings → Item Recovery
    • Enable the setting and configure a retention period between 7 and 90 days

If item recovery is not enabled, deleting an individual item results in permanent deletion with no recovery option.

Supported Item Types

Item recovery (soft delete) in Microsoft Fabric applies only to supported item types. When one of these items is deleted and item recovery is enabled, it enters a soft-deleted state and becomes recoverable during the configured retention window. Items not on this list are permanently deleted immediately.

Currently supported item types include:

    • API for GraphQL
    • Copy job
    • Cosmos database
    • Data agent (preview)
    • Data pipeline
    • Environment
    • Graph index (preview)
    • Graph queryset (preview)
    • Healthcare data solutions
    • KQL queryset
    • Lakehouse
    • Map (preview)
    • Mirrored Azure Databricks catalog
    • Mirrored database
    • Mirrored Snowflake
    • ML experiment
    • ML model
    • Notebook
    • Ontology (preview)
    • Operational agent (preview)
    • Real-time dashboard
    • Spark job definition
    • SQL database (preview)
    • User data function
    • Variable library
    • Warehouse
    • Warehouse snapshot

This expanded list reflects Fabric’s continued evolution beyond traditional analytics artifacts, covering data engineering, real-time analytics, machine learning, graph workloads, mirroring technologies, and domain-specific solutions. As Fabric adds new workloads and item types, support for item-level recovery is expected to continue expanding.

Permissions and Access Model

Item recovery respects existing Fabric workspace roles and does not introduce a new security model.

Role-Based Capabilities:

    • Workspace Contributors, Members, and Admins
      • View soft-deleted items
      • Restore items during the retention period
    • Workspace Admins
      • Permanently delete soft-deleted items before retention expires
    • Tenant Admins
      • Enable or disable item recovery
      • Configure and manage the retention period

This model ensures that recovery actions remain aligned with ownership and governance boundaries already defined within Fabric.

What Can Be Recovered

When a supported item is restored within the retention window, it is returned to its original state.

Recovery preserves:

    • Item configuration and settings
    • Data and metadata
    • Permissions and access controls
    • Lineage relationships
    • Endorsements and sensitivity labels

This ensures restored items remain fully integrated into the existing Fabric ecosystem, without introducing security gaps or lineage inconsistencies.

Final Thoughts

Item recovery (soft delete) addresses a long-standing operational gap in Microsoft Fabric by providing protection at the individual item level, not just the workspace level. In collaborative environments with frequent changes, this capability significantly reduces risk and recovery effort.

However, it should be enabled intentionally:

    • Align retention settings with governance and compliance requirements
    • Clearly communicate recovery behavior to workspace owners
    • Understand which items are protected and which are not
    • Avoid treating soft delete as a substitute for formal backup or disaster recovery practices

As Fabric adoption grows and environments scale, item-level recovery moves from a convenience feature to a foundational governance control. Used correctly, it provides resilience without adding operational complexity.

If you’re already using Microsoft Fabric, or considering it, and aren’t sure how you should architect a new design or evolve an existing one, let’s talk.