Microsoft Fabric and Azure data platforms in Swindon: 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 Swindon, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Swindon's base in automotive and mobility, logistics and freight, and insurance and reinsurance 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 and engineering manufacturing and national research council headquarters functions.

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

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.

Insurance and reinsurance

Policy, premium and claims data where the same risk is represented differently in underwriting, finance and claims systems, and where development over time is the whole point. Actuarial results land as spreadsheets with no lineage, so the reported reserve movement cannot be tied back to the model run that produced it.

Systems to plan for: policy administration, claims management, actuarial reserving models, reinsurance systems and broker feeds. Claims data frequently includes health and criminal-conviction information, which attracts the stricter GDPR special-category conditions.

Public sector

Case and service data locked inside line-of-business systems with restrictive reporting modules, feeding statutory returns with precisely defined rules. Returns are assembled by hand each cycle by a small number of experienced staff, concentrating risk in individuals. Freedom of information and transparency duties mean published figures must be reproducible, and disclosure control has to be applied in the pipeline.

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 Swindon 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.

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 automotive and mobility workloads often are, while import still wins on smaller models with heavy DAX.

Migrating from what you have now

Few Swindon 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 avoid a big-bang cutover, which is the pattern that produces the rollbacks we get called in to repair. The reference pipeline we build first is usually the system that hurts most, which here is normally SAP ERP.

Residency, latency and the United Kingdom question

Azure UK South and UK West give genuine in-country data residency, and Power BI tenants can be provisioned in the United Kingdom region. Note that some workloads, certain preview features and a handful of AI services, still process outside the region, so residency claims should be checked per service rather than assumed tenant-wide.

For Swindon specifically, UK South (London) is the normal primary with UK West (Cardiff) as the pair. Latency from Swindon 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.

• UK GDPR data-minimisation and storage-limitation duties apply directly to analytics copies of personal data, which is where most estates quietly fail.
• Consumer Duty outcome monitoring has made customer-level analytics a supervisory expectation for regulated firms, not an optional capability.
• SECR energy and carbon reporting requires auditable activity data, which usually means the same lineage discipline as financial reporting.

Where to go next

If you are weighing a platform decision for a Swindon 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 United Kingdom and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Sunderland, Milton Keynes, Wolverhampton, Northampton, Luton and Peterborough.

Frequently asked questions