Microsoft Fabric Updates Blog

Dropped warehouse recovery in Microsoft Fabric (Preview)

When an accidental drop isn’t the end anymore

The morning has been productive. All deployments are proceeding as expected, and the dashboards are currently operational. Then a message lands:

“Why can’t I see the Marketing reports?”

You open the Fabric workspace—and the Marketing NY Taxi Warehouse is gone.
In traditional warehouses, this is where panic starts: restore jobs, pipeline replays, missed SLAs, and the dreaded question— “How long until it’s back?”

With Fabric, the story unfolds differently.

With Fabric Data Warehouse, this moment doesn’t spiral into chaos. It becomes a near-instant recovery event. Instead of launching complex restore workflows, you simply reach out to a Fabric Workspace Administrator and share one detail: the name of the dropped warehouse.

The administrator navigates to the Workspace Recycle Bin, where Fabric automatically lists all dropped data warehouses—along with their associated snapshots. They select Marketing NY Taxi Warehouse, then Restore. Seconds later, the warehouse reappears.

Not just the shell—but everything:

  • Tables schemas and data
  • Warehouse snapshots
  • Permissions and security
  • Saved queries, views, and stored procedures

Example: warehouse recovery in action

Figure: From drop to restore in minutes.

No manual rebuilds.
No copy jobs.
No restore pipelines.
No multi‑hour outage.
No data loss.

Just a quiet return to normal—and a powerful lesson in modern data resilience.

How did this work?

Because the data was never immediately deleted.

Microsoft Fabric automatically retains dropped data warehouses for a configurable retention period—quietly without any intervention.

Within the tenant‑configured retention window (anywhere from 7 to 90 days, with 7 days as the default), a Workspace Administrator can restore the warehouse to the exact state it was in before the drop.

No pre‑planning required.
No backups to manage.

Why does this matter in the age of AI?

Accidental drops can happen anytime—ETL moves fast, schemas change, and mistakes happen. What matters is how fast and predictably you recover.

Fabric is designed so recovery is:

  • Fast
  • Stress‑free
  • Boring (in the best way)

The takeaway

The Fabric warehouse recovery story is one of resilience by design.

Resilience isn’t about assuming failure is inevitable—it’s about building with foresight so when the unexpected happens, you have a trusted, well-defined path to recover quickly and confidently.

Explore the ability to recover your dropped Fabric Warehouses and share your valuable feedback.

To learn more, refer to the manage workspaces documentation.

Related blog posts

Dropped warehouse recovery in Microsoft Fabric (Preview)

April 14, 2026 by Tzvia Gitlin Troyna

As Microsoft Fabric continues to converge analytics experiences across workloads, one of the most important steps forward is reducing friction in how users move from raw data to insights. With the latest integrations, the Eventhouse Endpoint is now deeply embedded into the “Analyze data with” entry points across Lakehouse, Data Warehouse, and Eventhouse, bringing a … Continue reading “Unifying “Analyze data with” analytics across Fabric (Preview)”

April 13, 2026 by Twinkle Cyril

Schema evolution is a fact of life for modern analytics platforms. As data models grow, teams need to add columns, drop unused fields, and evolve constraints—often as part of tightly controlled deployment pipelines. Fabric DW supported transactional execution for key table‑focused DDLs like CREATE TABLE, DROP TABLE, TRUNCATE TABLE, CTAS and sp_rename—with this release, ALTER … Continue reading “ALTER TABLE inside explicit transactions in Fabric Data Warehouse (Generally Available)”