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

This page is about building a data platform for an organisation in Milton Keynes, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Milton Keynes's base in logistics and freight, retail, 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 a major national distribution hub position and corporate headquarters and shared-service centres.

Does a Milton Keynes 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 Milton Keynes

Logistics and freight

Event data from scanners, telematics, EDI and transport management systems, each with its own timestamp semantics and time zone handling. Source systems typically include transport management system, warehouse management system, telematics, EDI messages and customs platforms.

For a platform design, the consequence is specific. Subcontracted volume arrives as spreadsheets, so a third of the network is effectively unmeasured exactly where control is weakest. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a canonical event model with normalised UTC timestamps and documented source precedence, which is the prerequisite for every duration measure.

Shared services and business process outsourcing

Transaction and case volumes across multiple client entities, with contractual service levels, workforce data and per-client confidentiality boundaries. One generic service-level calculation is applied to every contract, so reported performance does not match what clients are entitled to measure.

Systems to plan for: workflow and case management, contact centre platforms, workforce management, client ERP instances and quality monitoring. Client data segregation is a contractual obligation, and processor duties under GDPR apply to the provider rather than only the client.

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. Product telemetry on identifiable users needs a lawful basis and consent handling, and SOC 2 or ISO 27001 evidence often covers the analytics estate.

A medallion layout for a logistics and freight 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 Milton Keynes client in logistics and freight.

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

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

Migrating from what you have now

Few Milton Keynes 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 transport management system.

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 Milton Keynes specifically, UK South (London) is the normal primary with UK West (Cardiff) as the pair. Latency from Milton Keynes 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 Milton Keynes 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, Luton, Warrington, Swindon, Slough and Newcastle upon Tyne.

Frequently asked questions