Microsoft Fabric and Azure data platforms in Neuchâtel: 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 Neuchâtel, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Neuchâtel's base in precision engineering and instruments, 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 micro-technology and precision engineering research and watchmaking and instrument manufacturing.

Does a Neuchâtel organisation actually need Fabric?

Fabric starts to earn its keep when several of the following are true at once: volumes that strain an import model, a genuine need for both SQL and notebook access to the same data, several teams requiring governed self-service, retention obligations that make a desktop model impossible, or an existing Premium capacity. 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 Neuchâtel

Precision engineering and instruments

Low-volume, high-value production with extensive measurement data per part, long order books and a service business attached to the installed base. Source systems typically include ERP, CAQ and metrology systems, MES, PLM and field service management.

For a platform design, the consequence is specific. Metrology data stays in the quality system, so the cost of variation never reaches the people deciding where to invest. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a measurement and scrap-cost model at part grain, which makes quality performance a financial conversation rather than an engineering one.

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.

Systems to plan for: MES, test and yield analysis systems, ERP, PLM and supplier portals. Export control classification applies to many components and to the associated technical data.

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 a precision engineering and instruments 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 Neuchâtel client in precision engineering and instruments.

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.

Capacity is sized from measurement, not from a spreadsheet. Each workload is profiled for its compute shape, for background refresh against interactive query, for concurrency and for when the peaks actually fall, then the result is checked on a trial capacity running your own 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

Direct Lake removes both the import refresh and the DirectQuery hop by reading Delta in place. It also carries a condition most teams discover late: unsupported constructs silently fall back, and the model then performs like DirectQuery. 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 precision engineering and instruments workloads often are, while import still wins on smaller models with heavy DAX.

Migrating from what you have now

Few Neuchâtel 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. What both have in common is that nothing is switched over in a single weekend. Single-weekend cutovers are what produce the rollbacks. The reference pipeline we build first is usually the system that hurts most, which here is normally ERP.

Residency, latency and the Switzerland question

Switzerland North and Switzerland West give in-country residency, which matters more here than almost anywhere else in Europe: banking secrecy, professional secrecy obligations and client expectation all push Swiss data to stay Swiss. Verify per service, because not every Azure or Fabric feature is available in both Swiss regions.

For Neuchâtel specifically, Switzerland North (Zurich) is the normal primary with Switzerland West (Geneva) as the pair. Latency from Neuchâtel 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.

• The revFADP brought Swiss law closer to the GDPR but not identical to it: records of processing, impact assessments and breach notification follow Swiss rules, and an EU-shaped compliance pack needs adapting rather than copying.
• FINMA outsourcing expectations require documented control over cloud providers, including the right to audit and a tested exit plan.
• Article 321 of the Criminal Code and sectoral secrecy duties restrict who may see client-identifying data, which has direct consequences for row-level security design.

Where to go next

If you are weighing a platform decision for a Neuchâtel 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 Switzerland and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: La Chaux-de-Fonds, Fribourg, Bern, Lausanne, Biel/Bienne and Yverdon-les-Bains.

Frequently asked questions