topic Re: GIT integration: azure devop - fabric in Data Engineering

GIT integration: azure devop - fabric

Antongig — Wed, 28 Jan 2026 15:04:00 GMT

I have a workspace in microsoft fabric and it is connected to an azure devops git repository.
When I change the name of an artifact for example a notebook, it does not track the rename properly and shows only the old name in the repo but the new name does not even appear anywhere in the repo even though it exists in fabric.

azure devops repo: file has old_filename and new_filename does not exist

fabric workspace: file has new_filename and old_filename does not exist

is this a fabric bug and do I have to delete and recreate all artifacts or what can I do that it gets tracked properly?

Re: GIT integration: azure devop - fabric

ssrithar — Wed, 28 Jan 2026 15:52:38 GMT

Hi @Antongig ,

According to Microsoft Learn this is an expected due to how Fabric identifies items. Microsoft Learn.

Fabric uses a Logical ID (a unique GUID) to track artifacts, rather than their display name. When you rename a notebook in the UI, Fabric updates the displayName property inside the metadata but does not always rename the physical folder in Git.

Official Solutions from Microsoft Learn & Community
You do not need to delete and recreate everything. Here are the recommended ways to fix the naming mismatch:

Option 1: The "Save As" Method (Cleanest)
As noted in the Fabric Community discussions referenced by Microsoft support:

In Fabric, open your notebook and select Save As with the New Name.

Go to the Source Control panel and Commit the new notebook.

Delete the old notebook from the Fabric workspace.

Commit that deletion to Git. This forces Git to remove the old folder and create a new one with the correct name.

Option 2: Manual Git Folder Rename
If you are comfortable with Git:

Clone the repo locally or use the Azure DevOps "Rename" feature in the Browser.

Rename the artifact's folder to NewName.Notebook.

Crucial: Open item.metadata.json and ensure the displayName matches the new name.

Commit and push these changes.

In Fabric, go to Source Control and click Update All. Fabric will re-bind the item using its Logical ID.

Option 3: Disconnect/Reconnect (The "Soft Reset")
Go to Workspace Settings > Git Integration.

Disconnect the workspace.

In Azure DevOps, manually rename the folder to your preferred name.

Reconnect the workspace to the branch.

Choose the sync direction that prioritizes your corrected Git folder.

If this post helps, then please appreciate giving a Kudos or accepting as a Solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

Re: GIT integration: azure devop - fabric

Thomaslleblanc — Thu, 29 Jan 2026 13:43:41 GMT

Prefer the “Save As → Commit → delete old → Commit” pattern for renames done from the Fabric UI.

Re: GIT integration: azure devop - fabric

chetanhiwale — Fri, 30 Jan 2026 05:11:47 GMT

Hi @Antongig ,

the method suggested by @Thomaslleblanc is correct. We have encountered this issue earlier and have followed the same approach.

Hope this helps !!