Edit

Share via

Introduction to Git integration (preview)

  • Article

This article explains to developers how to integrate Git version control with the Fabric Application lifecycle management (ALM) tool.

Important

This feature is in preview.

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. Currently, in Preview, only a few items are supported, but the list of supported items is growing.

Privacy information

Before you enable Git integration, make sure you review the following privacy statements:

Supported Git providers

The following Git providers are supported:

Supported items

The following items are currently supported:

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.

Considerations and limitations

General Git integration limitations

  • The authentication method in Fabric must be at least as strong as the authentication method for Git. For example, if Git requires multifactor authentication, Fabric needs to require multifactor authentication as well.
  • Power BI Datasets connected to Analysis Services aren't supported at this time.
  • Sovereign clouds aren't supported.
  • The Azure DevOps account must be registered to the same user that is using the Fabric workspace.
  • The tenant admin must enable cross-geo exports if the workspace and Git repo are in two different geographical regions.
  • The commit size is limited to 125 MB.

GitHub Enterprise limitations

Some GitHub Enterprise settings aren't supported. For example:

  • IP allowlist
  • Private networking

Workspace limitations

  • Only the workspace admin can manage the connections to the Git Repo such as connecting, disconnecting, or adding a branch.
    Once connected, anyone with permission can work in the workspace.
  • The workspace folder structure isn't reflected in the Git repository. Workspace items in folders are exported to the root directory.

Branch and folder limitations

  • Maximum length of branch name is 244 characters.
  • Maximum length of full path for file names is 250 characters. Longer names fail.
  • Maximum file size is 25 MB.
  • You can’t download a report/dataset as .pbix from the service after deploying them with Git integration.
  • When naming a folder in Git, the logical ID (Guid) is added as a prefix before the type if the item’s display name:
    • Has more than 256 characters
    • Ends with . or a space
    • Contains any of the following characters: " / : < > \ * ? |

Branching out limitations

  • Branch out requires permissions listed in permissions table.
  • There must be an available capacity for this action.
  • All workspace and branch naming limitations apply when branching out to a new workspace.
  • When branching out, a new workspace is created and the settings from the original workspace aren't copied. Adjust any settings or definitions to ensure that the new workspace meets your organization's policies.
  • Only Git supported items are available in the new workspace.
  • The related branches list only shows branches and workspaces you have permission to view.
  • Git integration must be enabled.

Sync and commit limitations

  • You can only sync in one direction at a time. You can’t commit and update at the same time.
  • Sensitivity labels aren't supported and exporting items with sensitivity labels might be disabled. To commit items that have sensitivity labels without the sensitivity label, ask your administrator for help.
  • Works with limited items. Unsupported items in the folder are ignored.
  • Duplicating names isn't allowed. Even if Power BI allows name duplication, the update, commit, or undo action fails.
  • B2B isn’t supported.
  • Conflict resolution is partially done in Git.
  • During the Commit to Git process, the Fabric service deletes files inside the item folder that aren't part of the item definition. Unrelated files not in an item folder aren't deleted.
  • After you commit changes, you might notice some unexpected changes to the item that you didn't make. These changes are semantically insignificant and can happen for several reasons. For example:
    • Manually changing the item definition file. These changes are valid, but might be different than if done through the editors. For example, if you rename a semantic model column in Git and import this change to the workspace, the next time you commit changes to the semantic model, the bim file will register as changed and the modified column pushed to the back of the columns array. This is because the AS engine that generates the bim files pushes renamed columns to the end of the array. This change doesn't affect the way the item operates.
    • Committing a file that uses CRLF line breaks. The service uses LF (line feed) line breaks. If you had item files in the Git repo with CRLF line breaks, when you commit from the service these files are changed to LF. For example, if you open a report in desktop, save the .pbip project and upload it to Git using CRLF.
  • Refreshing a semantic model using the Enhanced refresh API causes a Git diff after each refresh.

Related content