Microsoft Fabric ships strong native administration, governance, and retention-based recovery — but not the unified operational control plane: independent versioned backup, historical evidence, and cross-estate continuity. Your options for that gap are DIY, a patchwork of scripts, or Fabric Control. Here's the honest comparison.
Rely on the native portal and hope. Works until the day a workspace vanishes, a refresh silently fails for a week, or an auditor asks a question you can't answer.
PowerShell and the Fabric APIs can do a lot. But now you own a backup system, a logging pipeline, and a monitoring tool — forever. Every Fabric update is your maintenance burden.
Bolt a generic backup tool to a generic log aggregator to a generic monitor. None of them understand Fabric, so you spend your time translating between them.
Most teams start by asking whether the native tools are enough. Here's the honest answer, alongside the DIY route.
| Capability | Microsoft native | DIY scripts | Fabric Control |
|---|---|---|---|
| Unified operational estate view | Scattered across Admin Portal, OneLake Catalog & Capacity Metrics | Build & maintain | One control plane, free |
| Metadata-only egress guarantee | Not applicable | Your responsibility | Architectural |
| Historical CU trend & throttling detection | ~10–15 min latency, 14-day compute window | Build the KQL yourself | 60-day, live |
| Restore a deleted workspace or item | Recycle bin — up to 90 days, in place | Hand-rolled | From a versioned backup, any point in time |
| Restore into another capacity, or an object/table elsewhere | No — recycle bin is in-place only | Build it | Whole backup or a single table, anywhere |
| Independent copy you own (survives expiry & region loss) | No — stays in the estate, expires | If you build it | Your storage, your keys |
| Centralized pipeline logging | No unified engine | Build the engine | One API call |
| SLA blast-radius simulation | Not offered | Effectively impossible | Operations tier |
| Maintenance as Fabric evolves | Microsoft owns it | You own it forever | We own it |
| Time to first value | Immediate, but partial | Weeks to months | Minutes, free |
Microsoft's Capacity Metrics App shows a rolling 14-day compute window at roughly 10–15 minute latency. Fabric's recycle bin undeletes a workspace or item within a retention window, in place — useful, but not a versioned backup you hold, and it can't restore to an earlier point, into another capacity, or an object at a time. Governance is not recoverability, and a label is not a restore plan.
Microsoft operates Fabric. Fabric Control operates your Fabric estate — the governance, backup, and continuity layer on top, that stays yours as the platform keeps changing underneath.
Not a generic tool pointed at Fabric. It understands workspaces, capacities, datasets, and pipelines natively — because it was built for them.
Metadata-only egress is enforced by architecture. You can hand the design to a security reviewer and it holds up.
A real free tier for one tenant, forever. No feature clawback, no expiring clock, no dark patterns.
Fabric Control keeps the operational history it collects, per your retention policy — so when cross-tenant aggregation ships, your record is already there.
Governance you can demonstrate to an auditor with an evidence trail — who changed what, and that data stayed put.
Access is granted by you and revocable by you at any time. Revocation ends our reach immediately.
Free forever for one Azure tenant, no card. Join the waitlist for early access.