Microsoft Fabric and Azure data platforms in Telford: 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 Telford, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Telford's base in industrial machinery and engineering, automotive and mobility, and logistics and freight 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 engineering and automotive component manufacturing and electronics and assembly operations.

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

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. Source systems typically include SAP ERP, MES, quality management system, EDI customer schedules, warranty claims systems and PLM.

For a platform design, the consequence is specific. Customer scorecards and internal quality reporting use different denominators, so the plant believes it is performing while the customer escalates. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a traceability model linking batch and part to vehicle and claim, which is also what makes a recall survivable.

Logistics and freight

Event data from scanners, telematics, EDI and transport management systems, each with its own timestamp semantics and time zone handling. Subcontracted volume arrives as spreadsheets, so a third of the network is effectively unmeasured exactly where control is weakest.

Systems to plan for: transport management system, warehouse management system, telematics, EDI messages and customs platforms. Drivers' hours records, customs declarations and posting documentation all carry retention obligations and are frequently requested in audit.

Electronics and semiconductors

Very high volume test and yield data per die or unit, complex multi-stage processes, and component supply with long and volatile lead times. Test data is aggregated at ingestion, so when a field failure pattern emerges the unit-level evidence no longer exists. Export control classification applies to many components and to the associated technical data.

A medallion layout for an automotive and mobility 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 Telford client in automotive and mobility.

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

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

Migrating from what you have now

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

Frequently asked questions