Forum Discussion
Helper IFabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF
Hi dataengineerv2,
According to the current documentation, Variable Library and Connection Reference variables only work with existing Fabric connections; they do not create connections from ARM metadata. Fabric connections also do not support parameter expressions the same way as ADF, so dynamic connection definitions (for example, @{linkedService().absolute_url}) have to be manually re-authored. For Web/WebHook activities, Fabric expects a fixed Web v2 connection (host) mapped through UrlHostToConnectionId.
How to Add Connections to Your Resolutions File - Microsoft Fabric | Microsoft Learn
Variable library connection reference - Microsoft Fabric | Microsoft Learn
Thank you.
Community SupportHi dataengineerv2,
Microsoft's migration guidance says that moving Azure Data Factory to Fabric Data Factory involves adjusting some ADF concepts because the architectures differ. Before you call Create Connection, use the List Supported Connection Types API to see which connector types and creation methods are supported. For ADLS Gen2 with Workspace Identity, set up the workspace identity, grant the required Azure RBAC permissions, and, for firewall-enabled storage accounts, configure Trusted Workspace Access (Microsoft notes that Trusted Workspace Access isn't supported on Trial capacities). For Web/WebHook activities that use dynamic URLs, Fabric uses a connection plus a relative URL (for example through UrlHostToConnectionId) instead of ADF-style dynamic connection endpoints such as @{linkedService().absolute_url}.
How to Add Connections to Your Resolutions File - Microsoft Fabric | Microsoft Learn
Connections - List Supported Connection Types - REST API (Core) | Microsoft Learn
Connections - Create Connection - REST API (Core) | Microsoft Learn
Authenticate with Microsoft Fabric workspace identity - Microsoft Fabric | Microsoft Learn
Trusted workspace access in Microsoft Fabric - Microsoft Fabric | Microsoft Learn
Thank you.