Microsoft Fabric and Azure data platforms in Regensburg: architecture, capacity and cost

Microsoft Fabric is a genuine step forward and a genuine way to spend money quickly, and which one you get depends almost entirely on decisions made in the first fortnight.

This page is about building a data platform for an organisation in Regensburg, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Regensburg's base in automotive and mobility, electronics and semiconductors, and higher education and research 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 automotive electronics and semiconductor manufacturing and a research university and biotech park.

Does a Regensburg 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 Regensburg

Automotive and mobility

Deep traceability data spanning part, batch, vehicle and plant, with customer release schedules that change weekly and warranty data arriving months after production. Source systems typically include SAP ERP, MES, quality management system, EDI customer schedules, warranty claims systems and PLM.

For a platform design, the consequence is specific. Customer scorecards and internal quality reporting use different denominators, so the plant believes it is performing while the customer escalates. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a traceability model linking batch and part to vehicle and claim, which is also what makes a recall survivable.

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. Project margin is only known at completion, so loss-making contracts are discovered when it is far too late to act.

Systems to plan for: ERP, PLM / CAD, project management, field service management and CRM. Export control and dual-use classification data should be modelled explicitly where machinery is shipped outside the EU and UK.

Electronics and semiconductors

Very high volume test and yield data per die or unit, complex multi-stage processes, and component supply with long and volatile lead times. Test data is aggregated at ingestion, so when a field failure pattern emerges the unit-level evidence no longer exists. Export control classification applies to many components and to the associated technical data.

A medallion layout for an automotive and mobility 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 Regensburg client in automotive and mobility.

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.

We size capacity by measuring rather than estimating: each workload profiled for compute shape, background refresh against interactive query, concurrency and peak hours, then validated on a short-lived trial capacity with your real data. 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

The appeal of Direct Lake is that nothing is copied and nothing is refreshed. The risk is the fallback: one unsupported construct and the model quietly behaves like DirectQuery instead. 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 automotive and mobility workloads often are, while import still wins on smaller models with heavy DAX.

Migrating from what you have now

Few Regensburg 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 SAP 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 Regensburg specifically, Germany West Central (Frankfurt) is the normal primary with Germany North (Berlin) as the pair. Latency from Regensburg 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 Regensburg 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: Chemnitz, Hildesheim, Braunschweig, Aachen, Osnabrück and Paderborn.

Frequently asked questions