Skip to main content
Use this guide if you are a Fabric workspace admin, owner of the API for GraphQL, or Langdock workspace admin. After you complete the configuration, individual users only need to add their connection. For access and write operation decisions, see Access and mutations.

​
Before you start

You need:
  • A Fabric workspace backed by a Fabric, Trial, or Premium capacity.

​
Set up the API for GraphQL in Fabric

As a Fabric workspace admin or API owner, prepare the API for Langdock:
1

Create an API for GraphQL

In the Fabric workspace, create an API for GraphQL item.
API for GraphQL in the Microsoft Fabric New item panel
2

Choose how the API connects to its data sources

Choose Single sign-on (SSO) (recommended) when users should access the source with their own identity. Choose Saved credentials when every API caller should use one centrally managed source identity. Each GraphQL API uses a single mode across its sources.If you are unsure which option fits, compare how each authentication model handles identity, permissions, and access.
Microsoft Fabric connectivity dialog with single sign-on selected
3

Choose the data to expose

Add the relevant data sources and select the tables, views, stored procedures, and columns to include. Define relationships between objects in the same source when users should retrieve related records in one query. Relationships are available between objects from the same source.Keep the schema focused on the intended use case by including only the objects and operations consumers need.
Selected tables, view, and stored procedure in the Microsoft Fabric Choose data dialog
4

Enable introspection

Open API Settings, select Introspection, and enable it. Introspection is disabled by default. Enabling it allows Langdock to discover the available types, fields, arguments, queries, and mutations, and makes this schema metadata visible to all users with access to the API endpoint.
Introspection enabled in the settings for a Microsoft Fabric API for GraphQL
5

Grant access

Give every user Run Queries and Mutations on the GraphQL API item. The grant dialog uses that label, while Direct access and its ellipsis menu summarize and manage the same permission as Execute.
Selected Run Queries and Mutations permission in the Microsoft Fabric API for GraphQL grant dialog
With SSO, also grant each user the required permissions on every underlying source. With Saved credentials, grant the saved Fabric identity the required source permissions instead. See Control who can read or change data.
6

Refresh and verify the schema

After adding, removing, or changing source objects, select Update schema and verify the result in Schema explorer so the API reflects the latest source schema.Run a focused query in Fabric and confirm that the expected source objects and results are available before connecting users.
Microsoft Fabric GraphQL editor with a regional sales query and successful results

​
Enable the integration in Langdock

As a Langdock workspace admin, enable Microsoft Fabric. Langdock can then find APIs, inspect their schemas, query data, and use mutations without requiring users to provide IDs or endpoint URLs. The mutation action asks for confirmation before execution.
Microsoft Fabric read and mutation actions enabled separately in Langdock workspace settings
If newly enabled actions add Microsoft permissions, ask existing users to reconnect once.

​
Connect users

Ask each user to open Microsoft Fabric in Langdock, select Add connection, and sign in with the Microsoft account you granted access to. Direct users to the three step user guide. If an API is not discoverable by name, see Troubleshooting.

​
Validate the setup

Use a representative business user to confirm the access you intend to roll out:
  1. Run a focused query in Fabric’s GraphQL editor as that user.
  2. In Langdock, ask a question that requires the same data and compare the result with the source.
  3. If you expose mutations, use a disposable record, confirm the operation in Langdock, and verify the change in Fabric.
If a check fails, use Troubleshooting to identify whether discovery, schema, or permissions need attention.