Scalability Concern: Managing 5000+ Shortcuts in Fabric Git Integration

[vi1996ash]

In Fabric CI/CD, when creating a committing shortcut to Git, it generates one file per lakehouse. Since we expect to have over 5000 shortcuts, managing all of them in a single file could be challenging. Is it possible to have a separate file for each shortcut?

[v-echaithra]

Hi @vi1996ash ,

We’d like to confirm whether your issue has been successfully resolved. If you still have any questions or need further assistance, please don’t hesitate to reach out. We’re more than happy to continue supporting you.

Best Regards,
Chaithra E.

[v-echaithra]

Hi @vi1996ash ,

Thank you for reaching out to Microsoft Community.

As of now, Microsoft Fabric's CI/CD integration with Git stores all Lakehouse shortcuts in a single JSON file per workspace when committing.

Unfortunately, the platform does not yet support saving each shortcut in a separate file, which can make managing a large number of shortcuts more challenging.

As a temporary solution, maintain your own logical separation in Git for shortcuts:

/shortcuts/      --> Folder name
lakehouse1-shortcut.json
lakehouse2-shortcut.json

Use a scripted deployment process (e.g., via Fabric REST APIs or Fabric CLI when supported) to parse and deploy these into the actual workspace.

As this is a real scalability issue. Please consider checking out the Issues forum here:
Issues - Microsoft Fabric Community
And if it is not there, then you could post it in the same forum.
I hope this answers your query.

Best Regards,
Chaithra E.