Fusion in Fabric Installation

Deployment path

This guide is for Fusion in Fabric deployments (new installs and migrations). Do not use this page for Fusion with ADX installs. Choose one installation path per customer environment.

Installation Flow

Terraform 1.14.3 is recommended for Fusion v3.8.

Step 1: Install and configure the Fabric workload

1. In the customer Fabric capacity, install the Fusion in Fabric workload.
2. Register the customer in the Fabric workload administration site.
3. Connect the workload to an Eventhouse (existing or newly created).
4. Record fabricDatabase, Fabric query URI, and Fabric ingest URI.

Step 2: Prepare Terraform deployment files and variables

1. Ensure the Terraform user has owner rights on the target resource group.
2. Create a deployment folder under deployments/dev or deployments/prod.
3. Copy providers.tf, state.tf, and versions.tf from example_consumer/.
4. Populate state.tf backend values (resource group, storage account, container, SAS token, key, tenant, subscription).
5. Copy example_consumer/main.tf into your deployment folder and update inputs.

Use these Fabric-specific settings:

Variable	Value for Fusion in Fabric	Notes
kqlMode	"fabric" for new installs	Use "migration" only for existing ADX deployments moving to Fabric.
fabricQueryUri	"https://<identifier>.<region>.kusto.fabric.microsoft.com"	Required for kqlMode="fabric" and kqlMode="migration".
fabricIngestUri	"https://ingest-<identifier>.<region>.kusto.fabric.microsoft.com"	Required for kqlMode="fabric" and kqlMode="migration".
fabricDatabase	<database_name>	In Fabric KQL, run .show database details and use name.
adxCount	0 (if present)	Fabric deployments should not provision ADX resources.

kqlMode         = "fabric"
fabricQueryUri  = "https://<identifier>.<region>.kusto.fabric.microsoft.com"
fabricIngestUri = "https://ingest-<identifier>.<region>.kusto.fabric.microsoft.com"
fabricDatabase  = "<database_name>"

Existing deployments only

kqlMode = "migration" is only supported for existing Fusion deployments (first_run=false). Do not use migration mode during initial deployment (first_run=true).

If you are using legacy (non-module) scripts, run fusion_pre_install.ps1 before deployment.

Step 3: Deploy with Terraform

Choose your path

For a new Fusion in Fabric install, use kqlMode="fabric". For an existing ADX deployment migrating to Fabric, use kqlMode="migration".

For a first-time install:

1. terraform init
2. terraform plan -var first_run=true
3. terraform apply -var first_run=true
4. terraform apply -var first_run=false

For an existing ADX deployment migrating to Fabric:

1. Set kqlMode = "migration" and set fabricIngestUri, fabricQueryUri, and fabricDatabase.
2. Run:

terraform apply

This adds migration resources (including Azure Data Factory and event frame relay) and reconfigures existing resources.

Step 4: Connect Fabric workload to Fusion

1. In the Fabric workload, use Connect to Fusion.
2. Select the Azure resources for the Fusion 3.8 instance and confirm.
3. Trigger a model read.

Step 5: Validate

1. Verify Fusion resources are deployed successfully in Azure.
2. Verify fabricQueryUri, fabricIngestUri, and fabricDatabase are applied.
3. Validate data ingestion to Fabric Eventhouse.
4. For migration scenarios, validate data flows as expected during cutover.

For migration backfill and ADX decommission steps, continue with: fusion-3-8-to-fabric-migration.md