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

The question we are asked most often by Birmingham organisations is whether they need Microsoft Fabric. The answer is frequently no, and saying so has cost us work we did not want.

This page is about building a data platform for an organisation in Birmingham, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Birmingham's base in professional and legal services, automotive and mobility, and industrial machinery and engineering 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 professional and financial services centre and the surrounding automotive and components supply chain.

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

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 and commercial banking

High-volume transactional data at account and posting grain, with a core banking system that was never designed to be queried analytically and a general ledger that is authoritative but coarse. Each function builds its own extract from core banking with its own as-at timing, and the resulting small variances are never reconciled. They are simply explained away each month.

Systems to plan for: core banking platform, general ledger, card and payment processors, credit decisioning systems and CRM. Account-level data is both personal data and commercially sensitive, so row-level security and export control are design requirements rather than later hardening.

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. Customer scorecards and internal quality reporting use different denominators, so the plant believes it is performing while the customer escalates. IATF 16949 traceability expectations mean retention periods are long and immutability matters more than query convenience.

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

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

Migrating from what you have now

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

Frequently asked questions