Copy Job JSON Definition Not Persisted After Editing in Microsoft Fabric

[vestergaardj]

I have the following workspace setup in Microsoft Fabric:

• Production workspace containing:
  • Lakehouses
  • Semantic models
  • Notebooks
  • Copy Jobs
    These are used for production workloads.
• Additional workspaces:
  • Test
  • Development

To support environment separation, I created corresponding lakehouses in the Development workspace and configured a Copy Job to copy data from the Production lakehouse to the Development lakehouse. This setup works correctly.

Scenario

To avoid manually recreating Copy Jobs, I attempted to duplicate an existing Copy Job by:

1. Opening the original Copy Job JSON definition
2. Copying the JSON
3. Updating:
   • The Copy Job name
   • The Copy Job ID
   • The target lakehouse ID
4. Saving/closing the JSON editor

After closing the editor, the Copy Job appears correctly configured and displays the expected settings.

Problem

However, after closing the Copy Job and reopening it, the Copy Job is completely empty — as if it were newly created.

This suggests that:

• The edited JSON definition is not actually being persisted/saved
• Or the manually modified metadata/IDs invalidate the Copy Job without showing an error

Expected Behavior

After editing and saving the Copy Job JSON:

• The updated Copy Job definition should persist
• Reopening the Copy Job should display the saved configuration
• If certain properties (such as IDs) are not allowed to be modified, the UI/editor should provide validation errors or warnings

Actual Behavior

• JSON edits appear accepted initially
• No validation or save errors are shown
• Reopening the Copy Job results in an empty/default Copy Job configuration

Additional Notes

This capability would be very useful for promoting or replicating Copy Jobs across Development, Test, and Production workspaces without needing to recreate them manually.