400 Error When Using On-Premises Data Gateway with Fabric Pipelines (SQL Server Source)

[marcos-1992]

Hello everyone,

We are encountering a persistent issue when trying to connect a Fabric Data Factory pipeline to an on-premises SQL Server database using the On-Premises Data Gateway. The same connection works correctly from Power BI and Dataflow Gen2 (in the same Fabric Workspace), but not within the pipeline’s Copy Data activity.

Scenario Details:

• Environment:

  • Microsoft Fabric (Data Factory Pipelines) - SKU: F8, Region: North Central US

  • SQL Server hosted on Windows Server 2019

  • On-Premises Data Gateway installed on the server (version 3000.270.10 - May 2025, upgraded and restarted)

  • Connection is configured and appears online under Manage Connections and Gateways in the Fabric workspace

• Issue:
  When configuring a new Copy Data activity in a pipeline:

  1. We select the existing connection (the one that works with Power BI and Dataflows)

  2. When trying to browse the source tables (or validate the connection), we receive a 400 error

     

Troubleshooting Steps Taken So Far:

1. Firewall Temporarily Disabled on the on-prem server (no change)

2. Gateway Version Updated to the latest version, and the server was rebooted

3. Tested Multiple Auth Types:

   • SQL Authentication

   • Active Directory Password Authentication

4. Tested Connections to Multiple Databases on the same server

5. Changed Privacy Level Settings (from Organizational to None)

6. Verified Connection Works in:

   • Power BI Desktop (via Gateway)

   • Dataflow Gen 2

   • Connection test in the “Manage Gateways” area in Fabric (all green)

   • Connectivity with  *.frontend.clouddatahub.net from the Server where the gateway is installed

Observations:

• The issue only occurs within Fabric Pipelines when configuring the source for the Copy Data activity.

• It seems pipeline-specific, suggesting this could be a limitation, bug, or configuration gap within the pipeline service itself.

• I've reviewed similar issues posted in the forums and applied suggested workarounds (e.g., firewall, gateway version, permissions), but the problem persists.

Questions:

• Is there any known limitation or extra configuration step required for pipelines to use gateway connections that differ from Power BI/Dataflows?

• Are there specific ports or services beyond the usual for Gateway-to-SQL that Fabric Pipelines use?

Any help, suggestions, or pointers would be highly appreciated. 

Thanks in advance!

[marcos-1992]

Hi @v-lgarikapat,

Thank you for your response and for sharing the documentation.

We’ve followed all the recommended steps and are using the same login type that works successfully with both Dataflow Gen2 and Power BI. Unfortunately, the issue still persists within the Fabric Pipeline.

We also confirmed that the On-Premises Data Gateway instance running on the server is the only one configured and active.

We’ll continue testing with different configurations, and if we’re unable to resolve it, we’ll proceed with opening a support ticket.

Thanks again for your assistance!

Best regards,
Marcos

[v-lgarikapat]

Hi @marcos-1992 ,

Thanks for the update and for reviewing the setup on your end.

We appreciate your efforts in testing different configurations. If the issue persists, opening a support ticket would be a good next step.

Also, please continue to share any updates here, as it will help other community members find and follow the solution more easily.

Feel free to reach out if you have any other questions.

Best regards,
Lakshmi Narayana

[v-lgarikapat]

Hi @marcos-1992 ,

I wanted to follow up and confirm whether you’ve had a chance to review the information we provided.
If you have any questions or need further clarification, please don’t hesitate to reach out.

Additionally, have you had a chance to raise a support ticket regarding this issue?

If you’re still encountering any challenges, we’d be happy to assist you further.

Best Regards,

Lakshmi Narayana

[marcos-1992]

Hi @v-lgarikapat,

Thank you for the follow-up.

We haven’t yet been able to resolve the issue. We're currently in the process of making changes to the subscription associated with the Fabric instance, which are required to submit the support ticket. Our goal is to have the ticket created by tomorrow.

As soon as we receive any insights or updates from the Microsoft Support team regarding the root cause, we’ll share the details here in the thread.

Thanks again for your continued support.

Best regards,
Marcos

[v-lgarikapat]

@marcos-1992 ,

Thanks for the update.

We understand and appreciate you working on it. Looking forward to hearing back once you get more information from Microsoft.

Best Regards,

Lakshmi Narayana

[v-lgarikapat]

Hi @marcos-1992 ,

Thanks for reaching out to the Microsoft fabric community forum.

I have included the learning documents for your reference; they may help you

Configure SQL server in a copy activity - Microsoft Fabric | Microsoft Learn

Solved: Re: Status 400 Error when setting up an SQL Gatewa... - Microsoft Fabric Community

How to access on-premises data sources in Data Factory - Microsoft Fabric | Microsoft Learn

The previously known issue has been fixed.

Known issue - Multiple installations of on-premises data gateway causes pipelines to fail - Microsof...

If you're still facing the same issue,
I suggest raising a support ticket so the support team can assist you in resolving the problem.
Please refer to the link below for instructions on how to raise a support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

If this post helped resolve your issue, please consider marking it as the Accepted Solution.
This not only acknowledges the support provided but also helps other community members find relevant solutions more easily.

We appreciate your engagement and thank you for being an active part of the community.

Best regards,
LakshmiNarayana