> For the complete documentation index, see [llms.txt](https://docs.zingg.ai/zingg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingg.ai/zingg/connect-your-data/connect-cloud-warehouses/connect-microsoft-fabric.md).

# Connect Microsoft Fabric

Connect Zingg to Microsoft Fabric OneLake using abfss\:// path format. Available in all editions.

{% hint style="success" icon="right-long" %}
On Microsoft Fabric, data lives in OneLake. Use the `abfss://` path format to connect Zingg to your Lakehouse. Available in all editions.
{% endhint %}

### Prerequisites

On Microsoft Fabric, data lives in OneLake. Use the `abfss://` path format to connect Zingg to your Lakehouse. The path follows the pattern `abfss://<workspace-id>@onelake.dfs.fabric.microsoft.com/<lakehouse-id>/Files/<filename>` for files, and `.../Tables/<tablename>` for Lakehouse tables. All formats — CSV, Parquet, Avro, JSON, Delta — are available in both Community and Enterprise. For the full Zingg installation, workspace setup, and any additional dependency configuration required on Fabric Spark pools, follow the [Microsoft Fabric Platform Guide](/zingg/platform-guides/platform-guide-for-microsoft-fabric.md).

### Python API

```python
from zingg.client import *
from zingg.pipes import *

schema = (
    "rec_id string, fname string, "
    "lname string, stNo string, add1 string, "
    "add2 string, city string, "
    "areacode string, state string, "
    "dob string, ssn string"
)

workspace_id = "<workspace-id>"
lakehouse_id = "<lakehouse-id>"
base_path = (
    f"abfss://{workspace_id}@onelake.dfs.fabric.microsoft.com/"
    f"{lakehouse_id}/Files"
)

inputPipe = CsvPipe("inputpipe", f"{base_path}/yourdata.csv", schema)
args.setData(inputPipe)

outputPipe = CsvPipe("resultOutput", f"{base_path}/Output")
args.setOutput(outputPipe)
```

### JSON Config

```json
{
  "data" : [ {
    "name" : "inputpipe",
    "format" : "csv",
    "props" : {
      "location" : "abfss://<workspace-id>@onelake.dfs.fabric.microsoft.com/<lakehouse-id>/Files/yourdata.csv"
    },
    "schema" : "rec_id string, fname string, lname string, stNo string, add1 string, add2 string, city string, areacode string, state string, dob string, ssn string"
  } ],
  "output" : [ {
    "name" : "resultOutput",
    "format" : "csv",
    "props" : {
      "location" : "abfss://<workspace-id>@onelake.dfs.fabric.microsoft.com/<lakehouse-id>/Files/Output"
    }
  } ]
}
```

### Supported file formats

#### Parquet

```json
{
  "data" : [ {
    "name" : "parquetInput",
    "format" : "parquet",
    "props" : {
      "path" : "abfss://<workspace-id>@onelake.dfs.fabric.microsoft.com/<lakehouse-id>/Files/input.parquet"
    }
  } ]
}
```

#### **Delta (Lakehouse Tables)**

```json
{
  "data" : [ {
    "name" : "deltaInput",
    "format" : "delta",
    "props" : {
      "location" : "abfss://<workspace-id>@onelake.dfs.fabric.microsoft.com/<lakehouse-id>/Tables/yourtable"
    }
  } ]
}
```

#### **Avro**

```json
{
  "data" : [ {
    "name" : "avroInput",
    "format" : "avro",
    "props" : {
      "path" : "abfss://<workspace-id>@onelake.dfs.fabric.microsoft.com/<lakehouse-id>/Files/input.avro"
    }
  } ]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zingg.ai/zingg/connect-your-data/connect-cloud-warehouses/connect-microsoft-fabric.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.