Microsoft Fabric and Azure data platforms in Plymouth: architecture, capacity and cost
How to build a Microsoft Fabric or Azure data platform for a Plymouth organisation: medallion layout for defence and security and ports, terminals and maritime, honest capacity sizing, Direct Lake trade-offs and the United Kingdom residency position.
Local view for Plymouth, United Kingdom
A Fabric capacity bought before anyone has profiled the workloads is an expense in search of a benefit. That is the position several Plymouth organisations find themselves in when they call us.
This page is about building a data platform for an organisation in Plymouth, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Plymouth's base in defence and security, ports, terminals and maritime, and industrial machinery and engineering 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 naval dockyard and defence engineering and marine and port operations.
Does a Plymouth organisation actually need Fabric?
Look for a cluster rather than a single trigger: import refreshes that are getting uncomfortable, demand for SQL and notebooks against one copy, self-service across more than one team, retention that rules out a desktop model, or an existing Premium commitment. One analyst maintaining three import models that refresh in twenty minutes does not need a capacity, and buying one will not improve anything.
| Situation | Recommendation | Why |
|---|---|---|
| Under about 10 GB of modelled data, one or two authors, overnight refresh is fine | Stay on Power BI Pro with import models | A capacity adds cost and operational surface with no benefit you can measure |
| Refresh windows no longer fit overnight, incremental refresh already in use | Lakehouse or warehouse serving layer | The constraint is transformation throughput, not the reporting tool |
| Analysts need SQL, data scientists need notebooks, both on the same data | Fabric, serving layer first | One copy of the data with multiple engines is the thing Fabric genuinely does well |
| Retention obligations measured in years at event grain | Lakehouse with lifecycle policies | Delta on cheap storage is far less expensive than keeping history in a semantic model |
| Existing Synapse or Databricks platform that works and costs are stable | Keep it; surface through Fabric or Power BI | Re-platforming a working estate to tidy an architecture diagram is not a business case |
What the data actually looks like in Plymouth
Defence and security
Programme and contract data under security classification, with configuration control, export restrictions and long-lived support obligations. Source systems typically include ERP, PLM, programme management systems, quality and configuration records and secure document stores.
For a platform design, the consequence is specific. Analytics is built outside the accredited environment, which makes the most important programme data the only data excluded from it. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a programme cost and earned-value model with controlled baselines, deployed inside the security boundary the contract requires.
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. Project margin is only known at completion, so loss-making contracts are discovered when it is far too late to act.
Systems to plan for: ERP, PLM / CAD, project management, field service management and CRM. Export control and dual-use classification data should be modelled explicitly where machinery is shipped outside the EU and UK.
Ports, terminals and maritime
Vessel, container and yard movement data at very high event volume, with berth planning and customs status driving operational decisions hour by hour. Equipment telemetry and the terminal operating system disagree on what counts as a move, so productivity figures vary by source. Customs and security data is tightly controlled, and NIS2 applies to many port operators as critical infrastructure.
A medallion layout for a defence and security 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 Plymouth client in defence and security.
| Layer | What lands here | Ownership | Rules |
|---|---|---|---|
| Bronze | Raw extracts from ERP, PLM and programme management systems, at source grain, with ingestion metadata | Platform team | Append-only, replayable for any date, no business logic, retention set against your obligations |
| Silver | Conformed, deduplicated, type-safe entities with the agreed business keys | Platform team with domain sign-off | Every transformation testable; data quality assertions block promotion on failure |
| Gold | Dimensional models for reporting: programme cost and earned-value model with controlled baselines, deployed inside the security boundary the contract requires | Domain team | One definition per measure, documented; changes go through review |
| Semantic | Direct Lake or import model serving reports and Excel | Analytics engineering | No business logic that is not also in gold; measure dictionary maintained |
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.
| Option | Who it suits | Approximate list price | The catch |
|---|---|---|---|
| Power BI Free | One person exploring data with no sharing | No charge | Cannot share into a workspace, so it is not a business option |
| Power BI Pro | Small reader populations, typically under about 200 people | Around US$14 per user per month at list | Every reader needs a licence, so cost scales linearly with the audience |
| Premium Per User | Teams needing larger models, higher refresh rates or paginated reports | Around US$24 per user per month at list | Still per-user, so a large reader base gets expensive quickly |
| Fabric F2, F32 capacity | Data engineering workloads with a modest reader population | From roughly US$260 a month for an F2, pay-as-you-go | Readers still need Pro licences below F64, and small SKUs throttle under load |
| Fabric F64 capacity | Large reader populations and in-platform data engineering | Roughly US$8,400 a month pay-as-you-go, around US$5,000 reserved | Only pays for itself above roughly 350 to 600 readers, depending on your discount |
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 defence and security workloads often are, while import still wins on smaller models with heavy DAX.
Migrating from what you have now
Few Plymouth 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. Neither requires switching everything at once, which is the approach behind most of the failed migrations we are asked to rescue. 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 Plymouth specifically, UK South (London) is the normal primary with UK West (Cardiff) as the pair. Latency from Plymouth 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 Plymouth 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: Portsmouth, Sheffield, Southampton, Glasgow, Liverpool and Nottingham.
Frequently asked questions
Is Microsoft Fabric worth it for a mid-sized Plymouth business?
Sometimes. 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. If one analyst maintains three models that refresh in twenty minutes, a capacity is a cost without a return, and we will put that in writing.
How do we size a Fabric capacity without guessing?
By measuring. Each workload is profiled for compute shape and concurrency, mapped to capacity units, then validated on a trial capacity using your real data. You get a sizing model showing utilisation at launch, at double the users, and the point at which the next SKU becomes necessary.
Can Fabric coexist with our existing Synapse or Databricks platform?
Yes, and for most organisations that is the pragmatic path. Shortcuts and mirroring let Fabric read data in place, so you can serve analytics from Fabric without re-platforming the engineering layer. Serving layer first, then stop and measure. Every further migration step should be justified by what the first one actually showed.
Where will our data physically sit?
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.
What does this cost for an organisation in Plymouth?
A workload assessment is a fixed fee in the low five figures. A landing zone plus a reference pipeline is typically a six to ten week engagement; full programmes run in quarterly increments and are quoted per phase. Platform licensing is separate and should be priced from the current Microsoft rate card for United Kingdom.
Who operates the platform afterwards?
Your team, with explicit layer ownership documented, or us under a managed service if you would rather not carry the on-call. Either way the runbooks, architecture decisions and monitoring configuration are yours from day one. The University of Plymouth has genuine strength in marine science and engineering, feeding defence and maritime employers.
Read next
Data governance and GDPR for Plymouth organisations: controls that produce evidence
Practical data governance for analytics estates in Plymouth: what the Information Commissioner's Office (ICO) expects under UK GDPR and the Data Protection Act 2018, the sector rules that bite locally, Microsoft Purview in practice, and a 90-day plan.
Power BI consultancy in Plymouth: what it costs, what breaks and what to build first
A practical guide to Power BI consultancy in Plymouth: the definition traps in defence and security and ports, terminals and maritime, honest licensing arithmetic, hire-versus-engage costs, and the compliance position under UK GDPR and the Data Protection Act 2018.
Microsoft Fabric and Azure data platforms in Portsmouth: architecture, capacity and cost
How to build a Microsoft Fabric or Azure data platform for a Portsmouth organisation: medallion layout for defence and security and ports, terminals and maritime, honest capacity sizing, Direct Lake trade-offs and the United Kingdom residency position.