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

The question we are asked most often by Zug organisations is whether they need Microsoft Fabric. The answer is frequently no, and saying so has cost us work we did not want.

This page is about building a data platform for an organisation in Zug, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Zug's base in commodity trading, asset and wealth management, and software and technology 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 one of Europe's densest concentrations of commodity trading and holding companies and a well-known blockchain and digital assets cluster.

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

Commodity trading

Position, trade and logistics data with mark-to-market valuation, counterparty exposure and physical movements that must reconcile against paper positions. Source systems typically include CTRM platform, market data feeds, logistics and vessel tracking, finance and treasury systems and credit systems.

For a platform design, the consequence is specific. Risk and finance value the same position at different snapshot times, so the explained difference is recalculated manually every day. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a position and valuation model with a single curve snapshot policy, which ends the daily disagreement between risk and finance.

Fintech and payments

Event-level transaction and authorisation data at very high volume, with settlement arriving later and often reconciling imperfectly against the event stream. Product analytics tooling is treated as the system of record for revenue, so finance and product publish different numbers to different audiences.

Systems to plan for: ledger service, payment gateway, card scheme settlement files, KYC and onboarding platforms and product event streams. PCI DSS scope should be deliberately limited in the analytics estate, which means tokenising or excluding card data rather than landing it and securing it.

Professional and legal services

Time, billing and pipeline data where almost every meaningful figure is an allocation, and where confidentiality obligations constrain who may see matter-level detail. Four definitions of utilisation circulate simultaneously, so partner behaviour responds to whichever figure appears in the meeting they attend. Matter confidentiality and information barriers must be inherited by analytics through row-level security, not re-implemented loosely.

A medallion layout for a commodity trading 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 Zug client in commodity trading.

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

Migrating from what you have now

Few Zug 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 CTRM platform.

Residency, latency and the Switzerland question

Switzerland North and Switzerland West give in-country residency, which matters more here than almost anywhere else in Europe: banking secrecy, professional secrecy obligations and client expectation all push Swiss data to stay Swiss. Verify per service, because not every Azure or Fabric feature is available in both Swiss regions.

For Zug specifically, Switzerland North (Zurich) is the normal primary with Switzerland West (Geneva) as the pair. Latency from Zug 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.

• The revFADP brought Swiss law closer to the GDPR but not identical to it: records of processing, impact assessments and breach notification follow Swiss rules, and an EU-shaped compliance pack needs adapting rather than copying.
• FINMA outsourcing expectations require documented control over cloud providers, including the right to audit and a tested exit plan.
• Article 321 of the Criminal Code and sectoral secrecy duties restrict who may see client-identifying data, which has direct consequences for row-level security design.

Where to go next

If you are weighing a platform decision for a Zug 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 Switzerland and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Zurich, Geneva, Lausanne, Baden, Lugano and Schaffhausen.

Frequently asked questions