Fabric touches your entire data chain: pipelines, capacity, the semantic model, and the reports it produces. We understand that chain and keep it running, with a team that has worked with data for twenty years—from the first data warehouses to Fabric today.
A user reports that a report will not load or is showing outdated figures. That is the symptom. The cause is usually one layer deeper: a stalled pipeline, a failed data connection, or capacity reaching its limit and causing processes to queue. With Fabric, identifying the root cause is often the real work, because the problem and the place where you notice it are not the same.
We handle those reports and investigate where the problem really lies. A failed pipeline run, usually caused by a change in the source, a timeout, or a scheduling conflict. A data connection that needs to be reauthorized. Capacity that is consistently insufficient rather than experiencing a one-off spike. That last issue requires a trade-off you need to make more often with Fabric than with other platforms: is this a configuration problem, or is more capacity simply needed?
Meanwhile, the routine work continues: managing users and permissions, roles and workspace access, and the smaller changes that inevitably arise. That is part of the job too, and we take care of it.
A Fabric environment that no one manages will gradually fall out of step. Sources change, data volumes grow, capacity that was more than sufficient last year becomes constrained, and new features are continually added that you may or may not want to enable. That is why we review your environment on a regular schedule. We perform these checks using Fabric’s own monitoring dashboards and capacity metrics, or through the REST API when that is more practical.
When everything is working well, most of this goes unnoticed—and that is exactly the point. An environment that grows with the organization does not need emergency repairs when it suddenly no longer meets your needs.
Microsoft Fabric has only been around since late 2023. Anyone calling themselves a Fabric specialist today has therefore worked with it for no more than two and a half years, and the same applies to us. The difference lies in the experience you bring to this new platform.
We do not come to this without prior experience. Our team has worked with data for twenty years: data warehousing, modeling, ETL and governance. We have also worked with Azure—the infrastructure on which Fabric runs—for years. Those are precisely the disciplines that matter in Fabric, just under different names and in a new environment. Capacity that becomes unbalanced, a flawed semantic model, a deployment that cannot be reproduced: these are not new problems, even if the controls are new. Our consultants hold DP-600 and DP-700 certifications, the most demanding Fabric certifications available, and that expertise is built on a foundation of twenty years of data projects.
This experience matters most when making choices whose consequences only become apparent a year later. Which setup will hold up when your data volume triples? Where can you free up capacity through a better design instead of a more expensive license? Which shortcut seems convenient now but will cause problems later? That kind of judgment does not come from a certification, but from the projects you have completed before. Read more about our Fabric work on our Microsoft Fabric Consulting page.
Are you bringing us a Fabric environment that someone else set up? We start with an assessment. We review the setup, pipelines, capacity usage, semantic model and deployment process so that both sides understand exactly what we are taking over.
This almost always produces a list of items that need attention. We address anything urgent and include the rest in a plan. Especially with Fabric, where a suboptimal setup may only reveal itself as data volumes grow or capacity fills up, it is better to identify these issues in advance than encounter them later.
Fabric support uses the same support packages as our other platforms: Starter, Booster and Premium, with fixed response times and a monthly hours allowance. Starting at €950 per month. The full comparison, including add-ons, is available on our Support & Management page.
Not sure which package is right for you? We will review the size of your environment, your capacity usage and what you already handle in-house.
We’d be happy to review it with you and discuss what stands out, how urgent it is, and what the most sensible next step would be.
Both—and in practice, they overlap. Power BI has become part of Fabric, so a report that loads slowly and a pipeline that fails may be symptoms of the same problem. We support the entire chain. If your question mainly concerns the reporting layer, our Power BI support page may be a better place to start.
Because the disciplines that keep Fabric running well are not new: data modeling, capacity management, governance, and reliable deployment. We have been applying them on other platforms for twenty years, and we have worked with Azure—the infrastructure Fabric runs on—for years. Fabric is relatively new to everyone, but we know its foundations well.
Not as an off-the-shelf product. For Fabric, we use the platform’s own monitoring dashboards and capacity metrics, and query the REST API where useful. This gives us the same type of oversight as with Qlik: daily checks of refreshes, pipelines, and capacity, plus periodic checks of the environment’s broader health.
It gets out of sync. A business environment changes, and the Fabric environment needs to change with it: new features that you may want to enable or disable, capacity that needs to be readjusted, and a setup that becomes outdated. Without maintenance, the environment will eventually no longer meet your needs—usually just when you are relying on it.
That is exactly the question we ask first. Sometimes more capacity is justified, but often the gains come from a better setup: more efficient pipelines, a smarter semantic model, and refreshes that do not interfere with one another. We first look at what is driving consumption before you move to a more expensive license.
Yes. We start with an assessment of the setup, pipelines, capacity, semantic model, and deployment. You will then know what is in place, what needs attention, and in what order.
Whether something has stalled or you want to know if your environment is still configured properly, Barry and Eric will be happy to discuss it with you. Email us, call us, or book an appointment directly at a time that works for you.