Forum Discussion

david_avgarcia's avatar
david_avgarcia
Frequent Visitor
6 months ago
Solved

Copy Data - Use Cope Assistant (HTTP Connection) closes without adding activity to pipeline

Hi, I’m experiencing an issue with the Copy Data Assistant in Microsoft Fabric when trying to create a copy activity from an HTTP source using Basic authentication. I can navigate through all step...
  • bariscihan's avatar
    6 months ago

    If I were to propose a solution myself, I would avoid relying on the Copy Data Assistant entirely for HTTP-based sources and instead configure the pipeline manually.

    Based on the observed behavior, this does not look like a configuration or permission issue. The fact that the wizard successfully validates the connection, retrieves the schema, previews the data, and accepts mapping and destination settings strongly suggests that the failure happens during the final artifact creation step. Since this step fails silently, the Copy Data Assistant is not reliable for production use in this scenario.

    My recommended approach would be:

    • Create a pipeline manually

    • Add a Copy Data activity explicitly

    • Configure the HTTP source directly within the activity

    • Use an HTTP Linked Service with Basic Authentication

    • Define mapping and destination settings manually

    With this approach, the pipeline can be saved, published, and executed consistently without unexpected UI behavior.

    If I wanted to further diagnose the root cause or provide Microsoft with a more actionable bug report, I would need additional information such as:

    • The exact structure of the HTTP response (JSON object vs array, nested fields, etc.)

    • How authentication headers are being sent (standard Authorization header vs custom headers)

    • Whether the API uses pagination, redirects, or rate limiting

    • The destination type being used (Lakehouse table, Warehouse table, or file-based sink)

    • The workspace capacity type (Trial, F SKU, or P SKU)

    • Any errors or failed requests visible in the browser developer console (F12) at the moment the Save button is clicked

    Overall, this behavior appears to be a product limitation or bug in the Copy Data Assistant when used with HTTP sources and Basic Authentication, rather than a user-side misconfiguration. Until this is addressed in a future Fabric update, manually creating the pipeline is the most stable and predictable workaround.