Copy Activity creates incorrect Lakehouse schema (schema name replaced by table name)

Hi seba_garces_crz ,

Thank you for providing the screenshots and additional information. From what I can see, the Copy Activity is configured with distinct values for the Lakehouse schema and table name and there are no apparent setup issues that would explain the behavior you're experiencing.

Given that the pipeline functioned correctly until late May and is now creating objects under an unexpected schema, this does not seem to be a typical configuration problem. Your tests with alternative schema naming also led to the same outcome indicating the issue may not stem from the activity's defined values.

Could you review the Input and Output details from a recent pipeline run to verify whether the schema and table values are being passed accurately at execution time If these values are correct in the run details but the Lakehouse still creates objects under the wrong schema, it may indicate a service-side issue rather than a configuration error.

If the execution payload confirms the expected schema and table names, I suggest opening a Microsoft Fabric support ticket and including the pipeline run ID workspace details, and your screenshots. The observed behavior in the Lakehouse structure does not align with the sink configuration, and the Fabric engineering team may need to determine if a recent platform update is affecting Copy Activity writes to schema enabled Lakehouses.

Thank you.