Five short films about Fabric Control
Each film runs three minutes. The captions are in the picture, and the full transcript of each one sits beside it.
Value, without giving up control
See more. Decide better. Stay in control.
Transcript of Values
You invested in Microsoft Fabric to turn data into decisions. But how much of your team's day goes into figuring out what's happening behind those decisions?
Fabric Control is built to help you get more value from that investment. Not by replacing Fabric, but by making your estate easier to understand, while keeping you in control.
Start with visibility. As workspaces and workloads multiply, so do the questions. What needs attention? What changed? Fabric Control brings operational information together, so your team can spend less effort piecing the picture together, and more effort deciding what to do next.
Then, put capacity in context. Usage patterns and cost insights help you ask better questions before making your next resource decision. Is demand growing? Is the pressure recurring? The value isn't another chart. It's a more informed conversation about where your investment goes.
Context matters when something needs attention, too. A capacity isn't just a technical resource. People and workloads depend on it. Seeing those relationships helps your team investigate with the wider picture in mind, and put attention where it matters.
But useful visibility shouldn't require handing over the keys. Fabric Control's worker is designed to run inside your environment, with credentials kept under your control. That's a product principle with a practical purpose: clearer oversight, without making someone else the owner of your estate.
And clarity means being honest about what you know. A collected snapshot isn't the same as a live reading. Missing information isn't zero. Those distinctions matter, because a confident decision needs context, not just a reassuring colour on a screen.
The goal is to give the people responsible for Fabric a shared place to understand it. Operators can investigate. Leaders can discuss priorities. Administrators can review the estate. The software supports their judgment; it doesn't replace it.
You also choose what fits. Governance, Operations, and Backup address different needs. Operations doesn't require Backup. That separation lets the conversation start with the problem you're trying to solve, rather than a bundle you're expected to accept.
Microsoft provides the platform. Your team remains responsible for how its estate is run. Fabric Control adds an operational layer to help you connect those responsibilities with a clearer picture, and turn that picture into informed action.
That's the connection between value and values. Make the work clearer. Respect ownership. Give people better context. Help your team focus on the decisions that move the business forward.
Fabric Control. See more. Decide better. Stay in control. Explore what fits your estate at ddsfabriccontrol.com
Security starts with control
Understand the boundary. Review the access. Stay in control.
Transcript of Security
You want a clearer view of your Microsoft Fabric estate. But adding another tool shouldn't mean accepting a boundary you don't understand. Before you connect it, you need answers.
With Fabric Control, the security conversation starts with control. Understand where the worker runs. Review what it can access. Know what crosses the boundary. Those questions make the documented design meaningful to the people responsible for your environment.
The collection worker is designed to run in your own Azure environment, using a managed identity you control. That separates the worker's access inside your estate from the Fabric Control platform, rather than asking you to hand over a tenant login.
And setup is not the same as day-to-day operation. The person installing the worker and the identity running it have different responsibilities and different permissions. Review them separately. The access needed to create resources shouldn't be mistaken for the access used to collect information.
The documented baseline inventory access is read-only. But read-only still has a scope, and optional capabilities can need additional permissions. Make those choices deliberately. Decide what you need to see, understand the access it requires, and review any broader grants.
The connection model matters, too. The documented worker initiates outbound HTTPS connections; it doesn't require an inbound firewall opening. Your team can review the destinations and inspect that traffic with its own tooling. The boundary should be something you can examine, not just a reassuring diagram.
Be equally clear about information sharing. Operational metadata is transferred to Fabric Control, and optional collection settings can extend what is sent. Review the transfer inventory before enabling them. A useful security decision covers what crosses the boundary, not only where the worker runs.
Control also means deciding who can operate the worker. Access to start its job can provide access to its secrets and identity. Keep that access deliberate, and use protected secret handling rather than putting secrets in ordinary configuration. Ownership comes with responsibilities worth making explicit.
The toolkit documentation gives your team things to check: published download checksums, a read-only preflight, and guidance for inspecting the environment and its connections. Use those checks as evidence for your review, not as a replacement for your security policies.
Think about leaving before you start. Closing your organization on the platform and removing resources from your tenant are separate actions. Your team removes the worker resources and associated grants. Cancellation alone doesn't remove that infrastructure or stop its Azure charges. Plan the exit as deliberately as the installation.
And distinguish documented design from a verified deployment. Source documentation is a starting point, not proof of your installation. Ask what has been checked, understand what remains unverified, and validate the result against your own requirements.
Fabric Control. Understand the boundary. Review the access. Stay in control. Start the conversation at ddsfabriccontrol.com
Confidence you can examine.
Clearer questions. Better-informed decisions.
Transcript of Transparency
A confident decision starts with a question: what is this based on? A clear result helps. But without context, even a polished report can leave your team guessing about what it really means.
That's the transparency goal behind Fabric Control: confidence you can examine. Not simply another view of Microsoft Fabric, but a clearer conversation about the evidence, the boundaries, and the decisions that remain yours.
Start with scope. Before using a result, ask which environment and collection it represents, and what access was available. A useful view has boundaries. Understanding them helps you judge whether it answers the question you're actually asking.
Next, ask how current the information is. Fabric Control's refresh controls can distinguish when a view was updated from when its information was collected, where that timing is available. A fresh page is not automatically a fresh picture of your estate.
Then read the status, not just its color. The toolkit's preflight guide distinguishes a passed requirement, a failed requirement, an optional area that's off, and something it could not verify. Unknown is not the same as healthy.
That distinction gives the next conversation a firmer starting point. The guide identifies which requirement needs attention; it does not claim to diagnose the cause. Your team can investigate the right question without mistaking a label for an explanation.
Transparency also means understanding the product's boundaries before you approve it. The transfer inventory describes what is sent, why it is needed, and what is required or optional. Review those choices and their limits against your organization's requirements.
The toolkit gives reviewers something concrete to examine: readable setup scripts, documented permissions, and a published download fingerprint to compare. These are ways to check a claim, not a substitute for your own review or evidence that every risk has disappeared.
The documentation also states what has not yet been verified against an observed installation. A written design, a passed check, and evidence from your environment are different things. Being explicit about that difference makes the approval conversation more honest.
The same clarity matters when you leave. The removal guide distinguishes closing your organization from removing resources in your tenant. Closing does not perform that cleanup for you. Your team needs a deliberate removal plan, including access and any remaining costs.
For leaders, operators, and administrators, the value is a shared basis for decisions: what we know, what we still need to check, and who takes the next step. Transparency doesn't replace judgment. It gives judgment something clearer to work with.
Fabric Control. Confidence you can examine. Clearer questions. Better-informed decisions. Start the conversation at ddsfabriccontrol.com.
Less hunting. More clarity.
Make the next step easier to find.
Transcript of Ease of Use
You open a tool to answer a question, not to learn another maze. Where do I start? Which view do I need? What does this result mean? Everyday administration is easier when the next step is clear.
That's the ease-of-use goal behind Fabric Control: useful entry points, focused views, and guidance for the operational side of Microsoft Fabric. Less hunting for where to begin. More attention on the work itself.
Start with a familiar question: who has access to this workspace? Search can help you find a relevant page or an available estate item, rather than remembering every navigation path. It's a starting point for your review, not a guarantee that every answer is already there.
Then narrow the question. Workspace access views include search and filtering to focus your review, rather than treating the whole estate as one long list. The aim isn't more information. It's making relevant information easier to examine.
Keep context close to the question. Review the available information, check its scope, and consider how current it is before deciding. Refreshing a page is not the same as collecting a new picture of the estate. A simpler workflow still needs that distinction.
And when you need an explanation, guidance should be close at hand. Fabric Control includes contextual page help, and the client portal provides readable setup and operating guides. Your team has somewhere to look for the next step, without relying on memory alone.
Different people arrive with different responsibilities. Dashboard entry points are organized for administrators, operators, managers, and viewers. Each role gets a relevant starting point. Access still depends on permissions and enabled capabilities.
Getting started should be understandable too. The worker toolkit documents prerequisites, download verification, preflight checks, and setup steps. This is guided technical setup, not a promise of one-click installation. Your organization still supplies the right tools, permissions, and decisions for its environment.
The preflight guide also explains how to read the result: a requirement can pass, fail, be marked optional and off, or remain unverified. Unverified is not a pass. Knowing which requirement needs attention helps frame the next conversation, even when the underlying cause still needs investigation.
You don't have to approach every operational concern at once. Governance, Operations, and Backup are separate offerings, and Operations can stand on its own. Start with the task you need to improve, then evaluate the capabilities and setup that make sense for your team.
That's the practical meaning of ease of use: find a starting point, focus the question, understand the context, and choose a deliberate next step. Not removing the expertise your estate needs. Giving that expertise a clearer way to work.
Fabric Control. Less hunting. More clarity. Make the next step easier to find. Start the conversation at ddsfabriccontrol.com.
Close the gaps between knowing and acting
See the gaps. Connect the context. Take the next step.
Transcript of Closing Gaps
Your team has dashboards, scripts, and plenty of information. So why can a simple question still turn into a search across screens? The problem isn't always missing data. It's the gaps between the answers.
Fabric Control is designed to help close those gaps across your Microsoft Fabric estate. Not by replacing the platform, but by bringing operational context into the conversation. So your team can move from scattered signals toward informed decisions.
Start with the visibility gap. What are we responsible for? Fabric Control brings collected estate information into inventory views. Use that starting point to review your environment, while checking the collection scope and how recently the information was gathered.
Then consider the access gap. Knowing a workspace exists isn't the same as understanding who can use it. Workspace access views help you review roles and principals, so access becomes something your team can examine rather than simply assume.
Capacity raises another question: is this a passing spike, or a pattern worth investigating? Capacity insights bring collected usage into view over time. That context can support a better conversation about workload and sizing, without turning a chart into a guaranteed saving.
There's also a gap between seeing an item and understanding its connections. Available data-source and gateway information gives your team another place to look. Use those connections to guide investigation, while confirming relationships and dependencies that the collected information doesn't establish.
When an operational issue appears, the next question is what to do about it. Monitoring information can help frame that investigation. Your team still needs to assess the evidence, choose the next step, and confirm whether the issue is actually resolved.
Recovery deserves the same discipline. A backup and a tested recovery plan are not the same thing. If you're evaluating Fabric Control Backup, confirm supported scope, retention, and restore procedures. Then test the recovery you need, rather than assuming every dependency is covered.
And don't mistake an unanswered question for a healthy result. A missing measurement isn't proof that nothing is wrong. Closing gaps means checking freshness, coverage, and uncertainty, and distinguishing what the evidence shows from what still needs to be verified.
You don't have to tackle every gap at once. Governance, Operations, and Backup are separate offerings, and Operations can stand on its own. Start with the operational questions that matter most to your team, then evaluate the capabilities and scope needed to answer them.
That's the value of a more connected operational view: a clearer starting point for discussion, review, and action. Not a promise that every unknown disappears. A practical way to bring evidence and responsibility together, and make the next decision with more context.
Fabric Control. See the gaps. Connect the context. Take the next step. Start the conversation at ddsfabriccontrol.com
Be first to take control of your Fabric estate
The beta is open. Free forever for one Azure tenant, no card. Early adopters run Backup free for 3 months.