> ## Documentation Index
> Fetch the complete documentation index at: https://docs.langdock.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Fabric

> Connect Microsoft Fabric to Langdock to ask questions about data exposed through APIs for GraphQL and run mutations.

## Overview

Use the Microsoft Fabric integration to ask questions about business data in Langdock. Langdock can find accessible APIs for GraphQL, inspect the required schema, and run focused queries. Write requests use a separate mutation action with confirmation before execution.

## Use Microsoft Fabric

1. Open Microsoft Fabric in Langdock, select **Add connection**, and sign in with your Microsoft account.
2. Tag **Microsoft Fabric** in a chat.
3. Ask a question about your data. Name the workspace or GraphQL API only when Langdock asks you to distinguish between multiple matches.

<Info>
  If Fabric is not configured yet, share [Configure Microsoft Fabric for Langdock](./microsoft-fabric/setup) with your Fabric or Langdock workspace admin.
</Info>

## Supported data

A GraphQL API can expose and combine selected objects from these supported sources:

* Microsoft Fabric Data Warehouse
* Microsoft Fabric SQL database
* Microsoft Fabric Lakehouse through its SQL analytics endpoint
* Microsoft Fabric mirrored databases through their SQL analytics endpoints, including:
  * Azure SQL Database
  * Azure SQL Managed Instance
  * Azure Cosmos DB
  * Microsoft Fabric SQL database
  * Azure Databricks
  * Snowflake
  * Open mirrored databases
* Azure SQL Database connected directly

Microsoft Fabric Data Warehouses and Fabric SQL databases support queries and can expose mutations. Their stored procedures, as well as those from directly connected Azure SQL databases, can be exposed as controlled write operations. SQL analytics endpoints provide query access. See [Microsoft's supported data sources and features](https://learn.microsoft.com/en-us/fabric/data-engineering/api-graphql-overview) for the current source matrix and [current GraphQL limitations](https://learn.microsoft.com/en-us/fabric/data-engineering/api-graphql-limits).

Langdock uses an **API for GraphQL** item as the governed access layer across these sources. You choose in Fabric which objects and operations to expose, while specialized workloads such as Eventhouses, notebooks, pipelines, and semantic models continue to use their dedicated interfaces and integrations.

## Large results and exports

Ask for focused fields, filters, aggregation, and smaller pages whenever possible. Langdock returns larger successful query results as a JSON file automatically. You can also ask for a JSON file explicitly when you need a complete export for a workflow or code environment.

If a result is too large to return, narrow the query or retrieve it in multiple pages. For mutations, verify the changed record in Fabric before deciding whether to repeat an operation whose response could not be returned.

## Choose the guide you need

<CardGroup cols={3}>
  <Card title="Admin configuration" icon="plug" href="./microsoft-fabric/setup">
    Prepare and secure a Fabric API for GraphQL, then configure the integration for your workspace.
  </Card>

  <Card title="Access and mutations" icon="shield" href="./microsoft-fabric/permissions-and-mutations">
    Choose SSO or Saved credentials and control read and write access.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="./microsoft-fabric/troubleshooting">
    Resolve common discovery, schema, permission, query, and capacity issues.
  </Card>
</CardGroup>