---
title: Microsoft Fabric Warehouse
description: >-
  Connect Microsoft Fabric Warehouse to Datadog Data Observability to monitor
  data quality, track usage, and detect issues.
breadcrumbs: >-
  Docs > Data Observability Overview > Quality Monitoring > Warehouse
  Integrations > Microsoft Fabric Warehouse
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Microsoft Fabric Warehouse

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}

{% callout %}
# Important note for users on the following Datadog sites: app.datadoghq.com, us3.datadoghq.com, us5.datadoghq.com, app.datadoghq.eu, ap1.datadoghq.com, ap2.datadoghq.com, uk1.datadoghq.com

{% callout %}
##### Preview

Data Observability for Microsoft Fabric Warehouse is in Preview. Contact your Datadog representative to enable it for your organization.
{% /callout %}

{% /callout %}

## Overview{% #overview %}

The Microsoft Fabric Warehouse integration connects Datadog to your Fabric warehouses to sync metadata, query history, and table-level metrics. Use it to monitor data quality, detect anomalies, and trace lineage across your warehouses.

Datadog authenticates to Fabric with the app registration (service principal) configured in your Datadog Azure integration. Datadog uses the Fabric REST API to discover workspaces and warehouses. It then connects to each warehouse's SQL endpoint to read metadata, run data quality queries, and read query history from [Query Insights](https://learn.microsoft.com/fabric/data-warehouse/query-insights).

## Prerequisites{% #prerequisites %}

Before you begin, make sure you have:

- The [Datadog Azure integration](https://docs.datadoghq.com/integrations/azure.md) configured with an app registration. Log forwarding and metric collection are not required for Data Observability.
- A Fabric administrator who can view and change tenant settings.
- The Admin or Member role on each Fabric workspace you want to monitor.
- Warehouses that run on an active capacity and accept connections from the public internet.

## Grant Datadog access in Fabric{% #grant-datadog-access-in-fabric %}

### Step 1: Check the tenant setting{% #step-1-check-the-tenant-setting %}

1. In Fabric, open the [tenant settings](https://learn.microsoft.com/fabric/admin/about-tenant-settings#how-to-get-to-the-tenant-settings).
1. Under Developer settings, expand Service principals can call Fabric public APIs.
1. Make sure the setting is enabled. It is enabled by default for new Fabric tenants.
1. If the setting applies to Specific security groups, add the Datadog Azure integration's app registration to one of those groups.

### Step 2: Add the app registration to your workspaces{% #step-2-add-the-app-registration-to-your-workspaces %}

For each workspace you want to monitor:

1. In Fabric, open the workspace and click Manage access.
1. Click Add people or groups.
1. Enter the name of the app registration that the Datadog Azure integration uses.
1. Select Contributor or Viewer, then click Add.

Choose a role based on the features you need:

{% tab title="Contributor (recommended)" %}
The Contributor role supports all Data Observability features for Fabric Warehouse, including query history and lineage. Microsoft requires the Contributor role or higher to read [Query Insights](https://learn.microsoft.com/fabric/data-warehouse/query-insights).

**Note**: The Contributor role grants `CONTROL` on every warehouse in the workspace, which includes write access. Datadog runs only read queries.
{% /tab %}

{% tab title="Viewer" %}
The Viewer role grants read-only access to every warehouse in the workspace. It supports metadata sync and data quality monitors, but not query history or lineage. Leave Collect query history turned off when you configure the integration.

SQL-level restrictions such as `DENY` statements, row-level security, column-level security, and dynamic data masking apply to the app registration. Tables and columns the role can't read don't appear in Datadog, and monitors on them fail.
{% /tab %}

The workspace role applies to every warehouse in the workspace, including warehouses created later. You don't need to share individual warehouses or run `GRANT` statements.

You can also assign the role to a Microsoft Entra security group that contains the app registration. Role assignments through a group can take up to an hour to take effect.

## Configure the integration in Datadog{% #configure-the-integration-in-datadog %}

1. In Datadog, go to Datadog Data Observability > [Settings](https://app.datadoghq.com/data-obs/settings/integrations).

1. In the Microsoft Fabric Warehouse section, click Configure.

   {% image
      source="https://docs.dd-static.net/images/data_observability/fabric/data_obs_fabric_on_integrations_page.bedbab3deea00585efa1f39624b163ab.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/data_observability/fabric/data_obs_fabric_on_integrations_page.bedbab3deea00585efa1f39624b163ab.png?auto=format&fit=max&w=850&dpr=2 2x"
      alt="The Microsoft Fabric Warehouse row on the Data Observability Settings page, with a Configure button." /%}

If the section shows Install Azure integration, configure the [Datadog Azure integration](https://docs.datadoghq.com/integrations/azure.md) with an app registration first.

1. Select the app registration that you added to your workspaces, and click Configure.

   {% image
      source="https://docs.dd-static.net/images/data_observability/fabric/data_obs_fabric_select_app_registration.e8e37f7019cda0d0e3277df64145ca87.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/data_observability/fabric/data_obs_fabric_select_app_registration.e8e37f7019cda0d0e3277df64145ca87.png?auto=format&fit=max&w=850&dpr=2 2x"
      alt="The list of Azure app registrations for Microsoft Fabric Warehouse, with a Configure button for each." /%}

1. Turn on Monitor Fabric Warehouses.

1. Optionally, add Warehouse filters. Leave the field empty to monitor every warehouse the app registration can access, or enter one filter per warehouse:

   - `<WAREHOUSE_NAME>`: Matches a warehouse with this name in any workspace.
   - `<WORKSPACE_ID>/<WAREHOUSE_NAME>`: Matches a warehouse in one workspace. The workspace ID appears in the workspace URL after `/groups/`.

1. Optionally, turn on Collect query history to collect query history from Query Insights for lineage and query analysis. This option requires the Contributor role or higher.

   {% image
      source="https://docs.dd-static.net/images/data_observability/fabric/data_obs_fabric_configure.4b90abc3f9d10c12cdf6340625fbe08a.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/data_observability/fabric/data_obs_fabric_configure.4b90abc3f9d10c12cdf6340625fbe08a.png?auto=format&fit=max&w=850&dpr=2 2x"
      alt="The Monitor Fabric Warehouses and Collect query history toggles, with an optional warehouse filters field." /%}

1. Click Save.

## Next steps{% #next-steps %}

After you configure the integration, Datadog syncs your warehouse metadata every hour. Allow up to an hour for the first sync. Queries can take up to 15 minutes to appear in Query Insights before Datadog collects them.

After the initial sync completes, create a [Data Observability monitor](https://docs.datadoghq.com/monitors/types/data_observability.md) to start alerting on row count, column-level metrics, and custom SQL metrics. Fabric doesn't expose a table-level last-modified time, so to monitor freshness, create a freshness monitor on a timestamp column.

## Troubleshooting{% #troubleshooting %}

Changes to workspace roles can take up to an hour to apply in Fabric. If you recently added, changed, or removed a role, wait before troubleshooting.

If warehouses or tables are missing, verify the following:

- The app registration has a role on the workspace that contains the warehouse.
- The warehouse matches one of the configured warehouse filters.
- The warehouse's capacity is running.
- For the Viewer role, no SQL-level restriction hides the table from the app registration.

If Datadog reports invalid credentials, verify the client ID, tenant ID, and client secret in the Datadog Azure integration.

If Datadog reports a failed SQL login, verify that the app registration has a role on the workspace. Fabric rejects SQL logins from identities without a workspace role.

If query history fails with a permissions error, assign the app registration the Contributor role or higher on the workspace.

## Limitations{% #limitations %}

- Only Fabric Warehouse items are supported. Lakehouse SQL analytics endpoints, SQL databases in Fabric, and other Fabric item types are not supported.
- Workspaces that restrict inbound public access, such as workspaces that use private links, are not supported.

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Data Observability Overview](https://docs.datadoghq.com/data_observability.md)
- [Data Observability Monitors](https://docs.datadoghq.com/monitors/types/data_observability.md)
- [Azure integration](https://docs.datadoghq.com/integrations/azure.md)
