Forum Discussion
Fabric SQL DB connector from Data Factory
Hi Anonymous
Unfortunately not resolved yet. As an workaround, I am landing my data in LH as a middle step and can do LH to SQL DB transfer.Hi Mayumi_2021 ,
Thanks for getting back and sorry for late reply.Since your source is an on-premises SQL DB, the activity is running on a gateway. However, Fabric SQL DB is a cloud-based service, and cloud connections are not compatible with the gateway by default. To resolve this issue, you need to manually create a connection for Fabric SQL DB and enable the option "Allow this connection to be used with gateways" in the connection settings.
Steps:- Go to Settings --> Manage Connections and Gateways.
- Create a new connection for Fabric SQL DB.
- In the connection settings, enable "Allow this connection to be used with gateways."
- Save the changes and retry the pipeline execution.
If the issue persists, check the error logs and ensure the correct authentication method is used. If further assistance is needed, consider raising a support ticket.
Microsoft Fabric Support and Status | Microsoft Fabric
Hope this helps.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.
Best Regards,
Vinay.
I think this error is popping up as the result of a change made on the Fabric side. Comparing an old Copy Task with a new one side by side reveals a new field. It appears the old Copy Tasks are unaffected by the new change which requires you to manually allow a Fabric resource to connect to a Data Gateway resource. This surely lead to confusion for us when all of the existing Copy Tasks were working fine but the new ones threw this error.
To resolve this you must allow Gateway connections on the destination connection. Open your Copy Task, click the Destination tab, and next to your Connection you can press Edit and there you will find the "Allow this connection to be used with data gateways" checkbox.
This worked for me, thanks!