"BadRequest" error while trying to test a connection in a BLOB source on Azure Data Factory

Ícaro Costa 20 Reputation points
2023-02-08T12:05:23.88+00:00

I have a BLOB dataset in Azure Data Factory with some JSON files that I want to feed into a Data Flow. The connection to the BLOB itself seem to be working since when I click "Test Connection" it gives me a green icon, and it is able to load some preview data. However, when I go to the Data Flow and select this Dataset as a source, the "Test Connection" button gives me the following error:

BadRequest - RunId: d1507e64-538d-4c06-a1ab-b68ac72b8af0

Which doesn't help much. What is possibly happening here?

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,415 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,479 questions
Accepted answer
  1. AnnuKumari-MSFT 30,361 Reputation points Microsoft Employee
    2023-02-09T09:59:37.48+00:00

    Hi Ícaro Costa ,

    Welcome to Microsoft Q&A platform and thanks for posting your question here. As I understand your issue you are facing an error : "BadRequest" when you are trying to test connection of a JSON dataset inside your dataflow. Please let me know if that is not the case .

    Make sure you are not using Self hosted IR in dataflow since Dataflow only supports Auto Resolve Integration Runtime

    Point the linked service to AutoResolve Integration Runtime that is the default IR in Azure datafactory.

    testConnction

    Hope it helps. Please do consider clicking Accept Answer and Up-Vote for the same as accepted answers help community as well.

    2 people found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ícaro Costa 20 Reputation points
    2023-02-08T12:11:00.54+00:00

    I think I understood what the problem was, I was using different integration runtimes to test the different connections. So, the problem is resolved if you select the same integration runtime you used to connect the dataset on the debug session.

  2. rajendra verma 0 Reputation points
    2023-12-01T12:15:51.2933333+00:00

    I resolved this issue by restarting the debug flows (sometimes the engine not find the spark engine)

    0 comments