Changing Fabric Notebook Ownership

Hi Anonymous , I think the only way out is to delete the current schedule, and then create new one with the other user who you want the notebook to be run as.

Recommended option would be to use a service pricipal or workspace identity instead of individual credentials so this will not be enocuntered again.

Hi Anonymous ,

Yes, this can happen — changing the notebook owner does not automatically change the identity that the scheduled run uses. The schedule keeps the credentials of the person who originally created the schedule, unless you recreate it. That’s why it’s still running with your access even though the ownership is now different.

We had the same issue in our environment. The only thing that fixed it was to delete the existing schedule and create a brand-new schedule using the new owner’s account. Once the schedule is created under that user, Fabric runs the notebook with their permissions instead of yours.

Just updating ownership doesn’t replace the execution identity because the schedule itself is tied to the user who created it.

So in short:

• Changing notebook owner → does not change the schedule’s identity

• Recreating the schedule with the new owner → works correctly

After we recreated the schedule, the runs immediately started using the correct workspace access.

Hope this helps. If so, please give a Kudos 👍 or mark as Accepted Solution ✔️

– Gopi Krishna