Forum Discussion
Solved
On-prem SQL Server/MySQL gateway visible in Dataflow Gen2 but NOT in Copy Job or copy data (Fabric)
I’m facing an issue while working with Microsoft Fabric related to on-premises data gateway visibility across different Fabric components. Scenario I have installed and configured an On-premises ...
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 deekshi_03
This mismatch usually comes down to gateway version/region/permissions or to using the wrong gateway type for pipelines.
Pipelines/Copy job do support on‑prem gateways — but they require recent gateway builds and correct region alignment. Microsoft lists Fabric pipeline support via on‑prem gateway as GA, with minimum versions and monthly support cadence.
If the gateway is older or registered in a different region than your Fabric workspace capacity, Copy job may not surface it (Dataflows Gen2 can sometimes still bind, hence the discrepancy). Community threads highlight “Existing connection” not appearing until region alignment and permissions are corrected.
Alternatively, for network‑isolated scenarios, Virtual Network (VNet) Data Gateway is now supported by Copy job (Preview/Docs) and exposes a different selection path than the classic on‑premises gateway. If you created a VNet gateway but are looking under the on‑premises gateway dropdown, it won’t appear.
KIndly accept this as a solution if it solves your problem!