Microsoft Fabric and Azure data platforms in Stockport: 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 Stockport, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Stockport's base in industrial machinery and engineering, professional and legal services, 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 precision engineering and manufacturing and professional services relocating from central Manchester.

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

Professional and legal services

Time, billing and pipeline data where almost every meaningful figure is an allocation, and where confidentiality obligations constrain who may see matter-level detail. Source systems typically include practice management system, time recording, professional services automation, CRM and finance system.

For a platform design, the consequence is specific. Four definitions of utilisation circulate simultaneously, so partner behaviour responds to whichever figure appears in the meeting they attend. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a time, billing and WIP model with one agreed utilisation and realisation definition, reported from practice group down to individual under agreed visibility rules.

Retail

Transaction-level sales with returns, promotions and loyalty discounts layered on top, plus stock positions that differ between systems. Returns posted in a later period against a different channel quietly corrupt both weekly margin and channel comparison.

Systems to plan for: EPOS, ERP, warehouse management, loyalty platform and workforce management. Loyalty and marketing analytics require a consent-aware customer model, so consent state has to be a dimension rather than a filter applied late.

Healthcare provision

Patient-level activity data of the highest sensitivity, with cohort and pathway definitions that must be stable and clinically defensible. Two reports on the same pathway include different patients, and clinical confidence collapses the first time the difference surfaces in a meeting. Health data attracts the stricter GDPR special-category conditions, and small-number suppression must be enforced in measures including drill-through.

A medallion layout for a professional and legal services 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 Stockport client in professional and legal services.

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

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

Migrating from what you have now

Few Stockport 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 practice 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 Stockport specifically, UK South (London) is the normal primary with UK West (Cardiff) as the pair. Latency from Stockport 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 Stockport 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: Leeds, Nottingham, Belfast, London, Birmingham and Manchester.

Frequently asked questions