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,

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.