Introduction to Git integration
Microsoft Fabric is in preview.
This articles in this section are about version control using Git integration. To manage deployment of your app, see the deployment pipelines documentation.
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
- Leverage 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. Currently, in Preview, only a few items are supported, but the list of supported items is growing.
Read more about the Git integration process.
Read about the best way to manage your Git branches.
Before you enable Git integration, make sure you understand the following possible privacy concerns:
The following items are currently supported:
- Paginated reports
- Datasets (except push datasets, live connections, and model v1)
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 pane but you can't commit or update them.
Considerations and limitations
- Currently, only Git in Azure Repos is supported.
- If the workspace and Git repo are in two different geographical regions, cross-geo exports must be enabled by the tenant admin.
- Azure DevOps on-prem is not supported.