>
Voice of Volge is a series of books, and the firm's thought leadership on the solutions and the domains Volge specialises in. Each edition takes one of them and sets out what the technology makes possible, what it makes mandatory, and what an operator has to put in place before either is true of them.
OneLake, the lakehouse, real-time intelligence, and the economics of one platform
Figures carry their basis and their date. Where published estimates disagree, the range is given and the basis named rather than averaged away, and where a widely quoted number does not survive checking it is corrected here rather than repeated. Every chart plots a figure stated in the text, and nothing is projected beyond what a named source projects.
The analytics landscape fragmented one procurement decision at a time. A warehouse was bought for structured reporting, a lake for the data science team, a streaming stack for operational telemetry, a separate business-intelligence tier for the dashboards, a governance tool to catalogue what the others held. Each was licensed on its own meter, operated by its own team, and connected to the rest by pipelines that someone has to keep running. The landscape works. It also leaks , cost, latency, and trust , and it leaks at the seams between the services, not inside any one of them.
That leakage has a name, the integration tax. It is the engineering paid to move and reconcile the same data across stores that do not share one, the compute paid to maintain redundant copies, the latency added by every hop, and the trust lost each time two services disagree about the same customer because each holds its own copy. The tax is rarely a line item, which is exactly why it persists. It is distributed across pipeline maintenance, duplicated storage, idle reserved capacity on five separate meters, and the slow erosion of confidence in numbers that should match and do not.
Microsoft Fabric is a bet that the tax is large enough to justify collapsing the stack. Fabric is an end-to-end software-as-a-service analytics platform that unifies the workloads a data landscape runs. Microsoft Learn lists nine of them: Power BI, Databases, Data Factory, Industry Solutions, Real-Time Intelligence, Data Engineering, Data Science, Data Warehouse, and Fabric IQ, which is in preview. They run over one shared lake, OneLake, under one governance model and one capacity model (Microsoft Learn, 2026). It consolidates what were separately licensed Azure services, among them Azure Synapse Analytics, Azure Data Lake Storage, Power BI Premium and Azure Data Factory, onto a single platform over one copy of the data (Microsoft, 2026). The warehouse and the lakehouse read the same files. Power BI queries those files in place. The streaming engine and the data-science notebooks and the pipelines all operate on one logical store rather than on copies of it.
The adoption signal is not ambiguous. Microsoft reports 44,000 paid Fabric customers as at the first quarter of financial year 2027, up more than 50 per cent year over year and 4,000 more than a quarter earlier (Microsoft earnings, Q1 FY2027, 28 October 2026). The same call put more than 19,000 customers on Foundry and Fabric together, which is the clearest published measure of enterprises wiring agents to governed operational data, and Foundry itself at 120,000 customers against 100,000 a quarter earlier. Earlier disclosures fill in the trajectory. The volume of data held in OneLake was up nearly
four times year over year (Microsoft earnings, Q3 FY2026, 29 April 2026), and the annual revenue run rate passed two billion United States dollars alongside more than 31,000 customers (Microsoft earnings, Q2 FY2026, 28 January 2026). Consolidation onto one platform is the fastest-growing pattern in enterprise analytics.
The central finding. The decision a data leader actually faces is not which engine is fastest. It is what collapsing the analytics stack onto one platform saves, what it costs, and where it does not fit. Fabric's value is the integration tax it removes, set against the specialised depth a best-of-breed landscape retains. What it removes is one copy of the data, one governance plane and one capacity meter, and one operational surface. Where the landscape is fragmented, Microsoft-aligned, and dominated by integration toil, consolidation pays. Where a workload demands the engineering or warehousing ceiling of a specialist platform, it does not, and the honest architecture is hybrid.
A second finding sits in front of the first, and most consolidation cases omit it. The platform is not available everywhere its infrastructure is. Qatar Central, a live Azure region in Doha, carries Power BI and not the Fabric workloads, on Microsoft's own region availability page (Microsoft Learn, page updated 5 November 2026). Saudi Arabia has no Azure region at all, and no Microsoft 365 residency commitment of any kind (Microsoft Learn, page updated 27 October 2026). For a Gulf or Indian enterprise the consolidation question therefore has a prior question in front of it. Where may each data domain lawfully rest, and where may it lawfully be processed. Microsoft commits to storage at rest in the tenant geography. It does not commit to processing in region. The European Union Data Boundary is the only processing commitment it publishes anywhere.
This is a paper about consolidation economics, not about artificial intelligence. AI-readiness is one outcome of a consolidated, governed landscape, and a real one, but it is a downstream benefit treated briefly here. The companion Volge paper, The data estate is the accuracy budget (Topic 7), carries the agent-grounding argument in full. This paper points to it once and stays on the data leader's own drivers, namely consolidation of the landscape and migration off legacy services, cost and capacity, real-time analytics and governance, and business intelligence.
Six conclusions, developed in the chapters that follow.
Second, OneLake is the architectural decision that makes the rest follow. One logical lake, storing data once in an open format and exposing it to every workload without duplication, is what lets the warehouse, the lakehouse, and the BI tier
operate on one copy. Remove copy sprawl at the storage layer and the contradictions it manufactures disappear upstream of every consumer.
First, the integration tax is the lever, not engine performance. Cost, latency, and trust leak between services, not within them. The saving from consolidation comes from removing copies, pipelines, and redundant capacity , the connective tissue , rather than from any single engine running faster.
Third, the capacity model is the commercial mechanism, and F64 is its inflection. Fabric replaces per-service licensing with one pooled compute meter measured in capacity units. The F64 tier is the point at which Power BI Premium-equivalent features and Direct Lake become available. That is why it anchors most enterprise deployments, and why the total-cost comparison turns on capacity sizing rather than on headline list prices (Microsoft Fabric pricing, verified 8 November 2026).
Fourth, the migration is a programme, not a switch. Moving off Synapse, standalone Power BI Premium, and Azure Data Factory is staged work with real cutover risk. Microsoft has not declared Synapse end-of-life wholesale, but the strategic direction and targeted deprecations are unambiguous (Microsoft, 2025-2026). The migration is underwritten by the integration tax it retires, not by novelty.
Fifth, consolidation is not the answer for every workload. Databricks remains stronger for large-scale data engineering and machine learning on Apache Spark; Snowflake remains stronger for high-concurrency SQL warehousing and frictionless data sharing. Fabric wins on unification and on integration with the Microsoft and Power BI ecosystem. A mature landscape is frequently hybrid, and Fabric's zero-copy interoperability with both platforms is what makes hybrid viable rather than a contradiction.
Sixth, the region decides the shape of the landscape before the economics do. India, Qatar and the United Arab Emirates hold durable Microsoft 365 commitments on data location. Four Gulf states hold none. Fabric's full workload set runs in UAE North, Central India and South India (Microsoft Learn, page updated 5 November 2026). It does not run in Qatar Central, UAE Central or India West. Indian residency rules bite per class of data rather than per tenant, so payment data, insurance records and telecommunications network data each carry a rule of their own. A consolidation designed on one global capacity meets several of those rules at once. The sequence that works puts classification before placement, and placement before provisioning. Chapter five sets out the instruments and the vendor footprint behind each of those statements.
Fabric is the primary lens throughout. Databricks and Snowflake appear where the contrast sharpens the decision, and Fabric's interoperability with both is treated as a design feature rather than a concession. On Volge's reading the consolidation decision is an economics decision before it is a technology one, and it does not survive being made on a feature sheet.
The analytics landscape fragmented by accumulation, and the cost of that fragmentation sits in the integration between services, not inside any one of them. Cost leaks through duplicated storage and redundant reserved capacity; latency leaks through every pipeline hop; trust leaks every time two services disagree about the same entity. Consolidation is the lever because it attacks the seams , the copies, the pipelines, and the separate meters , rather than the engines. Read the tax first, because it is the saving that underwrites everything that follows.
No one designed the fragmented landscape. It accreted. A data warehouse arrived first, sized for structured financial and operational reporting. The data science team needed cheap, schema-flexible storage the warehouse could not give them economically, so a data lake followed. Operational use cases needed sub-minute latency the batch warehouse could not serve, so a streaming stack was bought. The business needed dashboards, so a business-intelligence platform was licensed on its own terms. Someone then needed to know what all of this held and who could see it, so a cataloguing and governance tool was added on top.
Each decision was locally rational. The sum is an landscape of five or six separately licensed, separately operated services, each with its own storage, its own compute, its own security model, and its own operational team. The data does not live in one place; it lives in all of them, in copies, and the copies are kept roughly aligned by pipelines that run on a schedule and break on their own one.
The cost of fragmentation is not the cost of the services. It is the cost of holding them together. That cost is distributed, which is why it rarely appears as a number a finance team can point at, and four components carry most of it.
Duplicated storage. The same dataset lands in the lake, is copied to the warehouse, is re-exported to the BI tier's import
model, and is staged again for the streaming joins. One logical dataset becomes four physical copies, each metered, each drifting from the others between refreshes.
Pipeline toil. Every copy is a pipeline, and every pipeline is code that someone writes, monitors, debugs at the wrong hour, and rewrites when an upstream schema changes. Integration debt , brittle interfaces, undocumented transformations, inconsistent access controls , accumulates fastest here, and it is the line of the business case most often underestimated.
Redundant capacity. Each service is sized and reserved on its own meter, against its own peak. Because the peaks do not coincide, the landscape carries idle reserved capacity across several services at once. That capacity is paid for and provisioned, and it sits unused, because compute cannot be pooled across products that do not share one.
Trust erosion. This is the tax that does not appear on any invoice and costs the most. When the warehouse and the BI extract disagree about a revenue figure because each holds its own copy refreshed at a different hour, the data team spends its credibility reconciling them. Numbers that should match and do not are the slow poison of a fragmented landscape, and they are manufactured by copy sprawl, not by any engine being wrong.
A consolidation case stands or falls on a baseline taken before the migration, and most programmes never take one. The measurement is not difficult. It is four counts, each already held somewhere in the landscape, and each in a unit a finance function will accept. Duplicated storage is measured in bytes. Take the gross footprint of every landing, warehouse and extract instance of a dataset, over the footprint of the authoritative copy. A ratio above two says the landscape is paying three times to hold one record. Pipeline toil is measured in engineering days a month, against the count of
pipelines whose only purpose is to move data between two services. Take the days from the change log and the on-call record, never from an estimate.
The other two counts are the ones that move the number. Reserved capacity utilisation is read per meter, as consumed units over reserved units across a full business cycle, because the waste sits in the peak each service reserves for itself and never shares. Reconciliation effort is measured in hours per close, from the finance and data teams' own time records. It should then be split between the reconciliation a regulator requires and the reconciliation two copies of one record require. Only the second is the tax. The first survives consolidation and should never be claimed as a saving.
A defensible baseline has four properties. The measurement window is stated and covers at least one full quarter, each figure has a named owner, the raw extract is retained, and the method is written down before the result is known. A baseline is inadmissible where it rests on a vendor's cost calculator, where it counts headcount the enterprise would carry in any case, or where it prices trust erosion at a number nobody can trace to a source. Trust erosion is real and should be described rather than priced. The quantified tax is the floor of the case, not the whole of it.
The fragmented landscape and the consolidated alternative are easiest to read side by side. The left is the accumulated landscape; the right is the same workloads over one shared lake.
The left-hand landscape spends its effort on the dotted lines , the copies and the catalogue reaching across products that do not share storage. The right-hand landscape removes the dotted lines by removing the copies. That is the whole consolidation thesis in one picture.
The reflex fix for a slow or expensive landscape is to tune an engine or renegotiate a service. The reflex is misdirected, because the cost does not sit in the engines. It sits in the integration between them, and no amount of engine tuning reaches it.
Consolidation attacks the cost where it actually lives. Store the data once and the duplicated storage disappears. Read it in place from every workload and the copy pipelines disappear with it. Pool the compute under one meter and the redundant reserved capacity collapses to a single sizing decision. Govern one copy and the trust erosion stops at the source, because there is one authoritative record rather than a population of disagreeing ones. None of this requires any single engine to be the fastest in its class. It requires the seams to be removed, and removing the seams is what a single platform over one lake is for.
The trade is real and is stated honestly here. Consolidation buys operational simplicity and removes the integration tax; it costs the specialised depth that a dedicated, best-of-breed engine retains. The rest of this paper is the working-through of that trade , the architecture that delivers the consolidation in chapter two, the economics and the migration in chapter three, and the honest limit of the approach in the same chapter, where best-of-breed still wins.
OneLake, the workloads, Direct Lake, governance
Fabric is one software-as-a-service platform, nine workloads over one shared lake, governed and metered as a unit. OneLake is the decision that makes the rest follow , one logical store, one open copy of the data, read in place by every workload. Direct Lake lets Power BI query that copy without importing or duplicating it, which closes the largest remaining seam in the classic BI architecture. The medallion pattern organises the lake into rising tiers of quality, and governance arrives as a layer rather than a bolt-on, through the OneLake Catalog for discovery and item governance and through Microsoft Purview for protection and compliance. Understand OneLake and the rest of the platform is a consequence of it.
OneLake is one unified logical data lake for the entire organisation, provisioned automatically with every Fabric tenant, which Microsoft frames as OneDrive for data (Microsoft, 2025-2026). It is the single most consequential design choice in the platform, because every other workload reads from it.
The architectural payoff is the elimination of copies. OneLake stores data once, in the open Delta Parquet format, and exposes that one copy to every Fabric engine , the warehouse, the lakehouse, the data-science runtime, the real-time engine, and Power BI , without duplication. A shortcut lets data that physically lives elsewhere, in Amazon Simple Storage Service, in Azure Data Lake Storage, or in another organisation's own store, surface inside OneLake without being copied across. The landscape becomes one logical surface over data that may remain physically distributed.
This is the structural answer to the copy sprawl of chapter one. In the fragmented landscape, each service held its own copy and the pipelines kept them roughly aligned. In OneLake, there is one copy, and every workload reads it in place. The pipelines that existed only to move data between services have nothing left to do, and the storage those copies consumed is reclaimed. The open format matters here for the same reason. Tables live in Delta Parquet rather than a proprietary warehouse format, so every engine reads the same files without conversion, which forecloses the lock-in and the re-export proliferation that proprietary formats impose.
Fabric unifies the workloads a complete analytics landscape runs, each presented as a role-tailored experience over the same OneLake storage (Microsoft, 2026). The point is not that each workload is individually best in class; it is that they share one copy of the data, one governance plane, and one capacity meter.
The table below maps each workload to the separately licensed service it consolidates and to the landscape problem it addresses.
| Fabric workload | What it does | Consolidates | Landscape problem it addresses |
|---|---|---|---|
| Power BI | Semantic models and reports, Direct Lake | Power BI Premium | BI queries OneLake in place; no import refresh |
| Databases | SQL database in Fabric for operational data | A separately licensed operational database tier | Operational data lands in OneLake without an export |
| Data Factory | Pipelines, mirroring, 200+ connectors | Azure Data Factory | Ingestion and integration on-platform; mirroring replaces copy pipelines |
| Industry Solutions | Industry-specific data models and solutions | Bespoke industry build-out | Domain models arrive on the platform rather than as a project |
| Real-Time Intelligence | Streaming and event analytics via Eventhouse and KQL, with Activator for triggers and actions | Synapse Data Explorer; separate streaming stack; bespoke alerting glue | Closes the recency gap, and acts on conditions, without a standalone meter |
| Data Engineering | Spark notebooks and lakehouse over OneLake | Synapse Spark; lake compute | Lake and engineering on the shared copy, no separate store |
| Data Science | Notebooks, model training, MLflow | Synapse / Azure ML notebooks | Models train on the curated lake, not on a re-exported slice |
| Data Warehouse | T-SQL warehouse on open Delta tables | Synapse dedicated SQL pools | Warehouse reads the same files as the lake; no copy between them |
| Fabric IQ (preview) | Ontology, Fabric Graph, semantic models, data and operations agents | Bespoke semantic layer | One set of business semantics over the shared copy |
Read the consolidation column down the table. Each row retires a separately licensed, separately operated service, and the retirement is what removes the integration tax, not because any single Fabric workload outperforms the specialist
it replaces, but because all nine now share one copy and one meter.
The classic business-intelligence architecture carries one of the most expensive seams in the landscape, the import. To make a dashboard fast, the BI tier copies data out of the warehouse into its own in-memory model and refreshes that copy on a schedule. The copy is another store to size, the refresh is another pipeline to run and to fail, and the model is stale between refreshes by construction.
Direct Lake removes the seam. It is a Power BI semantic-model storage mode, available in Fabric, that lets the engine read Delta tables in OneLake directly , loading only the columns a query needs into memory , without importing the data and without a scheduled refresh (Microsoft, 2026). It targets near-import query speed with near-real-time freshness, which is the combination the import-versus-direct-query choice never offered.
For the consolidation thesis this is the closing move. The warehouse, the lakehouse, and now the BI tier all read one copy of the data in OneLake. The import copy is gone. So is the refresh pipeline, and the dashboard reflects the curated data as it stands rather than as it stood at the last refresh. Direct Lake is one of the capabilities that becomes available at the F64 capacity tier, which is part of why F64 anchors the economics in chapter three.
A single lake is not the same as an organised one. OneLake removes the copies; the medallion architecture organises what remains into rising tiers of quality, and it is the recommended pattern for structuring a Fabric lakehouse (Microsoft Learn, 2025-2026).
Bronze holds data as it arrived, an unedited record of source. Silver standardises formats, removes duplicates, and resolves each entity to one consistent representation. Gold organises the validated data into curated models fit for reporting and analytics. The tiers operate independently, so a new source can be exercised in bronze without disturbing the gold models the business consumes. Because all three tiers live in OneLake as one copy, the staging happens in place , the data is refined where it sits rather than copied between systems to be cleaned, which is precisely the copy-and-pipeline pattern the consolidated landscape exists to remove.
Two properties make this consolidation rather than relabelling. Lineage is continuous and automatic across lakehouses and pipelines, and across analytics, so the path from a
report back through the gold model, the silver transformations, and the bronze source is recorded rather than reconstructed after an incident. Policy follows the data across one lake rather than being re-implemented per service, so a sensitivity label or access rule set once is honoured by every workload that reads the copy. The OneLake Catalog, OneLake security, and Purview together govern one landscape as a layer. In the fragmented world, the same control had to be configured separately in the warehouse, the lake, the BI tier, and the streaming stack, and the gaps between those configurations were where exposure lived.
In the fragmented landscape, governance was the tool added last and on top, a catalogue reaching across products that did not share a security model, perpetually behind the data it was meant to govern. Fabric inverts that, and it does so across two surfaces rather than one. The OneLake Catalog is the centralised experience for discovering, exploring, securing, and governing Fabric items, and for assessing governance state and acting on recommendations. Microsoft Purview supplies information protection, data loss prevention, audit, and risk and compliance for supported Fabric data, with lineage and classification that travel with the data from ingestion and transformation through modelling to consumption (Microsoft Learn, 2026).
This is also the bridge to the AI-readiness benefit, which this paper treats briefly and by reference. A consolidated, governed, current landscape is the same landscape an enterprise needs to ground AI agents trustworthily. That means one authoritative copy with measured quality, continuous lineage, and policy that follows the data. The full argument for why data quality, not the model, caps agent accuracy is the subject of the companion Volge paper, The data estate is the accuracy budget (Topic 7). The reader who needs the agent-grounding case is directed there. The point for this paper is narrower and stands on the data leader's own terms. The governance that makes consolidation safe is the same governance that makes the landscape AI-ready, so AI-readiness arrives as a by-product of the consolidation rather than as a separate programme.
Four decisions govern a Fabric landscape, and all four are taken before the first dataset lands. They are the capacity and tenant topology, the domain and workspace boundary, the access pattern chosen for each source, and the ownership of each medallion layer. Each is cheap to decide and expensive
to revisit, because each becomes a dependency of everything built on it. A programme that begins by provisioning a capacity and creating workspaces on request has taken all four decisions by default and documented none of them.
Capacity topology answers who pays and who can throttle whom. One capacity for the whole organisation gives the best pooling and the worst blast radius, because a single runaway notebook consumes the units the finance close needs. One capacity for each business unit inverts both properties. The workable middle is a small number of capacities aligned to funding boundaries, with a separate capacity for anything that must not be starved and another for development. Capacity placement also fixes the region. The region fixes the law that applies, which is why chapter five belongs before the provisioning decision rather than after it.
Domain and workspace boundaries decide whether governance is enforceable. A domain holds the data of a business area and carries its own stewards and policy; a workspace holds the items a team builds. Where workspaces are created per project, the lake acquires a shadow structure nobody owns within a year. The rule that survives is one workspace per team and lifecycle stage, with the medallion layers separated by workspace rather than by folder, so that permissions are granted on a boundary the platform itself recognises.
The access pattern for each source is the decision with the most money in it. A shortcut leaves the data where it is and reads it in place, which suits large volumes already held in a governed lake. Mirroring brings an operational database into OneLake continuously, which suits systems that change frequently and queries that cannot tolerate a source outage. A copy is justified on four conditions only: the source cannot be reached directly, the contract forbids direct access, the source cannot carry the read load, or the transformation is heavy enough that re-reading the source is the greater cost. Ask of every proposed copy which condition it meets. A copy that meets none is the integration tax being rebuilt inside the new platform.
Medallion ownership decides whether the layers mean anything. Bronze is owned by the ingestion team and is never edited. Silver is owned by the domain and carries a published contract, namely a schema, a stated refresh frequency and a quality test that fails loudly. Gold is owned by the consumer and may be rebuilt at will. Promotion between layers needs a rule written in advance, naming who may promote, which test must pass, and what a consumer is owed when a contract changes. Without that rule silver becomes a staging area and gold becomes the new warehouse.
Each of those decisions fails in a recognisable way, and the failure shows up in production rather than in review. A single shared capacity fails as intermittent report timeouts during the close, reported by the business as a reporting problem and diagnosed weeks later as a notebook. Workspace sprawl fails as a request for a report nobody can trace to a source. A copy taken for convenience fails as two numbers in two decks, which is the trust erosion of this chapter arriving inside the consolidated platform.
Two further failures are worth naming because they are quiet. An unowned silver layer fails slowly. Consumers build directly on bronze to avoid waiting for the domain, and within two quarters the lake has a second, undocumented serving layer. A capacity sized from a vendor table rather than from observed consumption fails at the first month-end, when a heavy batch load and an interactive peak arrive in the same hour. Neither failure produces an incident. Both produce a landscape that looks consolidated and behaves fragmented.
Fabric's commercial mechanism is one pooled capacity meter that replaces several per-service meters, and the total-cost comparison turns on capacity sizing rather than on headline prices. F64 is the inflection that unlocks Power BI Premium-equivalent features and Direct Lake, which is why it anchors most enterprise deployments. The migration off Synapse, standalone Power BI Premium, and Azure Data Factory is a staged programme with real cutover risk, underwritten by the integration tax it retires. And consolidation is not the answer everywhere: Databricks and Snowflake retain genuine, specialised advantages, and the honest architecture for many landscapes is hybrid.
Fabric replaces per-service licensing with a single pooled compute meter. Capacity is purchased as an F-SKU, measured in capacity units, and that one pool of compute is shared across every workload. The warehouse and the lakehouse, the pipelines and the real-time engine, and Power BI all draw from it (Microsoft, 2026). This is the commercial expression of the architecture. One platform, one lake and one meter.
The SKU range is wide. Microsoft lists thirteen F-SKUs, running from F2 to F8192. On pay-as-you-go billing, at about 0.18 United States dollars per capacity unit per hour for capacity
left running continuously, that is roughly 263 dollars a month at F2 and roughly 1,076,000 dollars a month at F8192. A one-year or three-year reservation saves about 41 per cent against pay-as-you-go, and enterprise-agreement rates are typically below list (Microsoft Fabric pricing, verified 8 November 2026). Pricing changes and is region- and contract-specific, and the figures here should be reconfirmed against current Microsoft pricing before any commitment.
| F-SKU | Approx. capacity units | Approx. monthly list, pay-as-you-go | Typical fit |
|---|---|---|---|
| F2 | 2 | ~USD 263 | Development, small workloads, evaluation |
| F8 | 8 | ~USD 1,051 | Departmental analytics |
| F64 | 64 | ~USD 8,410 | Inflection: Power BI Premium P1 equivalent + Direct Lake; common enterprise start |
| F128 | 128 | ~USD 16,819 | Large enterprise; common Fortune 500 starting band with F64 |
| F256 | 256 | ~USD 33,638 | Heavy, broad landscape |
| F2048 | 2048 | ~USD 269,107 | Very large, multi-domain landscape |
| F8192 | 8192 | ~USD 1,076,429 | Top of the published range |
Every row is a pay-as-you-go list price for capacity running continuously, at about USD 0.18 per capacity unit per hour over a 730-hour month (Microsoft Fabric pricing, verified 8 November 2026). A one-year or three-year reservation saves about 41 per cent against these figures, which puts F64 reserved near USD 4,960 a month. Pricing is region- and contract-specific and changes; reconfirm against current Microsoft pricing.
The F64 tier, at roughly 8,410 United States dollars per month on pay-as-you-go and nearer 4,960 on a one-year reservation, is where the economics turn. The reason is specific. F64 is the Power BI Premium P1 equivalent, which is the tier at which Fabric includes Power BI Premium-equivalent capabilities and makes Direct Lake available across the workloads (Microsoft Fabric pricing, verified 8 November 2026). Two consequences follow.
This is why F64 to F128 is the common starting band for large enterprises and why the total-cost question is a capacity-sizing question rather than a headline-price comparison. The list price of an engine is the wrong unit of analysis; the right one is the total of capacity, retired per-seat licensing, reclaimed duplicate storage, and removed pipeline operation, set against the several meters the consolidated landscape replaces.
First, report consumers no longer need individual Power BI Pro licences. At F64 and above, viewers consume reports on free licences. For an enterprise with thousands of report consumers that can dominate the total-cost comparison on its own, because the per-seat Pro licensing that a standalone Power BI deployment carries collapses into the capacity. Second, Direct Lake becomes available, which removes the import-and-refresh seam described in chapter two and, with it, the duplicated import storage and the refresh pipelines.
The total-cost case for consolidation is not that any one Fabric workload is cheaper than its specialist counterpart. It is that the consolidated landscape removes whole categories of cost that the fragmented landscape carries structurally. The table sets the two side by side.
| Cost component | Fragmented multi-service landscape | Consolidated on Fabric |
|---|---|---|
| Compute licensing | Separate meter per service, each sized to its own peak | One pooled capacity meter shared across workloads |
| Storage | Duplicated copies per service | One copy in OneLake; copies reclaimed |
| BI licensing | Per-seat Pro for every consumer | Free viewers at F64+; licensing in the capacity |
| Pipeline operation | Copy pipelines between every service | Copy pipelines removed; data read in place |
| Idle reserved capacity | Redundant across non-coincident peaks | Single pooled sizing decision |
| Governance tooling | Separate catalogue and policy per service | OneLake Catalog and Purview over one landscape |
| Operational headcount | Specialists per service and per integration | One operational surface and skill base |
The saving concentrates in the rows that describe the seams. The seams are duplicated storage and copy pipelines, redundant capacity and per-seat licensing, and the headcount that maintains the integration. Those are precisely the integration-tax components of chapter one, and they are the components consolidation retires. The compute-licensing row is the one that requires care. A poorly sized capacity that throttles under load, or an oversized one that idles, can erase the saving. That is why capacity sizing and the governance of capacity consumption are where consolidation programmes are won or lost in practice.
The landscape Fabric consolidates is, for most enterprises, an Azure landscape already: Azure Synapse Analytics, Azure Data Lake Storage, Power BI Premium, and Azure Data Factory. The migration is the work of moving those onto the one platform, and it is a programme rather than a switch.
Microsoft has not declared Azure Synapse Analytics end-of-life wholesale, and that nuance matters for planning. What is clear is the strategic direction and a set of targeted deprecations. Synapse dedicated SQL pools receive security updates but no new features, Synapse Data Explorer was retired in favour of the Fabric Eventhouse on 7 October 2025, and migration tooling , assessment-first pipeline and warehouse migration assistants , has shipped to support the move (Microsoft Learn, 2025-2026). No retirement date exists for Azure Data Factory either, and the only dated item there is the retirement of its Legacy Trusted Service mode in August 2027. Fabric is positioned as the long-term platform, and the deprecations point one way.
Stage one , assess and land. Stand up the OneLake foundation and a right-sized capacity, inventory the Synapse, ADLS, Power BI Premium, and ADF landscape, and run an assessment-first compatibility review. The objective is a landed platform and an honest map of what moves cleanly and what does not.
Stage two , migrate the warehouse. Move Synapse dedicated SQL workloads to the Fabric Data Warehouse, validating query parity and performance against the open Delta tables. This is the stage with the most cutover risk, because reporting depends on it; run it in parallel before cutting over.
Stage three , move pipelines and BI. Migrate Azure Data Factory pipelines to Fabric Data Factory, and move Power BI Premium semantic models to Direct Lake on OneLake, retiring the import copies and refresh schedules. The objective is the BI tier reading one copy in place.
Stage four , make current and decommission. Migrate streaming and event workloads to Real-Time Intelligence on the Eventhouse, then decommission the legacy services and their separate meters. The decommissioning is where the integration-tax saving is actually realised; until the old meters are switched off, the enterprise pays for both landscapes.
The cutover risk is real and is the reason for the parallel-run discipline. The dominant failure mode is decommissioning a legacy service before its Fabric replacement has been validated at production load, then discovering a capacity-sizing or feature-parity gap with no fallback. Migrate, validate in parallel, then decommission , in that order, never the reverse.
Capacity is sized from observed consumption, not from a table of typical fits. The inputs are the concurrency at the peak hour rather than the mean, the duration of the heaviest scheduled job, the refresh profile of the semantic models the business actually opens, and the headroom a close or a quarter-end needs. Each is measurable in the landscape being replaced. A sizing that cannot show those four inputs is a guess wearing a SKU number, and it errs in the vendor's direction. The discipline that works is simple. Size for the observed peak, run a full business cycle, then resize on evidence rather than on complaint.
When a capacity runs out of units the symptom reaches the business before it reaches the platform team. Interactive reports slow and then queue. Failures follow, and the first report is a complaint about a dashboard. The response has an order. Identify the consumer that moved, not the report that broke. Move the offending workload to its own capacity or its own schedule before buying a larger SKU. An oversized capacity hides the behaviour that caused the problem and then charges for it every month. Raise the SKU where the load is genuine, sustained and attributable to a funded outcome.
The parallel run is the largest single cost of the migration and the one most often left out of the business case. For the length of each stage the enterprise pays the legacy meter and the Fabric capacity at once, plus the engineering to keep two pipelines producing the same answer. That cost is bounded only by the length of the stage, which is why a stage with no exit test runs indefinitely and consumes the saving it was meant to prove. Budget the overlap explicitly, stage by stage, and treat an overrun as a programme issue rather than as an operating cost.
A rollback path belongs to each stage and expires only when the stage closes. In practice the legacy service stays running
and reachable, its data continues to refresh, and the switch back is tested once rather than assumed. The test is cheap while both landscapes exist. It is impossible afterwards, which is why the order of operations in this chapter never changes. Migrate, validate at production load, then decommission.
Each stage closes on a test rather than on a date. The tests below are the minimum, and each is passed against production load rather than against a sample.
Reconciliation during the parallel run is the part teams underestimate, because proving that two warehouses agree is harder than migrating one. The test is not a row count. It is a set of named measures, each at the grain the business reports it, compared across both landscapes for the same period, with a stated tolerance and a documented explanation for every difference inside it. Differences will appear, and most will be legitimate: a late-arriving record, a different time zone at the boundary of a day, a rounding convention carried in a legacy view. Each has to be identified once and then suppressed deliberately, rather than re-investigated every cycle. Two consecutive closes that tie out on that basis is the evidence a finance function will accept. One close that ties out is a coincidence until the second confirms it. Budget the work explicitly, as engineering days per measure rather than as a contingency, and name the person in finance who signs it off.
Consolidation is a trade, and the trade does not favour Fabric everywhere. A data leader is owed the honest version of where best-of-breed still wins.
Databricks is the stronger platform for large-scale data engineering and machine learning. It was founded by the creators of Apache Spark and built Delta Lake into a de facto open-format standard; its Spark performance, its granular Unity Catalogue governance, its mature ML and model-serving stack, and its multi-cloud reach are the reasons engineering-heavy and ML-heavy landscapes choose it (industry analysis, 2026). Its scale reflects that position: a revenue run-rate above 7 billion United States dollars, growing more than 80 per cent, with more than 1,000 customers consuming above one million dollars a year (Databricks, August 2026). Where the workload is large-scale, code-first data engineering or production ML at the frontier, Databricks retains a genuine ceiling Fabric does not match.
Snowflake is the stronger platform for high-concurrency SQL warehousing and frictionless, secure data sharing. Its separation of storage and compute, its elastic per-warehouse scaling, and its data-sharing and marketplace capabilities are mature and hard to beat for that profile (industry analysis, 2026). Its scale is substantial: 14,554 customers, with 828 of them above one million dollars in trailing-twelve-month product revenue, in the quarter ended 31 July 2026 (Snowflake earnings, Q2 FY2027, 2 September 2026). Where the requirement is heavy concurrent SQL analytics across many tenants, or data sharing across organisational boundaries, Snowflake retains advantages Fabric does not fully close.
| Decision axis | Choose Fabric | Choose Databricks | Choose Snowflake |
|---|---|---|---|
| Primary goal | Consolidate a fragmented landscape; cut integration tax | Large-scale data engineering and ML | High-concurrency SQL; data sharing |
| Ecosystem | Microsoft, Azure, Power BI landscape | Multi-cloud, open, code-first | Multi-cloud, SQL-first |
| Strength | Unification; BI integration; SaaS simplicity | Spark depth; ML maturity; open governance | Concurrency; elastic scaling; sharing |
| Team profile | Mixed, BI-led, low-to-pro-code | Engineering- and ML-heavy | SQL- and analyst-heavy |
| Honest limit | Specialist engineering and warehousing ceiling | Less unified; heavier to operate | Narrower than a full unified landscape |
The same trade reads as a selection decision-tree, mirroring the axes of the table above.
The decisive practical point is that this is not a single choice for the whole landscape. Fabric's bi-directional, zero-copy interoperability with both Databricks and Snowflake means an enterprise can consolidate the fragmented majority of its landscape onto Fabric while leaving a specialised engineering or warehousing workload on the platform that serves it best,
sharing data between them without copying it (Microsoft, 2025-2026). The honest architecture for a large landscape is frequently hybrid, and the interoperability is what makes hybrid coherent rather than a return to the copy sprawl consolidation set out to remove.
A durable consolidated landscape is layered, open, and governed end to end: sources unified into OneLake, refined through the medallion tiers, governed through Purview, made current through Real-Time Intelligence, and consumed by Power BI through Direct Lake and by every other workload on one copy. The architecture is the easy part. What makes it defensible is a control with a test behind it, a named failure mode with a detection, a measure taken from a baseline, and an exit criterion a steering committee can refuse to waive.
The architecture below is anchored to Fabric, in line with the paper's lens, but the layering is portable. Each layer can be sourced, governed, and evolved on its own, which is the structural hedge against both lock-in and instability.
Read the architecture as one governed pipeline feeding several consumers from a single copy. The unification choices on the left , mirroring for operational systems that change often, shortcuts for large data already sitting in a governed lake, connectors for SaaS, and direct ingestion for streams , all converge on one OneLake copy. Every consumer on the right reads that copy rather than its own re-export. The governance plane spans both. That is the consolidated landscape; everything else is sizing and sequencing.
The architecture above is not buildable until five things exist, and none of them is a Fabric feature. They are a classification scheme with an owner, an access model expressed in groups rather than in individuals, a named funded owner for each data domain, a source-system contract for every system in scope, and a capacity budget somebody controls. A programme that starts without them does not stall. It proceeds, and absorbs each missing decision as a default nobody chose.
The order matters as much as the list. Classification and the access model gate everything that follows, because they decide what may be placed where and who may read it. The source contracts gate the pipelines. The capacity budget gates the sizing. A programme that can name an owner
against each of the five is ready to build. One that cannot is ready to write a design document.
The roadmap is the migration of chapter three set against the maturity model below. It is disciplined on validation and conservative on decommissioning by design, because the failure mode is always the same, a legacy meter switched off before its replacement has earned the trust.
Phase one, foundation. Land OneLake, size an initial capacity at F64 or F128, and connect the first sources through mirroring and shortcuts. Stand up Purview from the start rather than after. The objective is a governed platform and a baseline.
Phase two, consolidate the core. Migrate the warehouse and the primary pipelines, build the medallion tiers, and move the highest-value Power BI models to Direct Lake. Run the legacy and Fabric landscapes in parallel. The objective is the core reporting landscape reading one copy.
Phase four, decommission and optimise. Retire the validated legacy services and their meters, tune capacity against
observed consumption, and govern capacity to prevent throttling and idle waste. The objective is the realised saving, which arrives only when the old meters are switched off.
Phase three, extend and make current. Add Real-Time Intelligence where recency determines accuracy, extend to the data-science workloads, and bring adjacent domains onto the platform. The objective is the breadth of the landscape consolidated, not just the core.
The model locates the enterprise and defines its next increment. It is the diagnostic counterpart to the roadmap.
| Level | Description | Landscape and storage | Governance and capacity | Typical outcome |
|---|---|---|---|---|
| 0 , Fragmented | Separately licensed services; copies everywhere | Many stores; duplicated copies | Per-service; bolted-on catalogue | Full integration tax; trust erosion |
| 1 , Landed | OneLake stood up; first sources connected | One lake emerging beside legacy | Purview started; capacity sized | Foundation set; saving not yet realised |
| 2 , Core consolidated | Warehouse and core BI on Fabric; Direct Lake live | One copy for core; legacy in parallel | Lineage and policy active; capacity tuned | Copies and import refreshes retired for the core |
| 3 , Landscape consolidated | Pipelines, science, real-time on platform | One copy across the landscape | Policy follows data; capacity governed | Most integration tax removed |
| 4 , Optimised unified landscape | Legacy decommissioned; hybrid only by design | One copy; best-of-breed by deliberate choice | Landscape-wide governance; capacity optimised | Saving realised; AI-ready by-product |
On Volge's own assessment, rather than on any published survey, most enterprises sit between Level 0 and Level 1 as at late 2026, with consolidation under way but legacy meters still running in parallel. The saving is realised at Level 4, when the legacy services are decommissioned, not at Level 1, when the platform is merely landed. Any residual best-of-breed workload at Level 4 is hybrid by deliberate design, connected through zero-copy interoperability rather than by reintroduced copies.
The consolidation reads most clearly as a shift in the conditions under which the landscape operates.
| Condition | Fragmented landscape | Consolidated on Fabric |
|---|---|---|
| Data location | Copies across many services | One copy in OneLake |
| Storage format | Proprietary per service | Open Delta Parquet, read by all |
| BI delivery | Import copies and scheduled refresh | Direct Lake on one copy |
| Compute meter | One per service | One pooled capacity |
| Governance | Bolted-on, per service | OneLake Catalog and Purview as a layer across the landscape |
| Real-time | Separate streaming stack | Real-Time Intelligence on-platform |
| Operational surface | Several teams and skill sets | One platform, one skill base |
A single copy of the data is only defensible if somebody can prove it. The controls below are the minimum set for a consolidated landscape, and each is written as something testable rather than as a policy statement. The test matters more than the control. A classification scheme with no sampling test is a spreadsheet. A lineage claim nobody has traced end to end is a diagram. Each control also produces evidence, which is what an auditor, a regulator or an incoming chief data officer asks for. Evidence is what separates a governed landscape from a tidy one.
| Control | What it enforces | How you test it | Evidence it produces |
|---|---|---|---|
| Single authoritative copy | One owning workspace per dataset, with every other instance declared a shortcut, a mirror or a retired copy | Reconcile the copy register against the lake's own item inventory each quarter, and query two named consumers for the same total | A copy register with an owner against every entry, and a dated reconciliation |
| Data domain residency | Each domain placed in a region permitted for its class, with processing stated separately from storage | Sample five datasets per domain and trace the region of the capacity, the region of the source and any support access from outside the geography | A versioned residency register, one line per data domain |
| Classification at ingestion | Every dataset carries a classification before it reaches silver | Attempt to promote an unclassified dataset and confirm that the promotion fails | A failed-promotion log |
| Access on a boundary | Permissions granted on the workspace and domain boundary rather than item by item | Pull the item-level permission exceptions and require a named justification for each | An exception list, shrinking between reviews |
| Control | What it enforces | How you test it | Evidence it produces |
|---|---|---|---|
| Continuous lineage | Every published report traces to its source without manual annotation | Take the two reports the board uses most and walk the lineage back to the source system | Two traced lineage paths, dated |
| Capacity governance | Consumption attributable to a funded owner, with no unbounded workload | Replay the heaviest week and confirm that every consumer is attributable | A consumption report by owner |
| Retention and erasure | Retention per data class, including any statutory floor | Run an erasure request end to end on a test subject and confirm that each medallion layer and the backups honour it | A completed erasure drill record |
| Log integrity | Access and change logs retained for the period the applicable rules require, in a permitted location | Request a log extract for a named dataset and a named hour the way a supervisor would, and time it | A dated log extract and the elapsed time to produce it |
Two of those controls are commonly skipped, and both are the ones that fail an examination. The erasure drill is skipped because it is awkward, since an erasure that reaches bronze, silver, gold and the backup copies touches every layer the medallion pattern created. The log extract is skipped because it looks trivial until it is timed. Where the applicable rules require production within a stated period, the control is the elapsed time and not the existence of the log. Source: Volge analysis, 2026, written against the instruments set out in chapter five.
A control list is only half the work, because the failures that matter announce themselves in the business rather than on the platform. The table below names the ones seen most often in consolidation programmes, with the detection that catches each one early enough to be cheap. Read the second column first. It is what somebody will report, and the point of the exercise is to recognise the cause from the symptom without a month of investigation.
One failure deserves separate treatment because it is invisible until it is expensive. Residency drift happens through ordinary provisioning. A team needs a capacity, the portal offers a region, and a regulated domain acquires a new location without anybody deciding. The control is to restrict provisioning to the regions already approved for that domain, and to make the exception route amend the register rather than
| Failure mode | What it looks like in production | How it is detected | What closes it |
|---|---|---|---|
| Copy sprawl inside the platform | Two Fabric items report different totals for the same measure, and each has a defender | Scheduled comparison of named measures across items, run as a job rather than as an audit | A copy register, and deletion of the loser once its consumers have been moved |
| Capacity starvation at the close | Interactive reports queue or fail in the last three days of the month | Peak-hour consumption by consumer, held against the close calendar | Workload separation or rescheduling, taken before a larger SKU is bought |
| Unowned silver | Consumers build on bronze to avoid waiting for the domain | Count of gold items reading directly from bronze | A published contract for every silver table, with a named steward |
| Semantic models sized on a sample | A model performs well against test volumes and slowly against production ones | Query duration distribution per model, compared with its predecessor | Model or table redesign, taken before the report is published |
| Residency drift | A capacity or workspace is created in a convenient region and a regulated domain follows it | Region of every capacity and workspace reviewed against the residency register | Provisioning restricted to approved regions, with an exception route that changes the register |
| Decommissioning before validation | A legacy service is switched off and a gap appears at the next close, with no fallback | The stage exit tests, which is their only purpose | Reinstatement where it is still possible, and a written stage gate where it is not |
| Pipeline drift | A migrated pipeline succeeds while producing a stale or partial result | Freshness and row-count assertions on the target, not pipeline status | Assertions promoted to blocking, with a named owner paged |
bypass it. Chapter five sets out why the register is kept per data domain and not per tenant.
The pattern across that list is that the symptom and the cause sit in different teams. A business user reports a slow report and the cause is a notebook in another workspace on the same capacity. A finance analyst reports a wrong number and the cause is a copy taken for convenience eighteen months earlier. Detection therefore cannot sit with the team that feels the symptom. It has to be instrumented on the platform, against named measures and named consumers, and reviewed on a cadence somebody owns.
Measure the conditions the consolidation was meant to change, against a baseline taken before it started. Six
measures carry the case. Each has a definition that fits in a sentence, a source inside the landscape, and a discipline about the baseline that matters more than the target does.
What is deliberately absent here is a single maturity score. A score aggregates these six into a number nobody can act on, and it improves when the easiest of them improves. The maturity model above does a different job, which is to locate an enterprise and name its next increment. Keep the six measures separate, dated and owned by name. Source: Volge analysis, 2026.
Done is a set of conditions, and a programme that cannot state them is not sequencing a migration but running a platform project. The conditions below are expressed per stage so that a steering committee can refuse to close a stage.
Each is observable by somebody outside the programme, which is the only property that makes an exit criterion useful.
A governed landscape decays unless something decides on a rhythm, and the rhythm costs less than the remediation. Four forums carry the work, and each exists to take a named decision rather than to review a report. Keep them short and keep the decision rights explicit, because a forum with no decision right becomes a status meeting and is then cancelled for being one.
The evidence each control produces needs a home and a retention period, and both are decisions rather than defaults. Keep the registers, the drill records and the dated extracts where an auditor can reach them without the platform team's help. Evidence only one team can produce is evidence a supervisor will discount. Retention follows the longest applicable requirement rather than the most convenient one. In India it is a floor rather than a ceiling, since rules 6(1)(e) and 8(3) of the Digital Personal Data Protection Rules, 2025 require a minimum of one year for personal data, associated traffic data and logs of processing, once that tranche commences on 13 May 2027.
The architecture names the target, the roadmap sequences the journey, and the controls decide whether the result can be defended. Follow the sequence and the landscape consolidates onto one governed copy and the integration tax is retired. Skip the validation discipline and the programme either throttles in production or pays for two landscapes at once. Skip the control tests and it pays for one landscape it cannot evidence.
The platform is not available everywhere its infrastructure is. Qatar has an Azure region, a Microsoft 365 residency commitment and a Foundry presence, and it cannot run the Fabric workloads this paper is about. Saudi Arabia has no region and no residency commitment of any kind, against a law that forbids exporting government agency data. India's rules attach to classes of data rather than to tenants, which makes residency a question about domains and not about a tenant. Classification comes before placement, and placement before provisioning.
The platform this paper argues for is not available in every country that can run it. Qatar Central is the Azure region at Doha. It has three availability zones and a Microsoft 365 Local Region Geography behind it, and for Fabric purposes it is a Power BI only region (Microsoft Learn, Fabric region availability, page updated 5 November 2026). The lakehouse cannot run there. Neither can the warehouse, data engineering or Real-Time Intelligence. Microsoft's own remedy is stated
on the same page, which is to create a capacity in a region where Fabric is available. For a Qatari enterprise that means leaving the country.
That single fact is the right way into the regional picture. It separates two questions a consolidation programme usually merges. Infrastructure presence is not platform availability, and platform availability is not a residency commitment. A country may hold all three, two of the three, or none. Four Gulf states hold none. The order of work changes as a result. Classification comes before placement, and placement comes before provisioning. The consolidation economics of chapter three are then calculated inside whatever those two allow.
Read Microsoft's own availability pages against each other and the Gulf picture is uneven in a way the policy rhetoric obscures. UAE North is the only Gulf region carrying the full Fabric workload set. UAE Central, at Abu Dhabi, is Power BI only and has no availability zones. It is also a restricted-access region, to which a subscription must request access through the Azure region access request process (Microsoft Learn, Azure regions list, page updated 13 October 2026). India runs the full set at Central India and South India. India West is Power BI only.
The sharpest item in the comparison is an absence. India South Central, the Hyderabad region, appears in the Azure regions list with three availability zones and Central India as its pair. It does not appear in the Fabric region availability table at all (Microsoft Learn, pages updated 13 October and 5 November 2026). A new Azure region does not bring Fabric with it. An architecture that assumed otherwise has planned a capacity where the platform is not documented as available. Settle that with the vendor in writing, not in a design review.
Qatar Central carries a second constraint, and a lakehouse with a recovery obligation feels it. It is an unpaired region, as are Israel Central, Italy North, Poland Central and Spain Central, so the Azure constructs that depend on a region pair do not apply to it (Microsoft Learn, page updated 13 October 2026). Recovery is therefore designed explicitly, across regions the organisation chooses for itself. That choice reopens the residency question. The in-country region was supposed to close it.
| Jurisdiction | Azure region | Fabric workloads in region | Microsoft 365 durable commitment | Copilot Studio in region |
|---|---|---|---|---|
| Saudi Arabia | None | None | None | No |
| United Arab Emirates | Two, UAE Central restricted | UAE North only; UAE Central is Power BI only | Product Terms, Multi-Geo and Advanced Data Residency | Yes, UAE North |
| Qatar | One, unpaired | None; Power BI only | Product Terms, Multi-Geo and Advanced Data Residency | No; data stored in the United States |
| India | Four, two with availability zones | Central India and South India; India West is Power BI only | Product Terms, Multi-Geo and Advanced Data Residency | Yes, two regions |
| Kuwait, Oman, Bahrain | None | None | None | No |
Sources: Microsoft Learn region and data-location documentation, pages updated between 8 October and 5 November 2026, verified 8 November 2026. Compilation by Volge. On the last column, Microsoft states that where a tenant's location is not listed in the Copilot Studio data locations table, data is stored in the United States (Microsoft Learn, page updated 30 April 2026).
Saudi Arabia combines the region's most elaborate localisation apparatus with the thinnest vendor footprint of any large Gulf market. Microsoft's published Azure regions list carries no Saudi entry under any name, live, restricted or in preview, the Middle East entries being Qatar Central, UAE Central, UAE North and Israel Central (Microsoft Learn, page updated 13 October 2026). The Kingdom is absent from Microsoft 365 data residency as well. It is not a Local Region Geography and is not eligible for the Advanced Data Residency add-on. It does not appear in the table of durable commitments on data location (Microsoft Learn, page updated 27 October 2026).
What that absence means is stated by Microsoft rather than inferred. A Saudi tenant falls into the category Microsoft calls All Other Geographies. There, customer data "isn't committed to reside in any particular datacenter", and Microsoft "stores data in a location that enables effective service delivery, and that location is subject to change without notice" (Microsoft Learn, page updated 27 October 2026). Kuwait, Oman and Bahrain sit in the same category. Qatar, the United Arab Emirates and India do not.
Set that against Saudi law and the collision is complete. Article 3-3-5 of the Cloud Computing Services Provisioning
Regulations version 4 prohibits a provider or a subscriber from transferring content comprising data of Saudi government agencies outside the Kingdom. The prohibition covers any purpose and any form, permanently or temporarily, including temporary storage and backup, unless another Saudi instrument expressly permits it. The Regulations were issued by the Communications, Space and Technology Commission under Decision No. 506/1445 and took effect on 10 October 2023. The article number and the wording rest on named law-firm commentary, Aldhabaan Law Firm writing in the Chambers Cloud Computing 2026 guide, because the CST file itself could not be read. The law forbids export of that data. The vendor offers no commitment to avoid it.
Three further Saudi facts shape the architecture. A provider serving any Saudi government customer must hold CST registration at Class A or above. Class A covers public government data only. Confidential requires Class B, and secret or top secret requires Class C, per CST's own register. For a financial institution the binding constraint is an approval rather than a geography. The Saudi Central Bank's Cyber Security Framework, No. 381000091275 of 24 May 2017 and in force, states at 3.4.3 that in principle only cloud services located in Saudi Arabia should be used, with explicit SAMA approval required where they are not. It also requires SAMA approval before cloud services are used at all. SAMA's Rules on Outsourcing, No. 41027017 of 15 December 2019, add a written no-objection for overseas outsourcing, with a rationale for why the work cannot be done within the Kingdom.
One widely repeated claim should be dropped. The National Data Management Office's Data Management and Personal Data Protection Standards, version 1.5 of January 2021, contain no data residency, localisation or in-Kingdom hosting requirement, which was established by searching the whole instrument. The National Cybersecurity Authority's Cloud Cybersecurity Controls, CCC-2:2024, deleted the sub-controls of the 2020 edition that had required cloud services to be provided from inside the Kingdom. It recorded that localisation controls had moved to the NDMO, and the receiving instrument has not been identified. Classification vocabulary diverges as well. The SDAIA Data Classification Policy, version 1 of 5 May 2020, uses Top Secret, Secret, Restricted and Public, and gives personally identifiable information as an example of Restricted. CST's registration classes use a different vocabulary again. Quote the instrument being relied on, and name it.
The honest options for a regulated Saudi workload do not include a sovereign Azure region. Microsoft's own documentation points elsewhere. The features that distinguish Sovereign Public Cloud are documented as European Union and EFTA features, namely the EU Data Boundary, Data Guardian and operations controlled by European residents. The only two National Partner Clouds Microsoft names are Bleu in France and Delos Cloud in Germany (Microsoft Learn, pages updated 31 March 2026). The branch that answers a Saudi or Kuwaiti question is Sovereign Private Cloud. That means Azure Local and Microsoft 365 Local, running on infrastructure the customer or a local partner operates. What those components include against the cloud service is not established in the documentation this paper relies on, and nor is whether Fabric runs on them in any form. Establish both in writing before committing. Outside Europe, Microsoft's sovereignty story is encryption and policy rather than jurisdiction.
The commitment a Gulf or Indian enterprise holds is about where data rests. It is not about where the data is worked on. India, Qatar and the United Arab Emirates are Local Region Geographies, so a tenant in any of the three holds durable commitments on data location for Exchange Online, SharePoint, OneDrive, Teams and Copilot (Microsoft Learn, page updated 27 October 2026). Those commitments come through Product Terms, Multi-Geo and the Advanced Data Residency add-on. Every one of them is about storage. The European Union Data Boundary is the only processing commitment Microsoft publishes, and eligibility rests on a sign-up location in the European Union or EFTA. There is no Gulf or Indian equivalent.
Advanced Data Residency is also sold the wrong way round. The core productivity services already carry a Product Terms commitment for an eligible tenant. What the add-on buys, outside Europe, is a durable in-country commitment over the security and compliance tier: Microsoft Defender for Office P1, Exchange Online Protection, Office for the web, Viva Connections and six named Purview services (Microsoft Learn, page updated 27 October 2026). The six are Audit Standard, Audit Premium, Data Lifecycle Management, Data Loss Prevention, Information Barriers and Information Protection. The add-on also admits no partial adoption. Every paid licence in the tenant must carry one.
Some workloads leave the region by default, and no add-on brings them back. Viva Insights Advanced, Viva Learning and Planner default to the European macro region for every Gulf state, with Oman's Viva Learning going to Asia Pacific instead
(Microsoft Learn, page updated 8 October 2026). Microsoft Forms data for every Gulf and Indian tenant sits in the United States. Advanced Data Residency covers none of those services, so there is no paid remedy. India has a dedicated Planner geography, IND7, while its Viva data goes to Asia Pacific. For an analytics programme the consequence is narrow and worth stating. Telemetry and survey data that feed adoption reporting may sit outside the geography the lakehouse is committed to.
India's residency rules do not attach to a tenant. They attach to classes of data, which is why an Indian lakehouse is designed per domain. The Digital Personal Data Protection Act, 2023 is phasing in. The Digital Personal Data Protection Rules, 2025, notified on 13 November 2025 as G.S.R. 846(E), commence in tranches: rules 1, 2 and 17 to 21 on notification, rule 4 on consent managers from 13 November 2026, and rules 3, 5 to 16, 22 and 23 from 13 May 2027. Everything of commercial consequence sits in the last tranche. Until then section 43A of the Information Technology Act, 2000 and the SPDI Rules remain the operative Indian data security provisions.
Two of those rules bear directly on a medallion design. Rule 6(1) requires encryption, obfuscation, masking or virtual tokens, appropriate access control for computer resources, and visibility of access through logs, monitoring and review. Rules 6(1)(e) and 8(3) impose a minimum one-year retention of personal data, associated traffic data and logs of processing, binding on a processor engaged by a fiduciary as well. That is a retention floor. It cuts against deletion by default, and against aggressive expiry in the bronze layer. Rule 7 then requires breach intimation to each affected data principal without delay. The Data Protection Board is told without delay as well, and again in detail within seventy-two hours. There is no de minimis threshold at all.
The localisation lever in the DPDP instruments has not been pulled. Rule 13(4) permits the Central Government to specify personal data, and the traffic data pertaining to its flow, that may not be transferred outside India. The recommendation comes from a committee of officials, and the rule reaches only a Significant Data Fiduciary once notified, from 13 May 2027. No data has been specified. No committee has been announced. Section 16 works as a negative list rather than as an adequacy whitelist, so transfer is permitted by default and restricted only to a country the Government names. No country has been named.
The binding Indian residency rules are sectoral, and each lands on a different data domain inside the same lakehouse. The Reserve Bank of India's Storage of Payment System Data circular of 6 April 2018, RBI/2017-18/153, requires at clause 2(i) that the entire data relating to payment systems be stored in a system only in India. The RBI's FAQs of 26 June 2019 permit processing abroad, on one condition. The data must be deleted abroad and brought back to India within one business day or twenty-four hours, whichever is earlier. Retention abroad pending dispute resolution is not permitted. SEBI's Framework for Adoption of Cloud Services by SEBI Regulated Entities, circular of 6 March 2023 and in force, requires MeitY-empanelled providers whose data centres hold valid STQC audit status. It also requires storage and processing of regulated-entity data within the legal boundaries of India, disaster recovery and near-disaster-recovery copies included. The CSCRF's own localisation control, PR.DS.S2, has been in abeyance since SEBI's clarifications of 31 December 2024, and remains so.
Three further rules complete the picture. The IRDAI (Maintenance of Information by the Regulated Entities and Sharing of Information by the Authority) Regulations, 2025, notified on 1 January 2025, require at regulation 9(iii) that records of all policies issued and all claims made in India be held in data centres located and maintained in India only. The Telecommunications (Authorisation for Telecommunication Network) Rules, 2026, G.S.R. 644(E), in force from 20 July 2026, require at rule 25(3) that all systems of a newly authorised telecommunication network be stored in India only, along with the data, logs and information associated with it. No copies may be sent, shared or made available outside India. The English rendering of that rule is MediaNama's, 24 July 2026. And the Department of Science and Technology's geospatial guidelines of 15 February 2021 require data finer than the stated threshold to be stored and processed only on servers located in India.
Logs are the Indian question answered wrongly most often in a lakehouse design. CERT-In's Directions of 28 April 2022, No. 20(3)/2022-CERT-In, are in force and unamended. Direction (iv) requires every service provider and intermediary, every data centre and body corporate, and every Government organisation to enable logs of all their ICT systems and maintain them securely for a rolling period of 180 days, "maintained within the Indian jurisdiction". CERT-In's own FAQs of May 2022 say at Q35 that logs "may be stored outside India also as long as the obligation to produce logs to CERT-In is adhered to by the entities in a reasonable time". The binding text says India. The clarification says anywhere, provided production is
timely. Cite both, decide deliberately, and record the decision. The six-hour incident reporting obligation in direction (ii) is what the log location is ultimately for.
Four accreditation gates in the region bind the supplier rather than the data. A consolidation plan that ignores them stalls at procurement. CST registration by class is the Saudi gate. In Dubai, the Dubai Electronic Security Center's Cloud Service Provider Security Standard is mandatory, in DESC's own words, for all providers wishing to offer cloud services for Dubai government and semi-government entities (DESC, certifications page modified 27 March 2026). It carries annual surveillance audits and recertification every three years. Kuwait requires a CITRA cloud licence. Clause 2.1 of the Cloud Computing Regulatory Framework version 2.4 permits only a CITRA-licensed party with a data centre and infrastructure inside Kuwait to contract to provide cloud services to the public sector, and the licence is not available to foreign operators directly. Oman requires a Telecommunications Regulatory Authority authorisation before contracting, under the Cloud First Policy published 1 July 2026.
Two of those regimes also constrain the data itself, in ways a lakehouse feels immediately. Kuwait's framework prohibits hosting Level 3 and Level 4 data outside Kuwait, along with individuals' personal data held by government bodies, private-sector companies or service providers. Level 3 data must sit in a private or hybrid cloud (clauses 4.2.1.1 and 3.1.4.3 of the Arabic primary text). Clauses 4.3.3 and 4.3.4 go further. They forbid a provider from complying with a foreign jurisdictional demand for subscriber content. Oman's Cloud Computing First Circular, MTCIT Summary 10/2026 of 28 June 2026, requires government entities to classify data before storing or processing it in a cloud environment. Classification is therefore a precondition of migration rather than a parallel workstream.
The United Arab Emirates runs two regimes that pull in opposite directions. The federal Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, has been in force since 2 January 2022 and still had no Executive Regulations as at 8 November 2026. It therefore carries no compliance commencement date, no statutory breach notification deadline and no published penalty schedule. Article 2(2) carves out government data, free zones with their own legislation, health data and banking data. DIFC Law No. 5 of 2020 and the ADGM regulations sit separately, and the ADGM text could not be verified. Against that, Federal Law No. 2 of 2019 on the Use of Information and Communications Technology in Health Fields is the country's hardest localisation rule. Article 13, in force since 14 May 2019, prohibits storing, processing, generating or transferring health data relating to health services provided inside the State outside the State, free zones included. Article 24 attaches a fine of not less than AED 500,000 and not more than AED 700,000. An analytics landscape that ingests health service data in the UAE has a criminal provision to satisfy, not a policy.
The regional ground changes the sequence rather than the destination. Classify the data domains before placing them, because every binding rule in this chapter attaches to a class of data and not to a tenant. Place each domain before provisioning a capacity. The capacity fixes the region, and the region fixes the law. Separate the storage position from the processing position in every document that reaches a regulator, because the vendor does. And treat the out-of-region defaults as design facts to be disclosed rather than discovered: Forms in the United States, Viva and Planner in Europe for the Gulf, and the Copilot Studio data location in the United States for a Qatari or Saudi tenant. A disclosure made in advance is a design constraint. The same fact found by a supervisor is a finding.
A regional position is only useful once it sits on paper in three places, and the same facts serve all three. Keep the wording identical across them, because a difference between them is what an examiner finds.
One line belongs in all three and is usually missing. Name what is not in region. That includes the identity layer, any preview capability in use, and any support access from outside the geography. Microsoft documents that preview, beta and other pre-release services typically store customer data in the United States and may store it globally (Microsoft Learn, page updated 7 October 2026). That is the clause to read before a residency-constrained programme adopts an early-access capability.
Consolidating the analytics landscape onto one platform is the defining data-platform decision of the present cycle, and the evidence in this paper resolves to a short list of conclusions for the chief data officer and the data-and-analytics leadership.
The cost, latency, and trust that leak from a fragmented landscape leak at the seams between services, not inside any one engine. Consolidation is the lever because it removes the seams , the copies, the pipelines, the redundant meters , rather than tuning the engines. Fabric delivers that consolidation through OneLake, the shared workloads, Direct Lake, and the OneLake Catalog and Purview governance layer, and the saving it offers is the integration tax it retires, set against the specialised depth a best-of-breed landscape keeps.
For most enterprises the platform decision is shaped by the existing Azure and Power BI landscape as much as by a feature comparison, and the real question is sequencing and sizing rather than selection. The migration off Synapse, Power BI Premium, and Azure Data Factory is a staged programme underwritten by the saving it realises, and the discipline that determines its success is validation before decommissioning, never the reverse.
A sixth question now belongs beside those five, and in the Gulf and India it outranks several of them. Where may each data domain lawfully rest, and where may it lawfully be
processed. The answer is not a tenant-level answer, and it is not a commitment the vendor makes about processing. Microsoft commits to storage at rest in the tenant geography and publishes a processing commitment only for the European Union, and the platform itself is unavailable in a Gulf country that has an Azure region, a residency commitment and a Foundry presence. Chapter five sets out what follows for the sequence of work.
Five questions belong on the leadership agenda. First, is the integration tax actually quantified, or merely assumed. The tax is duplicated storage and copy pipelines, redundant capacity and trust erosion. Second, is the landscape consolidating onto one copy in OneLake, or are copies still proliferating across services. Third, is the capacity right-sized and governed, given that a mis-sized capacity erases the saving the consolidation was meant to deliver. Fourth, does the migration validate each replacement in parallel before the legacy meter is switched off. Fifth, where best-of-breed genuinely wins, is the hybrid deliberate and connected by zero-copy interoperability, rather than an accident of unfinished consolidation. Large-scale engineering on Databricks and high-concurrency warehousing on Snowflake are two such cases.
The decision is not whether to consolidate. It is what to consolidate, in what order, inside what the law of each jurisdiction allows, and against a baseline somebody has taken. A programme that can answer those four has a case. A programme that cannot is buying a platform and hoping the saving follows.
| Capability | Microsoft Fabric (OneLake) | Databricks | Snowflake |
|---|---|---|---|
| Delivery model | End-to-end SaaS, unified workloads | Lakehouse platform, multi-cloud | Cloud data warehouse, multi-cloud |
| Unified logical lake | OneLake, provisioned per tenant | Unity Catalogue over lakehouse | Single platform; lake plus warehouse |
| Open storage format | Delta Parquet, open by default | Delta Lake and Iceberg | Iceberg and proprietary |
| Greatest strength | Unification; BI and Microsoft-ecosystem integration | Large-scale data engineering and ML on Spark | High-concurrency SQL; data sharing |
| BI integration | Native Power BI with Direct Lake | Connects to external BI | Connects to external BI |
| Real-time | Real-Time Intelligence, Eventhouse, KQL | Structured streaming | Snowpipe streaming |
| Governance | OneLake Catalog and Microsoft Purview, integrated | Unity Catalogue | Horizon governance |
| Capacity / pricing | Pooled F-SKU capacity; one meter | Compute per workload; consumption | Per-warehouse compute; consumption |
| Principal constraint | Specialist engineering/warehousing ceiling | Less unified; heavier to operate | Narrower than a full unified landscape |
| Interoperability | Bi-directional zero-copy with both | Reads OneLake via Unity Catalogue | Interoperability with Fabric |
Fabric is the primary lens of this paper. Interoperability is treated as a design feature, not an exception. A consolidated landscape need not be single-vendor. On scale, Databricks reports >USD 7bn revenue run-rate and >1,000 customers above USD 1M (Databricks, August 2026), while Snowflake reports 14,554 customers, 828 of them above USD 1M trailing-twelve-month product revenue in the quarter ended 31 July 2026 (Snowflake earnings, Q2 FY2027). Sources: Microsoft and vendor disclosures and industry analysis, 2025-2026.
Assess and land
Consolidate
A minimum set of conditions for a defensible consolidation programme, organised by phase.
Govern and optimise
Compiled by Volge from Microsoft Learn region and data-location documentation, pages updated between 8 October and 5 November 2026 and verified 8 November 2026.
Availability changes; reconfirm against current Microsoft documentation before an architectural decision.
The two tables below carry the regional facts chapter five argues from, so that an architecture can be checked against them without rereading the chapter.
| Jurisdiction | Azure region | Microsoft 365 Local Region Geography | Fabric workloads in region | Foundry project region | Copilot Studio in region |
|---|---|---|---|---|---|
| Saudi Arabia | None | No | No | No | No |
| United Arab Emirates | UAE North; UAE Central restricted | Yes | UAE North only | UAE North | UAE North |
| Qatar | Qatar Central, unpaired | Yes | No, Power BI only | Qatar Central | No, data stored in the United States |
| India | Central India, India South Central, South India, West India | Yes | Central India and South India | Central India and South India | Central India and South India |
| Kuwait | None | No | No | No | No |
| Oman | None | No | No | No | No |
| Bahrain | None | No | No | No | No |
| Jurisdiction | Instrument | What it does | Status |
|---|---|---|---|
| Saudi Arabia | CST Cloud Computing Services Provisioning Regulations v4, Decision No. 506/1445, effective 10 October 2023 | Prohibits transfer of Saudi government agency data outside the Kingdom; gates providers by Class A, B or C registration | In force |
| Saudi Arabia | SAMA Cyber Security Framework 3.4.3, No. 381000091275, 24 May 2017 | In-principle in-Kingdom cloud with explicit SAMA approval otherwise, and SAMA approval before cloud is used at all | In force |
| Jurisdiction | Instrument | What it does | Status |
|---|---|---|---|
| Saudi Arabia | SDAIA Data Classification Policy v1, 5 May 2020 | Four levels, Top Secret, Secret, Restricted and Public, with personally identifiable information given as an example of Restricted | In force |
| Saudi Arabia | NCA Cloud Cybersecurity Controls CCC-2:2024 | Deleted the 2020 edition's in-Kingdom provisioning sub-controls, recording transfer of localisation controls to the NDMO | In force; receiving instrument not identified |
| United Arab Emirates | Federal Decree-Law No. 45 of 2021, in force 2 January 2022 | Data protection law whose Executive Regulations have not been issued, leaving no commencement date, breach deadline or penalty schedule | In force, machinery deferred |
| United Arab Emirates | Federal Law No. 2 of 2019 on ICT in Health Fields, Article 13, effective 14 May 2019 | Prohibits storing, processing, generating or transferring health data relating to health services provided in the State outside the State, free zones included | In force |
| United Arab Emirates | DESC Cloud Service Provider Security Standard | Mandatory, in DESC's words, for cloud services to Dubai government and semi-government entities, with annual surveillance audits | In force |
| Qatar | Law No. 13 of 2016 on Personal Data Privacy Protection | Discourages measures that curb trans-border data flow; no adequacy list and no prior approval gate for transfers | In force |
| Kuwait | CITRA Cloud Computing Regulatory Framework v2.4 | Requires a CITRA licence and an in-Kuwait data centre to serve the public sector; prohibits hosting Level 3 and Level 4 data outside Kuwait | In force |
| Oman | MTCIT Cloud Computing First Circular, Summary 10/2026, 28 June 2026, with the Cloud First Policy published 1 July 2026 | Requires classification before cloud storage or processing, and contracting only with TRA-authorised providers | In force |
| Jurisdiction | Instrument | What it does | Status |
|---|---|---|---|
| India | DPDP Rules, 2025, G.S.R. 846(E), 13 November 2025 | Security safeguards, a one-year retention floor on personal data and processing logs, and two-stage breach intimation | Phasing in; principal tranche 13 May 2027 |
| India | CERT-In Directions, No. 20(3)/2022-CERT-In, 28 April 2022 | Six-hour incident reporting, and 180-day ICT logs maintained within the Indian jurisdiction, qualified by FAQ Q35 of May 2022 | In force |
| India | RBI Storage of Payment System Data, RBI/2017-18/153, 6 April 2018 | Entire payment system data stored in a system only in India, with processing abroad requiring return within 24 hours | In force |
| India | SEBI Framework for Adoption of Cloud Services, circular of 6 March 2023 | MeitY-empanelled providers with STQC-audited data centres, and data including disaster-recovery copies within India | In force; CSCRF control PR.DS.S2 in abeyance |
| India | IRDAI (Maintenance of Information by the Regulated Entities and Sharing of Information by the Authority) Regulations, 2025, 1 January 2025 | Records of policies issued and claims made in India held in data centres located and maintained in India only | In force |
| India | Telecommunications (Authorisation for Telecommunication Network) Rules, 2026, G.S.R. 644(E), 20 July 2026 | Systems, data and logs of a newly authorised network stored in India only, with no copies made available outside India | In force |
Compiled by Volge from primary instruments and, where the primary text could not be read, from named law-firm commentary identified at the point of use. This table is indicative and not legal advice; Volge is not a law firm, and qualified counsel should be engaged for compliance decisions.
Prepared by Volge · June 2026, revised November 2026. This document is a point of view intended to inform data and analytics leadership decision-making. It is not financial, licensing, or investment advice. Microsoft Fabric capacities, feature availability, and pricing change and are contract- and region-specific; the capacity and pricing figures here are indicative as at 8 November 2026 and should be reconfirmed against current Microsoft pricing before they are relied upon for budgeting or architectural decisions. Statistics are attributed to their sources and were accurate to the best of available knowledge as at 8 November 2026; the Microsoft Fabric platform and the wider data and analytics field are moving rapidly, and figures should be reconfirmed before they are relied upon.
This paper draws on the following, accessed June 2026 and re-verified 8 November 2026. Figures are attributed in-text to their primary source. Where a statistic appears across multiple secondary outlets, the most authoritative primary attribution is given.
Volge consolidates analytics landscapes onto one governed copy of the data, and the work is engineering rather than advice. The practice sits where this paper locates the money, in the seams between services: the duplicated copies, the pipelines that exist only to move data, the capacity reserved several times over, and the reconciliation that follows two versions of one record. Delivery is by senior data engineers. They work inside the client's own tenant, capacity and repositories, through to the decommissioning of the legacy meters.
The work has a usual shape. A baseline pass quantifies the integration tax on the four counts set out in chapter one, with the raw extracts retained and an owner named against each figure, because a consolidation case that cannot show its baseline does not survive a finance review. The build then follows the dependency order of chapter four. Residency and classification come first, then the OneLake foundation and a right-sized capacity, then the warehouse, then the pipelines and semantic models. Decommissioning comes last, and it is where the saving is realised.
The regional position is the part a Gulf or Indian client usually needs first. Volge is headquartered in the Gulf, and the distinction between a storage commitment and a processing commitment set out in chapter five is established per data domain before a capacity is provisioned, not after. Where the platform is not available in country, as in Qatar, the options are set out with their legal consequences attached rather than described as a limitation. Where no commitment exists at all, as in Saudi Arabia, the choice between a documented cross-border position and infrastructure the client or a local partner operates is taken deliberately and recorded.
Who does the work. A deployment strategist holds the business outcome and the governance cadence with the client's data leadership. A transformation architect holds the target design, the capacity topology and the sequence. Senior data engineers own the workstreams and build inside the client's environment. The same people stay from the baseline to the final decommissioning, which is what makes the control tests
in chapter four drills the team has run rather than procedures it has recommended.
An engagement starts with a scoped assessment, usually four to six weeks. It produces the quantified baseline, a residency and processing position for each data domain, a copy register with an owner against every instance, a capacity sizing taken from observed consumption, and a staged plan whose first stage already has an exit test. Volge is a Microsoft partner and benefits commercially where a client expands its Microsoft footprint, which a reader should weigh when reading the recommendations in this paper. The conversation begins wherever the landscape stands today.
Volge is an engineering firm providing enterprise technology transformation services to clients across the Middle East, India, APAC, Europe, and North America.
Delivery stands on two pillars: Forward Deployed Engineering, with senior specialists embedded in the client’s own team, and Intelligent Command Centre Operations, run from our Global Delivery Centres, which keeps what they build running. Senior engineers stay with an engagement from the first diagnosis through to production.
Our services span Strategy, Data, Platforms, AI and Automation, Cyber Trust, Technology Operations, and Applied Functional Engineering. Engagements begin with a diagnosis. The firm is built on working autonomy: engineers decide, innovate, co-create, and own their work. Motivated engineers build the systems that sustain our clients’ growth.
This edition may be shared with organisations evaluating a Volge engagement. It may not be altered or republished without Volge’s permission, and figures carry their stated basis and date. Volge, Intelligent Command Centre, and Intelligent Command Centre Operations are marks of Volge; other names are the trademarks of their respective owners.