Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article explains to developers how to integrate Git version control with the Microsoft Fabric Application lifecycle management (ALM) tool.
Note
Some of the items for Git integration are in preview. For more information, see the list of supported items.
Git integration in Microsoft Fabric enables developers to integrate their development processes, tools, and best practices straight into the Fabric platform. It allows developers who are developing in Fabric to:
- Backup and version their work
- Revert to previous stages as needed
- Collaborate with others or work alone using Git branches
- Apply the capabilities of familiar source control tools to manage Fabric items
The integration with source control is on a workspace level. Developers can version items they develop within a workspace in a single process, with full visibility to all their items. The workspace structure, including subfolders, is preserved in the Git repository.
See the list of supported items.
Read up on basic Git and version control concepts.
Read more about the Git integration process.
Read about the best way to manage your Git branches.
Network security for Git integration
Workspace-level security in Microsoft Fabric provides granular control over data access and network connectivity by allowing administrators to configure both inbound and outbound protections for individual workspaces. These controls ensure that sensitive data remains within trusted network boundaries, and they integrate with CI/CD tools like Git integration. For more information, see Network security for continuous integration/continuous deployment
Privacy information
Before you enable Git integration, make sure you review the following privacy statements:
- Microsoft privacy statement
- Azure DevOps Services Data protection overview
- GitHub Data protection agreement
Supported Git providers
The following Git providers are supported:
- Azure DevOps (cloud-based only)
- GitHub (cloud-based only)
- GitHub Enterprise (cloud-based only)
Supported items
The following items currently support Git integration:
Data Engineering items:
Data Science items:
- Machine learning experiments (preview)
- Machine learning models (preview)
- Data Agents (preview)
Data Factory items:
Real-time Intelligence items:
- Activator (preview)
- Eventhouse
- EventStream
- KQL database
- KQL Queryset
- Real-time Dashboard
- Event Schema Set (preview)
- Maps (preview)
- Anomaly detection (preview)
Data Warehouse items:
- Warehouse (preview)
- Mirrored Azure Databricks Catalog
Power BI items:
- Metrics Set (preview)
- Org app (preview)
- Paginated report (preview)
- Report (except reports connected to semantic models hosted in Azure Analysis Services, SQL Server Analysis Services, or reports exported by Power BI Desktop that depend on semantic models hosted in MyWorkspace) (preview)
- Semantic model (except push datasets, live connections to Analysis Services, model v1) (preview)
Database items:
- SQL database
- Cosmos database (preview)
Graph:
Industry solutions:
- Healthcare (preview)
- HealthCare Cohort (preview)
If the workspace or Git directory has unsupported items, it can still be connected, but the unsupported items are ignored. They aren't saved or synced, but they're not deleted either. They appear in the source control panel but you can't commit or update them.