Still documented as 'Native execution engine for Fabric Data Engineering'. The page still refers to 'the preview phase' in the enablement section, though it covers Runtime 1.3 and 2.0.
Read
10 Nov 2026
What it does well
Per Microsoft's documentation, no code modifications are required, and the engine is enabled with an Acceleration tab toggle or spark.native.enabled.
The engine works with Parquet, Delta and CSV, including data reached through OneLake shortcuts.
Where it is limited
The engine runs only inside Microsoft Fabric on Azure and does not run on AWS EMR or EKS.
Microsoft's page gives no number, workload or dataset for the speedup, and a benchmark method or scripts: none found on 2026-11-10.
Published speed results
Fact
Source type
Source, read
The page says the engine significantly raises query performance while minimizing operational costs, but gives no number, workload or dataset. 'Actual results vary by workload characteristics and configuration.'
Fabric is billed by capacity units (F2 to F4096 SKUs), pay-as-you-go or reservation. An opt-in Autoscale Billing for Spark runs Spark jobs on dedicated serverless resources at standard regional pay-as-you-go CU-hour rates, with a base Fabric capacity still required. SKU prices on the page load dynamically and were not readable.
Docs say no code modifications are required and no vendor lock-in. Unsupported operators fall back to JVM Spark. Listed limitations include decimal-to-float casting, timezone, round(), map() duplicate-key and collect_list ordering differences on Runtime 1.3, said to be resolved in Runtime 2.0.
Enable via the Acceleration tab toggle in an environment, or set spark.native.enabled to true at the start of a notebook or Spark job definition. Per-query disable is by setting the flag to false and re-enabling in later cells. Fabric Spark Advisor alerts show fallback.
Supports Runtime 1.3 (Spark 3.5, Delta Lake 3.2) and Runtime 2.0 (Spark 4.1, Delta Lake 4.1). Works with Parquet, Delta and CSV, including data reached via OneLake shortcuts. Not an AWS service.
The engine is based on two open source components: Velox, a C++ library introduced by Meta, and Apache Gluten (incubating), a middle layer introduced by Intel that offloads JVM SQL engine execution to native engines.
Enable it with the Acceleration tab toggle in an environment, or set spark.native.enabled to true in a notebook or Spark job definition. It needs Runtime 1.3 or 2.0.
Fabric is billed by capacity units (F2 to F4096 SKUs), pay-as-you-go or reservation. Autoscale Billing for Spark still requires a base Fabric capacity. SKU prices were not readable on the page.
Published benchmark with workload, data size and result for the Fabric native execution engine (searched: learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engin, azure.microsoft.com/en-us/pricing/details/microsoft-fabric)
Public benchmark repo or scripts (searched: learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engin)
Microsoft Fabric native execution engine side by side with each other option