topic Fabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF in Data Engineering

Fabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF

dataengineerv2 — Tue, 30 Jun 2026 11:23:22 GMT

Migrating an ADF ingestion factory (~219 pipelines, 36 linked services) to Fabric Data Factory programmatically via the REST API. Three connection issues I can't resolve through the API — looking for the supported path or confirmation they're UI/manual-only:
whats is the best apprach to migrate adf pipleins with having parametarized linked services call
1. Connector types not creatable via the Connections REST API. POST /v1/connections returns "Kind: AzureDatabricks is not supported" and "Kind: Ftp is not supported." Which connector kinds does the public Connections API support, and for the rest (Databricks, FTP, …) is the UI the only option, or is there an automation/API path?

2. ADLS Gen2 + Workspace Identity → DMTS_UntrustedEndpointForWorkspaceIdentity. Creating an AzureDataLakeStorage connection with Workspace Identity fails as an untrusted endpoint. What's required to create it via API end-to-end — does the storage account need trusted-workspace-access / the workspace identity pre-granted? Is there an API to establish that trust?

3. Parameterized linked services with per-call dynamic endpoints. Several ADF REST linked services use url = @{linkedService().absolute_url} — the URL is passed by each dataset at runtime, so one linked service calls many URLs. Fabric connections need a fixed endpoint. What's the recommended pattern — one connection per host + dynamic relative URL? Parameterize the connection field by GUID via a Variable Library? Any way to represent a fully dynamic-URL connection?

Environment: Fabric Trial capacity; connections created via a Service Principal. Official docs/links appreciated.

Re: Fabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF

v-saisrao-msft — Wed, 01 Jul 2026 10:00:27 GMT

Hi @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}.

Migration Planning for Azure Data Factory to Fabric Data Factory - Microsoft Fabric | Microsoft Learn

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.

Re: Fabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF

v-saisrao-msft — Mon, 06 Jul 2026 04:03:06 GMT

Hi @dataengineerv2,

Have you had a chance to review the solution we shared earlier? If the issue persists, feel free to reply so we can help further.

Thank you.

Re: Fabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF

v-saisrao-msft — Thu, 09 Jul 2026 04:51:16 GMT

HI @dataengineerv2,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.

Re: Fabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF

dataengineerv2 — Thu, 09 Jul 2026 08:06:04 GMT

just this 2 things getting porblems , the parameterized lnked services and dynamic urls endpoints, i mean the alternatives like varibles which is in preview but can i use that in my migration tool ? i mean that is only useful when you have already created connections , in my tool i just gettging all this thigs from arm template and calling that api to create connections , but due to this dynamic names dont know how i can handle this ?

Re: Fabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF

v-saisrao-msft — Wed, 15 Jul 2026 08:00:23 GMT

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

Convert Azure Data Factory Global Parameters to Fabric Variable Libraries - Microsoft Fabric | Microsoft Learn

Variable library connection reference - Microsoft Fabric | Microsoft Learn

Thank you.

Re: Fabric Data Factory (REST API): 3 connection blockers migrating a parameterized ADF

v-saisrao-msft — Mon, 20 Jul 2026 04:17:33 GMT

Hi @dataengineerv2,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.