# Connecting Microsoft Fabric

> Microsoft Fabric is planned after Databricks, tested only on simulated services. What the connection needs and what its profile covers.

Status: planned after Databricks, with no date. The Fabric connector is built and tested only against simulated Fabric services; it has not run on a real account, so there is no flow to follow yet. This page lists what the connection needs and what the draft Fabric profile covers. The [Microsoft Fabric platform page](https://emolysis.com/platforms/microsoft-fabric) has the summary.

## What you need

- A Fabric workspace on a capacity you can use, with rights to create items in it.
- A Microsoft Entra ID account to sign in with. Credentials are kept in your machine's credential store, as on every platform.
- For a first try, a development workspace, so that nothing you test touches production.

## What the profile is drafted to cover

- **Dialect:** Spark SQL and PySpark in lakehouses, and T-SQL in warehouses.
- **Table format:** Delta tables in [OneLake](https://emolysis.com/glossary/onelake).
- **Merge idiom:** `MERGE` on lakehouse Delta tables.
- **Incremental tools:** notebooks on a pipeline schedule, and Dataflow Gen2.
- **Deployment unit:** a PySpark notebook, created or updated through the Fabric REST API, with your lakehouse as its default.
- **Compute:** Spark job definitions and sessions, and the SQL analytics endpoint.
- **Known traps:** deploying workspace items through the API needs care with item definitions and the order items are created in.
- **Sampling:** reading lakehouse tables through Spark into DuckDB.

The same profile fields apply to every platform; see [Platform profiles](https://emolysis.com/docs/platform-profiles).

## What stays the same

The workflow is the same on every platform. You describe what you need, the agent picks a [shape](https://emolysis.com/docs/shapes), fills the template for your platform and proves it with [golden tests on DuckDB](https://emolysis.com/docs/golden-tests), and the agent deploys only after a green run. See [Deploying](https://emolysis.com/docs/deploying).

## Not decided yet

- The order in which Microsoft Fabric and Snowflake follow Databricks.
- How lakehouse and warehouse targets are offered side by side.
- Dates. None are given.

## Meanwhile

[Connecting Databricks](https://emolysis.com/docs/connect-databricks) shows how the first platform connects, and the [news page](https://emolysis.com/news) follows progress. If your team runs on Fabric and would like to take part in early access, see [early access](https://emolysis.com/early-access).

---

Page: https://emolysis.com/docs/connect-fabric. Emolysis is a product of Bandpey GmbH, Munich, Germany. It is in private development, and nothing is released yet.