On-prem SQL Server/MySQL gateway visible in Dataflow Gen2 but NOT in Copy Job or copy data (Fabric)

[deekshi_03]

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 Data Gateway on my machine.

• I have admin access to the gateway and workspace.

• I am using Microsoft Fabric (Free Trial) with a student email ID.

What works

• When I use Dataflow Gen2, I am able to:

  • Connect to on-prem SQL Server / MySQL

  • See and select the existing on-prem gateway

  • Successfully access and preview data

What does NOT work

• When I try to use Copy Job / Copy Data activity:

  • The existing gateway does NOT appear

  • Gateway dropdown shows None

  • I’m unable to select or reuse the gateway that works in Dataflow Gen2

Checks already performed

I have already verified the following:

• Required database drivers (MySQL / SQL Server) are installed

• Outbound firewall rules are allowed

• Gateway service is running and online

• Gateway is properly registered and visible in Dataflow Gen2

• I have full admin permissions on:

  • Gateway

  • Workspace

• Public network access and connectivity are validated

Despite all this, Copy Job does not recognize the gateway.

Can someone please clarify:

• Whether this is a known limitation

• Or if there are specific prerequisites for enabling gateway usage in Copy Job?

Any official references or workaround suggestions would be greatly appreciated.

[v-sgandrathi]

Hi @deekshi_03,

Following up to see how things are going with your issue. Has the response provided resolved your query? We’d love to know if you need more help or if everything’s working fine now.

Thanks for staying active in the Microsoft Fabric Community!

[v-sgandrathi]

Hi @deekshi_03,

we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.

Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!

[v-sgandrathi]

Hi @deekshi_03,

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. In contrast, Copy Job uses the Fabric Data Integration runtime, where support for classic on-premises gateways is still limited, especially in Fabric Free Trial or student tenants. Therefore, even if the gateway is updated, region-aligned, and has the necessary permissions, it may not show up in Copy Job. This explains why the gateway is visible in Dataflow Gen2 but not in Copy Job. Currently, this is a product limitation, and typical workarounds include using Dataflow Gen2 for on-premises ingestion or a paid Fabric capacity or VNet Data Gateway for pipeline scenarios.

Thank you.

[deekshi_03]

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?

[deborshi_nag · Accepted solution]

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. 

[deborshi_nag]

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!

[deekshi_03]

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?

[tayloramy]

Hi @deekshi_03, 

Just to confirm, are both items being created in the same workspace or in different worksapces on the same capacity? 

I've not seen this behaviour in my gateway, so I recommend opening a ticket with Microsoft to see what is up, but I would like to understand what the scope of the issue is.