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

A Fabric capacity bought before anyone has profiled the workloads is an expense in search of a benefit. That is the position several Watford organisations find themselves in when they call us.

This page is about building a data platform for an organisation in Watford, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Watford's base in retail, professional and legal services, and media, advertising and creative 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 retail and consumer head-office functions and professional services and shared-service centres.

Does a Watford organisation actually need Fabric?

Fabric starts to earn its keep when several of the following are true at once: volumes that strain an import model, a genuine need for both SQL and notebook access to the same data, several teams requiring governed self-service, retention obligations that make a desktop model impossible, or an existing Premium capacity. 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 Watford

Retail

Transaction-level sales with returns, promotions and loyalty discounts layered on top, plus stock positions that differ between systems. Source systems typically include EPOS, ERP, warehouse management, loyalty platform and workforce management.

For a platform design, the consequence is specific. Returns posted in a later period against a different channel quietly corrupt both weekly margin and channel comparison. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be one sales fact with consistent return treatment and a margin ladder finance recognises, which ends the commercial-versus-finance disagreement.

Construction and real estate

Project cost and progress data with subcontractor valuations, variations and retentions, plus asset and tenancy data on the property side. Project reporting runs monthly on manually consolidated spreadsheets, so a problem contract is identified two months after it turned.

Systems to plan for: project costing systems, ERP, BIM and design systems, site progress apps and property management systems. Subcontractor payment and tax reporting obligations apply, and health and safety records carry their own retention duties.

Media, advertising and creative

Audience and campaign data from many external platforms, each with its own metric definitions, alongside project and resource data on the delivery side. Each platform's own numbers are reported side by side as if comparable, producing totals that exceed actual results. Audience and behavioural tracking requires consent under ePrivacy rules, and some measurement licences restrict internal redistribution.

A medallion layout for a retail 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 Watford client in retail.

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

Migrating from what you have now

Few Watford 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 EPOS.

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 Watford specifically, UK South (London) is the normal primary with UK West (Cardiff) as the pair. Latency from Watford 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 Watford 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: St Albans, Manchester, Cardiff, Nottingham, Belfast and Milton Keynes.

Frequently asked questions