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

[david_avgarcia]

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 steps of the wizard normally:

• The HTTP connection succeeds
• The assistant retrieves the schema correctly
• I can preview the data without any issues
• All mapping and destination settings are accepted

However, when I reach the final step and click Save, the wizard simply closes without any error message.

After closing:

• No Copy activity is added to the pipeline
• No pipeline is created in the workspace
• Nothing appears in recent items
• There are no warnings, no errors, and no notifications

It looks as if the wizard silently exits without generating the pipeline artifact.

I’ve reproduced this multiple times in a new pipeline and in a new workspace. The behavior is always the same: the setup works, but the final save step does nothing.

This happens specifically with:

• Source: HTTP connector
• Auth: Basic Authentication

Could this be a known issue with the Copy Data Assistant or the HTTP connector?
Any guidance or workaround would be appreciated.

Thanks!

[v-sgandrathi]

HI @david_avgarcia,

Thank you @bariscihan for your answer.

we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.

Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!

[bariscihan · Accepted solution]

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.

[david_avgarcia]

Yes, that is what I have to end up to doing, thank you for the reply!!

[bariscihan]

Yes, that is the approach I will follow.
Thank you for the clarification and for sharing the known issue reference.

For now, I will proceed by creating the pipeline and Copy activity manually instead of using the Copy Data Assistant for HTTP-based sources with Basic Authentication.

Appreciate your support!

[v-sgandrathi]

Hi @david_avgarcia,

This is a known issue with Microsoft Fabric Copy Data Assistant when using an HTTP source and Basic Authentication. Although the wizard validates the connection, retrieves the schema, previews data, and accepts mapping and destination settings, the Save step fails silently, closing the wizard without creating a pipeline or Copy activity and without showing any error. This typically happens during artifact creation because backend validation errors are not displayed in the UI. To work around this, avoid using the Copy Data Assistant for HTTP sources. Instead, manually create a pipeline, add a Copy Data activity, and configure the HTTP source with Basic Authentication, or use an HTTP linked service. This approach is reliable and allows the pipeline to be saved, published, and run until the issue is fixed in a future Fabric update.

Providing the known issues link below:
Microsoft Fabric Known Issues

Thank you
Sahasra.