Microsoft Fabric and Azure data platforms in Newcastle upon Tyne: 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 Newcastle upon Tyne, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Newcastle upon Tyne's base in software and technology, public sector, and shared services and business process outsourcing 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 growing software and data engineering cluster and large public-sector and shared-service operations.

Does a Newcastle upon Tyne 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 Newcastle upon Tyne

Public sector

Case and service data locked inside line-of-business systems with restrictive reporting modules, feeding statutory returns with precisely defined rules. Source systems typically include case management systems, finance and ERP, HR and payroll, GIS and gazetteers and grant management.

For a platform design, the consequence is specific. Returns are assembled by hand each cycle by a small number of experienced staff, concentrating risk in individuals. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a governed model that produces both the statutory return and internal performance reporting, so published and internal figures cannot diverge.

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.

Systems to plan for: billing and subscription platform, CRM, product event pipeline, support platform and finance system. Product telemetry on identifiable users needs a lawful basis and consent handling, and SOC 2 or ISO 27001 evidence often covers the analytics estate.

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. Client data segregation is a contractual obligation, and processor duties under GDPR apply to the provider rather than only the client.

A medallion layout for a public sector 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 Newcastle upon Tyne client in public sector.

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.

Sizing comes from a trial capacity running your real workloads, profiled for compute shape, refresh against query load, concurrency and peak hours. Estimating it from user counts is how organisations end up throttled at month end. 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 reads Delta files in OneLake with no import refresh and no DirectQuery round trip, but unsupported constructs trigger fallback and performance then depends on the SQL endpoint. 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 public sector workloads often are, while import still wins on smaller models with heavy DAX.

Migrating from what you have now

Few Newcastle upon Tyne 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 case management systems.

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

Frequently asked questions