Forum Discussion

deekshi_03's avatar
deekshi_03
New Member
7 months ago
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 ...
data engineering
Data Pipeline
  • deborshi_nag's avatar
    deborshi_nag
    7 months ago

    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. 

v-sgandrathi's avatar
v-sgandrathi
Community Support
7 months ago

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.