Forum Discussion

davadrl's avatar
davadrl
Regular Visitor
11 months ago

Data Pipeline: linkedService name changes to GUIDs inflate Git diffs

Hi all, I've noticed that Microsoft Fabric is now replacing the linkedService.name property in pipeline-content.json with randomly generated GUIDs — even though previously I used defined, consistent...
data engineering
data pipeline
anilgavhane's avatar
anilgavhane
Icon for Super User rankSuper User
11 months ago

davadrl 

Use a Resolutions File

Microsoft recommends using a resolutions.json file to map your original linked service names to Fabric connection GUIDs. This helps maintain consistency across environments.

Example structure:

 

[ { "type": "LinkedServiceToConnectionId", "key": "lakehousename", "value": "cc7e4456_6230_4e46_9986_ab7c206ded89" } ]

 

You can find the GUID in the Fabric connection settings. This mapping ensures your pipeline logic remains stable even if the internal GUID changes.

More details: Microsoft Learn – Add Connections to Resolutions File

 

Can You Disable GUIDs?

No, there’s currently no supported way to disable or override GUID generation in pipeline-content.json. Microsoft has not announced plans to revert to the previous behavior.

 

✅ Best Practices

  • Use resolution files for all linked services.
  • Avoid editing pipeline-content.json manually—let Fabric manage it and use external mapping for clarity.
  • Document your mappings in Git to aid reviewers.
  • Raise feedback via Microsoft Fabric Community or support channels if this behavior impacts your workflow.

 

Let me know if you’d like help generating a resolution file or scripting the mappings for your pipelines.