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
rajeshgumpena's avatar
rajeshgumpena
Regular Visitor
11 months ago

In Fabric, Manage connections and gateways assigns GUIDs to connections. In migration/resolution files, you map logical linked service names to these GUIDs (via "LinkedServiceToConnectionId"). Microsoft Learn notes:

“The value is the GUID of the Fabric connection you want to map to. You can find the GUID in settings of the Fabric connection.”

This suggests that connections are identified internally by GUIDs, so the "name" field in pipeline JSON is tied to that identifier.

Conclusion: It seems intentional that Fabric replaces friendly linkedService.name values with GUIDs to ensure consistency with the internal registry and support environment mapping. While this may cause noisy Git diffs, it doesn’t affect runtime since identity is managed separately. Currently, I haven’t seen any documented way to disable this behavior or preserve custom names.