Overview
What is Microsoft Fabric: Microsoft Fabric is a SaaS analytics platform that unifies data movement, data engineering, data science, real-time intelligence, and business intelligence into a single product.
All workloads share a common storage foundation, OneLake, a logical data lake that stores data in open Delta/Parquet formats by default for core analytics tables. Fabric serves data engineers, data scientists, and analysts who need shared analytics data across a common storage layer.
Datagrid connects to MS Fabric using Microsoft-supported APIs and access surfaces, including the Fabric REST API, to pull data from Lakehouses, Data Warehouses, and KQL Databases into Datagrid. Setup happens in the Datagrid UI, while Datagrid reads Fabric through Microsoft-supported APIs under the hood. The exact access method varies by Fabric workload. Once connected, Datagrid's AI agents interpret, cross-reference, and route that data to downstream workflows across CRM, ERP, and other operational systems.
This integration fits operators running mission-critical programs who need governed analytics data to trigger real work across other systems. Fabric's native data agents only generate read queries and do not create, update, or delete data, and they do not process unstructured file formats like PDFs or Word documents. Datagrid closes that gap by turning unstructured data into structured tables and writing enriched outputs to operational systems.
How to integrate MS Fabric with Datagrid
Use this integration to import Fabric data into Datagrid, authorize access, and schedule recurring syncs. The sections below walk through setup, authentication requirements, and sync behavior.
Connect your Fabric data
The MS Fabric integration imports data from Lakehouses, Data Warehouses, and KQL Databases into Datagrid. Once synced, Datagrid's AI agents can process and act on that data autonomously.
Click the + Create button on the top left of the screen.
Select Connect Apps.
Search for the MS Fabric connector from the list.
Log in with your Microsoft Fabric account. MS Fabric may prompt you to authorize Datagrid's access to your data. Grant the required permissions.
Click Next.
Pick the MS Fabric data you want to include in your dataset, such as Lakehouses, Data Warehouses, and KQL Databases.
Click Start First Import to begin syncing your MS Fabric dataset.
A typical access path uses the Fabric REST API. The exact endpoint varies by workload.
GET /v1/workspaces/{workspaceId}/items
Datagrid uses Microsoft-supported APIs and access surfaces to read the objects you select during setup.
Configure authentication
The integration authenticates through Microsoft Entra ID, formerly Azure Active Directory. Before connecting, you need:
An active Microsoft Fabric account with permissions to access target workspaces
A Microsoft Entra ID app registration with permissions to access the Fabric APIs
The Fabric REST API enabled by your tenant administrator under Developer Settings → Tenant Settings
Review sync details
These are the core sync parameters for the MS Fabric integration.
Direction — One-way (MS Fabric → Datagrid)
Frequency — Daily, weekly, or monthly
Supported objects — Lakehouses, Data Warehouses, KQL Databases
Storage format — Varies by Fabric workload; OneLake-native data commonly uses Delta/Parquet formats
After setup, you can keep Fabric data current in Datagrid with a recurring schedule.
Go to the left side panel and click on the MS Fabric dataset you created.
Click ... on the top right of the dataset.
Click the Schedule button, beside the Import Configuration button.
Set the desired frequency: daily, weekly, or monthly.
Specify the time of day for the data pull.
Specify downtime windows if needed, when the sync should not run.
Click Update to save the new configuration.
Why use MS Fabric with Datagrid
This integration fits operators running mission-critical programs who need governed analytics data to trigger real work across other systems.
Process unstructured data for Fabric analytics: Fabric's data agents do not process PDFs, Word docs, or plain text files. Datagrid's AI agents extract and structure that data before it lands in OneLake.
Close the analytics-to-action gap: Datagrid writes enriched outputs such as customer scores, risk flags, and demand forecasts back to CRM, ERP, and operational systems.
Automate cross-system workflows from Fabric signals: Fabric's Data Activator triggers are limited to Teams alerts, emails, and Power Automate flows. Datagrid executes multi-step actions across connected systems when those signals fire.
Unify data from multiple Fabric workloads: Pull Lakehouse tables, Warehouse data, and KQL Database outputs into a single Datagrid dataset. Datagrid's AI agents cross-reference across all of them without manual exports.
Keep syncs current without manual work: Configure daily, weekly, or monthly imports with downtime windows. Datagrid keeps datasets current with the latest Fabric data automatically.
Run AI agents on governed enterprise data: Fabric provides centralized governance and security through Microsoft Purview. Datagrid's AI agents operate on that governed data to generate validated, auditable outputs.
What you can build with MS Fabric Datagrid integration
Teams can use this integration to move from analytics review to execution across the systems where work actually happens.
These examples show how Datagrid can execute workflows with Fabric data across connected systems.
Automated document-to-Lakehouse pipeline: Datagrid AI agents extract structured entities from contracts, invoices, or spec sheets and load the results as structured tables into OneLake. Downstream Fabric workloads such as Power BI reports and SQL queries run against that structured data without manual data entry.
Real-time SLA breach response: Fabric's Real-Time Intelligence detects an SLA threshold violation in streaming operational data. Datagrid receives the signal and triggers a multi-step remediation, updates the project management system, notifies the account team, and logs the incident back to OneLake for audit.
Cross-source analytics enrichment for project teams: Combine Fabric Warehouse data, including financial actuals and resource utilization, with data from a CRM platform or marketing system in Datagrid. Datagrid's AI agents cross-check revenue forecasts against pipeline data, flag discrepancies, and route findings to the right team without switching between systems.
Predictive model output distribution: A data science team builds a churn prediction model in Fabric's ML workload. Datagrid reads the scored output from a Lakehouse Gold table and pushes high-risk customer records to the CRM, triggers retention workflows in the marketing automation stack, and writes execution logs back to OneLake for model performance tracking.
These workflows keep analytics connected to execution instead of stopping at dashboards or alerts.
Resources and documentation
Set up the MS Fabric connector on Datagrid - Datagrid setup steps for connecting and importing MS Fabric data
Microsoft Fabric REST API reference - complete API surface covering all Fabric workloads
Microsoft Fabric product overview - architecture, workloads, and OneLake fundamentals
Enable service principals for Fabric APIs - tenant admin setup required before connecting external applications
OneLake API access documentation - ADLS Gen2-compatible endpoints and SDK usage
Fabric Data Factory connector overview - full matrix of 200+ native connectors in Fabric
Frequently asked questions
What authentication method does the MS Fabric connector use?
The integration authenticates through Microsoft Entra ID, formerly Azure Active Directory. You need a Microsoft Entra ID app registration with the correct permissions, and your Fabric tenant administrator must enable service principal API access in the Fabric Admin Portal under Developer Settings → Tenant Settings. Traditional API key or username/password authentication is not available for Fabric APIs.
What types of data can I import from MS Fabric into Datagrid?
You can import data from Lakehouses, Data Warehouses, and KQL Databases. For OneLake-native analytics data, Fabric commonly uses open Delta/Parquet formats, though storage and access patterns can vary by workload.
How often can I schedule data pulls from MS Fabric?
Datagrid executes daily, weekly, or monthly sync schedules for MS Fabric data. You can also specify the exact time of day for each pull and define downtime windows when syncs should not run. Configure these settings through the Schedule button in your MS Fabric dataset pipeline.
Does my Fabric tenant admin need to configure anything before I connect?
Yes. A Fabric tenant administrator must enable the setting "Service principals can use Fabric APIs" in the Fabric Admin Portal. Without that setting, API calls from external applications, including Datagrid, will fail with authorization errors.
Can Datagrid write data back to MS Fabric?
The Datagrid MS Fabric integration imports data from Fabric into Datagrid as a one-way sync. Datagrid's AI agents can still write enriched outputs to other connected systems in your stack.
Similar integrations
If your workflows span storage, databases, and Microsoft collaboration tools, these related integrations are often relevant alongside MS Fabric.
Azure Data Lake Storage - Cloud storage layer that OneLake is built on; commonly used alongside Fabric for raw data staging.
Azure SQL Database - Microsoft's managed relational database, often paired with Fabric for transactional workloads that feed analytics pipelines.
Azure Blob Storage - Object storage for unstructured files that Fabric can virtualize through OneLake Shortcuts.
MS SQL Server - On-premises relational database frequently used as a source for Fabric's Data Factory ingestion pipelines.
Microsoft Excel - Spreadsheet data that teams commonly push into Fabric Lakehouses for unified analysis.
SharePoint - Document and list storage within the Microsoft ecosystem, often a source for project files that feed Fabric analytics.