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

The question we are asked most often by Poole 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 Poole, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Poole's base in medical devices, industrial machinery and engineering, and ports, terminals and maritime 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 medical device and precision manufacturing and port and ferry operations.

Does a Poole organisation actually need Fabric?

No single condition justifies a capacity. Several together do: data that no longer fits an import model, a requirement for both SQL and notebook access, multiple teams needing governed self-service, retention obligations beyond what a desktop file can hold, or a Premium capacity you already pay for. 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 Poole

Industrial machinery and engineering

Project and configuration data as much as production data: engineered-to-order items, long lead times, and service revenue that outlives the original sale. Source systems typically include ERP, PLM / CAD, project management, field service management and CRM.

For a platform design, the consequence is specific. Project margin is only known at completion, so loss-making contracts are discovered when it is far too late to act. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a project cost and margin model with an installed-base dimension, which turns aftermarket service from an anecdote into a managed revenue line.

Tourism, hospitality and events

Booking, channel and rate data with heavy seasonality, plus on-site spend and occupancy that only reconcile once channel commission is accounted for. Gross booking value from online travel agents is compared with direct booking revenue, making the most expensive channel look like the best one.

Systems to plan for: property management system, booking channels and OTAs, revenue management system, EPOS and CRM. Guest data is personal data with cross-border transfer implications when group systems sit outside the region.

Medical devices

Device history records, complaint and vigilance data, and post-market surveillance obligations that require linking field events back to manufacturing batches. Distributor-held data breaks traceability at exactly the point where a field action needs it. EU MDR post-market surveillance and vigilance reporting require a reproducible data trail from field event back to production batch.

A medallion layout for an industrial machinery and engineering 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 Poole client in industrial machinery and engineering.

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

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

Migrating from what you have now

Few Poole 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 keep the old platform running until each domain is proven. The alternative, moving everything at once, is how migrations end up reversed. The reference pipeline we build first is usually the system that hurts most, which here is normally ERP.

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 Poole specifically, UK South (London) is the normal primary with UK West (Cardiff) as the pair. Latency from Poole 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 Poole 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, Liverpool, Edinburgh, Southampton, Bournemouth and Brighton and Hove.

Frequently asked questions