Microsoft Fabric and Azure data platforms in Lincoln: 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 Lincoln organisations find themselves in when they call us.

This page is about building a data platform for an organisation in Lincoln, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Lincoln's base in industrial machinery and engineering, agriculture and agribusiness, and higher education and research 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 power and gas turbine engineering and agri-food research and production.

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

Agriculture and agribusiness

Field, herd and yield data with weather dependence, subsidy and traceability reporting, and prices set by markets rather than by the business. Source systems typically include farm management systems, ERP, weather and satellite data, traceability platforms and subsidy reporting portals.

For a platform design, the consequence is specific. Subsidy and traceability reporting is produced separately from management reporting, so the same activity data is prepared twice differently. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a yield and margin model with time-versioned land and herd dimensions, plus traceability coverage reporting.

Energy generation and supply

Half-hourly or sub-hourly interval data at national scale, settlement runs that are revised months later, and metering that is partly estimated. Later settlement runs overwrite earlier ones, destroying the ability to explain why a previously reported figure has changed.

Systems to plan for: meter data management, settlement systems, SCADA, trading systems and billing platforms. Market reporting obligations and NIS2 critical-infrastructure duties apply, and consumption data is personal data for domestic customers.

Higher education and research

Student lifecycle, research grant and estates data in separate systems, with statutory returns and league-table submissions on fixed annual cycles. Statutory returns and internal management reporting are produced through separate routes, so published figures and internal figures disagree. Student data is personal data with additional duties around special-category attributes, and research data may carry funder-specific restrictions.

A medallion layout for an agriculture and agribusiness 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 Lincoln client in agriculture and agribusiness.

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

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

Migrating from what you have now

Few Lincoln 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 farm 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 Lincoln specifically, UK South (London) is the normal primary with UK West (Cardiff) as the pair. Latency from Lincoln 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 Lincoln 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, Norwich, Peterborough, Portsmouth, Aberdeen and Lancaster.

Frequently asked questions