Forum Discussion
On-prem SQL Server/MySQL gateway visible in Dataflow Gen2 but NOT in Copy Job or copy data (Fabric)
Hello deekshi_03
Community Support has already responded to you about this behaviour.
"This situation is caused by a current limitation in Microsoft Fabric, rather than an issue with your gateway setup. Dataflow Gen2 and Copy Job use different backend engines: Dataflow Gen2 relies on the Power Query/Power Platform infrastructure, which fully supports classic on-premises data gateways, so the gateway appears and functions correctly there."
However you can try the following -
Verify permissions
- In Manage connections and gateways, add yourself (and the workspace) as gateway users and ensure Edit rights in the workspace. Lack of user binding can hide connections in the Copy assistant.
Use an Existing connection in Copy job
- In the Copy assistant, click View more / Existing connections and search for the connection you created in Manage connections and gateways; this often avoids re‑entering credentials and surfaces the gateway‑bound connection.
Restart the gateway service & refresh Fabric
- Restart PBIEgwService on the gateway host and refresh your browser; transient state can block discovery.
If this helped, kindly appreciate giving a Kudos or accepting as a Solution.
Hello deborshi_nag
Thanks for the explanation.
I’ve already verified the gateway version, region alignment, and permissions, and everything matches the Fabric workspace capacity correctly. The gateway is running on a supported, up-to-date build and is registered in the same region as the workspace.
To clarify further, I have not created a VNet Data Gateway. I’m using a classic on-premises data gateway only, and I’m explicitly looking for it under the on-prem gateway option. This gateway works as expected in Dataflow Gen2, where I can successfully connect to on-prem SQL Server / MySQL.
However, the same gateway still does not appear in Copy Job / Copy Data activity, despite all the prerequisites being met. This creates an inconsistency where Dataflow Gen2 is able to detect and use the gateway, but Copy Job is not.
Could you clarify the reason the on-premises gateway appears in Dataflow Gen2 but not in Copy Job?
Hello deekshi_03
Community Support has already responded to you about this behaviour.
"This situation is caused by a current limitation in Microsoft Fabric, rather than an issue with your gateway setup. Dataflow Gen2 and Copy Job use different backend engines: Dataflow Gen2 relies on the Power Query/Power Platform infrastructure, which fully supports classic on-premises data gateways, so the gateway appears and functions correctly there."
However you can try the following -
Verify permissions
- In Manage connections and gateways, add yourself (and the workspace) as gateway users and ensure Edit rights in the workspace. Lack of user binding can hide connections in the Copy assistant.
Use an Existing connection in Copy job
- In the Copy assistant, click View more / Existing connections and search for the connection you created in Manage connections and gateways; this often avoids re‑entering credentials and surfaces the gateway‑bound connection.
Restart the gateway service & refresh Fabric
- Restart PBIEgwService on the gateway host and refresh your browser; transient state can block discovery.
If this helped, kindly appreciate giving a Kudos or accepting as a Solution.