Microsoft Fabric and Azure data platforms in Newbridge: architecture, capacity and cost
How to build a Microsoft Fabric or Azure data platform for a Newbridge organisation: medallion layout for pharmaceuticals and biotech and logistics and freight, honest capacity sizing, Direct Lake trade-offs and the Ireland residency position.
Local view for Newbridge, Ireland
A Fabric capacity bought before anyone has profiled the workloads is an expense in search of a benefit. That is the position several Newbridge organisations find themselves in when they call us.
This page is about building a data platform for an organisation in Newbridge, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Newbridge's base in pharmaceuticals and biotech, logistics and freight, and retail 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 pharmaceutical and healthcare manufacturing and retail and distribution.
Does a Newbridge 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 Newbridge
Pharmaceuticals and biotech
Regulated data across research, clinical, manufacturing and commercial domains, with validation requirements that make casual changes to a pipeline expensive. Source systems typically include CTMS and EDC, LIMS, MES, SAP ERP, pharmacovigilance systems and licensed market data.
For a platform design, the consequence is specific. Commercial and safety data share a workspace, which creates a compliance exposure that is painful to unwind once reports exist. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a manufacturing and quality model with deviation and batch release reporting, usually the fastest route to a defensible compliance and cost view.
Public sector
Case and service data locked inside line-of-business systems with restrictive reporting modules, feeding statutory returns with precisely defined rules. Returns are assembled by hand each cycle by a small number of experienced staff, concentrating risk in individuals.
Systems to plan for: case management systems, finance and ERP, HR and payroll, GIS and gazetteers and grant management. Freedom of information and transparency duties mean published figures must be reproducible, and disclosure control has to be applied in the pipeline.
Retail
Transaction-level sales with returns, promotions and loyalty discounts layered on top, plus stock positions that differ between systems. Returns posted in a later period against a different channel quietly corrupt both weekly margin and channel comparison. Loyalty and marketing analytics require a consent-aware customer model, so consent state has to be a dimension rather than a filter applied late.
A medallion layout for a pharmaceuticals and biotech 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 Newbridge client in pharmaceuticals and biotech.
| Layer | What lands here | Ownership | Rules |
|---|---|---|---|
| Bronze | Raw extracts from CTMS and EDC, LIMS and MES, 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: manufacturing and quality model with deviation and batch release reporting, usually the fastest route to a defensible compliance and cost view | 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 |
We size capacity by measuring rather than estimating: each workload profiled for compute shape, background refresh against interactive query, concurrency and peak hours, then validated on a short-lived trial capacity with your real 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
With Direct Lake the model reads Delta directly from OneLake, so there is no refresh to schedule and no query round trip. The catch is the condition attached: anything unsupported falls back, and you are then on SQL endpoint performance without having chosen it. 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 pharmaceuticals and biotech workloads often are, while import still wins on smaller models with heavy DAX.
Migrating from what you have now
Few Newbridge 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 CTMS and EDC.
Residency, latency and the Ireland question
North Europe sits in Dublin, so Irish organisations get in-country residency on the region most of Europe treats as its default. The practical consequence is excellent latency and a short list of residency questions, though cross-border processing still has to be documented where a service falls back to another region.
For Newbridge specifically, North Europe (Dublin) is the normal choice. Latency from Newbridge 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.
- Ireland hosts the EU establishment of many multinationals, so the DPC is frequently the lead supervisory authority, which raises the bar on analytics documentation well above local headcount.
- The Central Bank's outsourcing and operational resilience expectations apply to cloud analytics platforms used by regulated firms.
- EU-level obligations (DORA, NIS2, CSRD and the AI Act) apply in full, and the Irish implementation timetable is worth tracking per obligation.
Where to go next
If you are weighing a platform decision for a Newbridge 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 Ireland and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Naas, Drogheda, Swords, Navan, Carlow and Balbriggan.
Frequently asked questions
Is Microsoft Fabric worth it for a mid-sized Newbridge business?
Sometimes. The case for Fabric gets strong when more than one of these holds: import models under strain, the same data needed through both SQL and notebooks, governed self-service for several teams, retention that a desktop model cannot carry, or a Premium capacity already on the bill. 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?
North Europe sits in Dublin, so Irish organisations get in-country residency on the region most of Europe treats as its default. The practical consequence is excellent latency and a short list of residency questions, though cross-border processing still has to be documented where a service falls back to another region.
What does this cost for an organisation in Newbridge?
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 Ireland.
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. Newbridge relies on the Dublin and Kildare commuter catchment for analytics skills.
Read next
Power BI consultancy in Newbridge: what it costs, what breaks and what to build first
A practical guide to Power BI consultancy in Newbridge: the definition traps in pharmaceuticals and biotech and logistics and freight, honest licensing arithmetic, hire-versus-engage costs, and the compliance position under the EU GDPR and the Data Protection Act 2018.
Data governance and GDPR for Newbridge organisations: controls that produce evidence
Practical data governance for analytics estates in Newbridge: what the Data Protection Commission (DPC) expects under the EU GDPR and the Data Protection Act 2018, the sector rules that bite locally, Microsoft Purview in practice, and a 90-day plan.
Microsoft Fabric and Azure data platforms in Naas: architecture, capacity and cost
How to build a Microsoft Fabric or Azure data platform for a Naas organisation: medallion layout for logistics and freight and pharmaceuticals and biotech, honest capacity sizing, Direct Lake trade-offs and the Ireland residency position.