Microsoft Fabric and Azure data platforms in Bielefeld: 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 Bielefeld organisations find themselves in when they call us.

This page is about building a data platform for an organisation in Bielefeld, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Bielefeld's base in industrial machinery and engineering, food and drink manufacturing, and software and technology 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 household appliance and machinery manufacturing and food production.

Does a Bielefeld organisation actually need Fabric?

Look for a cluster rather than a single trigger: import refreshes that are getting uncomfortable, demand for SQL and notebooks against one copy, self-service across more than one team, retention that rules out a desktop model, or an existing Premium commitment. 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 Bielefeld

Industrial machinery and engineering

Project and configuration data as much as production data: engineered-to-order items, long lead times, and service revenue that outlives the original sale. Source systems typically include ERP, PLM / CAD, project management, field service management and CRM.

For a platform design, the consequence is specific. Project margin is only known at completion, so loss-making contracts are discovered when it is far too late to act. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a project cost and margin model with an installed-base dimension, which turns aftermarket service from an anecdote into a managed revenue line.

Software and technology

Product event streams at very high volume alongside subscription, billing and support data that must be joined at account grain to be useful. ARR comes from a finance spreadsheet with manual adjustments, so restating a prior period requires archaeology and diligence becomes painful.

Systems to plan for: billing and subscription platform, CRM, product event pipeline, support platform and finance system. Product telemetry on identifiable users needs a lawful basis and consent handling, and SOC 2 or ISO 27001 evidence often covers the analytics estate.

Food and drink manufacturing

Short shelf life, high SKU churn, promotional volatility and retailer scorecards that measure you on their definitions rather than yours. Internal service levels read green while the retailer scorecard reads amber, because the two measure different events. HACCP and traceability obligations mean batch records must be retrievable quickly enough to support a withdrawal within hours.

A medallion layout for an industrial machinery and engineering 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 Bielefeld client in industrial machinery and engineering.

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

With Direct Lake the model reads Delta directly from OneLake, so there is no refresh to schedule and no query round trip. The catch is the condition attached: anything unsupported falls back, and you are then on SQL endpoint performance without having chosen it. 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 industrial machinery and engineering workloads often are, while import still wins on smaller models with heavy DAX.

Migrating from what you have now

Few Bielefeld 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. Neither requires switching everything at once, which is the approach behind most of the failed migrations we are asked to rescue. The reference pipeline we build first is usually the system that hurts most, which here is normally ERP.

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 Bielefeld specifically, Germany West Central (Frankfurt) is the normal primary with Germany North (Berlin) as the pair. Latency from Bielefeld 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 Bielefeld 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: Bochum, Würzburg, Mannheim, Leipzig, Dortmund and Dresden.

Frequently asked questions