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

Before deciding on a lakehouse, it is worth establishing whether your data actually outgrew an import model or simply outgrew the person maintaining it.

This page is about building a data platform for an organisation in Slough, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Slough's base in software and technology, logistics and freight, and food and drink manufacturing 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 one of Europe's largest single-owner trading estates and technology and telecoms corporate operations.

Does a Slough organisation actually need Fabric?

The case for Fabric gets strong when more than one of these holds: import models under strain, the same data needed through both SQL and notebooks, governed self-service for several teams, retention that a desktop model cannot carry, or a Premium capacity already on the bill. 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 Slough

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. Source systems typically include billing and subscription platform, CRM, product event pipeline, support platform and finance system.

For a platform design, the consequence is specific. ARR comes from a finance spreadsheet with manual adjustments, so restating a prior period requires archaeology and diligence becomes painful. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be an effective-dated contract and movement model so ARR is reproducible for any historical date, then product events joined at account grain.

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.

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 software and technology 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 Slough client in software and technology.

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

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

Migrating from what you have now

Few Slough 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 billing and subscription platform.

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

Frequently asked questions