Fabric Control runs on operational metadata, not your data — and you control how much of that metadata you share. This page is written for the reviewer who has to sign off before you connect anything.
The single most important property of Fabric Control: your data content never leaves your Azure tenant. To do its job, the system reads and reports only operational metadata about your environment — never the contents of it.
Beyond the guarantee that your data never leaves, you also control the metadata that does. There's a small baseline the system needs to function — and above that, what you share is up to you.
A minimal set of operational signals is essential — without it, the product simply can't govern, protect, or recover anything. This baseline is deliberately small and contains no data content.
Richer metadata unlocks deeper insight, but it's your call. You choose how much detail to expose, and you can dial it back at any time — the deeper the picture you allow, the more Fabric Control can do for you.
The trade is simple and always in your hands: the more you share, the more the platform can tell you — but even at the minimum, your data content never leaves your tenant.
You provision access to Fabric Control using credentials you own and control. We never hold master keys to your environment.
Revoking access is yours to do, unilaterally, whenever you choose. The moment you do, Fabric Control's reach into your tenant ends.
Fabric Control operates on operational metadata — your data content never leaves your tenant. You grant the access it needs, and you can revoke it at any time.
Because your data content never leaves your tenant and you control the metadata that does, the hardest questions in a vendor review are already answered.
Nowhere. Your data content stays inside your tenant, and your backups stay in your own storage, under your own keys. There is no data content to trace, because none is transferred.
What we hold is operational metadata — never the contents of your environment. That metadata isn't nothing: names, structure, and configuration can be sensitive, which is why you control how much of it you share. But your data content and your backups stay in your tenant, so the exposure is bounded to the permitted metadata — not the data inside your estate.
These are architectural facts about what does and doesn't move, not policies you have to take on trust:
Because your data content never leaves your tenant — and you control the metadata that does — Fabric Control is well suited to regulated environments. Specific compliance obligations depend on your environment and configuration; talk to us about your requirements and we'll walk through exactly what is and isn't shared in your case.
Then join the waitlist for early access — no card, no data leaving your boundary.