Microsoft Fabric and Azure data platforms in Düsseldorf: architecture, capacity and cost

A Fabric capacity bought before anyone has profiled the workloads is an expense in search of a benefit. That is the position several Düsseldorf organisations find themselves in when they call us.

This page is about building a data platform for an organisation in Düsseldorf, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Düsseldorf's base in professional and legal services, telecommunications, and retail determines the data volumes, the latency requirements and the retention obligations, and those three things decide the architecture. The client population here is shaped by a concentration of corporate headquarters and professional services and telecoms and technology operations.

Does a Düsseldorf organisation actually need Fabric?

No single condition justifies a capacity. Several together do: data that no longer fits an import model, a requirement for both SQL and notebook access, multiple teams needing governed self-service, retention obligations beyond what a desktop file can hold, or a Premium capacity you already pay for. One analyst maintaining three import models that refresh in twenty minutes does not need a capacity, and buying one will not improve anything.

What the data actually looks like in Düsseldorf

Professional and legal services

Time, billing and pipeline data where almost every meaningful figure is an allocation, and where confidentiality obligations constrain who may see matter-level detail. Source systems typically include practice management system, time recording, professional services automation, CRM and finance system.

For a platform design, the consequence is specific. Four definitions of utilisation circulate simultaneously, so partner behaviour responds to whichever figure appears in the meeting they attend. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a time, billing and WIP model with one agreed utilisation and realisation definition, reported from practice group down to individual under agreed visibility rules.

Metals and materials

Heat and coil genealogy, energy-intensive process data, and quality certification per batch, with energy cost a dominant and volatile input. Energy and production data are reported on different period bases, so the cost per tonne figure moves for reasons nobody can explain.

Systems to plan for: process control systems, ERP, quality certification systems, energy monitoring and logistics systems. Emissions trading and carbon border reporting require auditable activity data with versioned emissions factors.

Retail

Transaction-level sales with returns, promotions and loyalty discounts layered on top, plus stock positions that differ between systems. Returns posted in a later period against a different channel quietly corrupt both weekly margin and channel comparison. Loyalty and marketing analytics require a consent-aware customer model, so consent state has to be a dimension rather than a filter applied late.

A medallion layout for a professional and legal services business

The medallion pattern is not complicated, and it is routinely implemented badly: a bronze layer that has already lost fidelity, a silver layer with no testable rules, and a gold layer that is really just the silver layer with different names. Here is how we would lay it out for a Düsseldorf client in professional and legal services.

Capacity sizing and what it really costs

Fabric capacity is billed by capacity unit. An F2 is roughly US$0.36 per hour pay-as-you-go, about US$260 a month, with around 40 per cent off for a one-year reservation. An F64, the smallest SKU at which report consumers no longer need an individual Pro licence, is roughly US$8,400 a month pay-as-you-go or around US$5,000 reserved.

The arithmetic that matters: F64 only becomes cheaper than per-user licensing somewhere in the region of 350 to 600 readers, depending on the discount you actually pay and whether you reserve capacity. Below that, Pro or PPU per user is normally the right answer, and buying capacity for prestige is a straightforward waste of money.

The sizing exercise is empirical: profile each workload, separate background refresh from interactive query, count real concurrency, find the true peak, then prove the number on a short-lived capacity before anything is bought. The output is a sizing model that states expected utilisation at launch, at double the readers, and the specific point at which you would need the next SKU. Always price from the current Microsoft rate card for your region and agreement. Any figure in an article older than a quarter should be treated as an order of magnitude, not a quote.

Direct Lake, import or DirectQuery

Direct Lake reads Delta files in OneLake with no import refresh and no DirectQuery round trip, but unsupported constructs trigger fallback and performance then depends on the SQL endpoint. We test it against an import model on your own data and choose on the measured result. In practice Direct Lake tends to win on large, frequently landing tables, which professional and legal services workloads often are, while import still wins on smaller models with heavy DAX.

Migrating from what you have now

Few Düsseldorf organisations start from nothing. The realistic options are a serving-layer-first adoption, where Fabric takes the gold layer and reporting while existing engineering stays in place, or a domain-by-domain migration with the old platform retained until each domain is validated. Both keep the old platform running until each domain is proven. The alternative, moving everything at once, is how migrations end up reversed. The reference pipeline we build first is usually the system that hurts most, which here is normally practice management system.

Residency, latency and the Germany question

Germany West Central in Frankfurt is the usual choice and gives in-country residency with very low latency to the financial sector. Germany North provides a paired region. Residency alone does not satisfy a German works council or data protection officer. They will also ask about processor chains and access by support personnel, so those answers need preparing.

For Düsseldorf specifically, Germany West Central (Frankfurt) is the normal primary with Germany North (Berlin) as the pair. Latency from Düsseldorf to that region is not usually a constraint for analytical workloads; the constraints that bite are feature availability per region and the processor chain your data protection officer will ask about.

• Betriebsrat co-determination is the single most underestimated factor in German analytics projects: any reporting that could be used to assess individual employee performance generally needs a works agreement before launch.
• MaRisk and BAIT expectations mean financial-sector data lineage and documentation standards are explicit, not inferred.
• The Lieferkettensorgfaltspflichtengesetz requires supply-chain due-diligence data that most ERP estates do not hold in reportable form.

Where to go next

If you are weighing a platform decision for a Düsseldorf organisation, a workload assessment will answer it with evidence in two to three weeks, and the written recommendation is yours whatever you decide. Book a technical review.

We work across Germany and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Berlin, Cologne, Bonn, Gütersloh, Hamburg and Munich.

Frequently asked questions