Copy Job simplifies your data ingestion with non-compromising experience from any source to any destination. Whether you need batch or incremental copying, Copy Job provides the flexibility to meet your data needs while keeping things simple and intuitive. Check out the details in Announcing Public Preview: Copy Job in Microsoft Fabric | Microsoft Fabric Blog | Microsoft Fabric
Copy Job doesn’t just simplify data movement—it also gives you full control over what you copy and how. You can choose specific tables and columns, map data, and customize read/write behaviors to suit your requirements.
By default, Copy Job appends data to your destination so that you never miss any change history. However, you can also customize the write behavior to upsert data on Azure SQL DB or SQL Server and overwrite data on Fabric Lakehouse tables, giving you full flexibility to match your needs.
Upsert for Azure SQL DB or SQL Server
Keep your source and destination in sync by incrementally loading new or updated rows and upserting them into SQL DB or SQL Server. After selecting incremental copy mode, simply enable the upsert option in advanced settings, choose a key column, and you’re all set!
Overwrite for Fabric Lakehouse Tables
Now, you can load your dataset from any source and overwrite it in Fabric Lakehouse tables, keeping source and destination fully synchronized. This is especially useful for smaller tables without timestamp or ID columns to identify changes.
Once you create a Copy Job, just enable the overwrite option in advanced settings below.
The Microsoft team is rapidly adding more connectors and capabilities like above. Got a feature in mind? Share it with us through the Microsoft Fabric Ideas portal.
Reference:
What is Copy job (preview) in Data Factory - Microsoft Fabric | Microsoft Learn
How to create a Copy job (preview) in Data Factory - Microsoft Fabric | Microsoft Learn
How to monitor a Copy job (preview) in Data Factory - Microsoft Fabric | Microsoft Learn