You could build this yourself. Here's why you shouldn't.
Microsoft Fabric ships strong native administration, governance, and retention-based recovery. What it doesn't give you is one operational layer across the whole estate: a versioned backup you hold, one view of the estate's state and history, and recovery you have tested. Your options for that layer are DIY, a patchwork of scripts, or Fabric Control. Here's the honest comparison.
What people do instead, and where it hurts
Do nothing
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.
Script it yourself
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.
Stitch together tools
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.
Who operates what
Microsoft runs the platform. You own the estate. Fabric Control operates the layer in between, and it stays yours as the platform keeps changing underneath.
Six questions to ask of any route
Native tooling, your own scripts, or a product: the answers show you where the gaps are. The guides carry the detail, with dates.
Can you restore to a point in time you choose, into another capacity, or a single table?
Recovery that only puts an item back inside the platform's retention window isn't a backup. How to back up a Fabric lakehouse
Do you hold an independent copy, in storage you control, that outlives the platform's retention windows?
Durable data isn't a recovered environment. Fabric disaster recovery: covered vs. not
Can you see the whole estate's operational state at once?
One live view, instead of a screen per workspace. How to monitor your Fabric estate
Can you see who has access to what, across every workspace, in one place?
The answer should take a minute, not an afternoon. Who has access to what in Fabric
Can you prove to an auditor who changed what, and that your data stayed put?
An evidence trail, not an assurance. Fabric Control works on operational metadata only; your data content never leaves your tenant. How the boundary works
Who maintains it as Fabric changes, and what does that cost you?
Scripts are yours forever. Fabric Control's governance tier is $0 for one Azure tenant; Backup and Operations are flat fees. Pricing
What makes Fabric Control different
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.
Purpose-built for Fabric
Not a generic tool pointed at Fabric. It understands workspaces, capacities, semantic models, and pipelines natively, because it was built for them.
Your data never leaves your tenant
Metadata-only egress is enforced by architecture. You can hand the design to a security reviewer and it holds up.
Free forever, honest to stay
A real free tier for your own tenant, forever. No feature clawback, no expiring clock, no dark patterns.
Your operational history is retained
Fabric Control keeps the operational history it collects, a year of it on the free tier, so the record of what existed and who had access is there when someone asks.
Provable, not promised
Governance you can demonstrate to an auditor with an evidence trail: who changed what, and that data stayed put.
You hold the keys
Access is granted by you and revocable by you at any time. Once a revocation takes effect, our reach ends.
Stop maintaining plumbing. Start governing.
Free forever for one Azure tenant, no card. The beta is open; early adopters get Backup free for 3 months.