Takeover of Fabric objects? Or at least, set the user to call a notebook

[daniele_tiles]

Hi to all,

we've found out yesterday that's isn't possible to Takeover of other  Fabric objects, exept of the semantic models.

This can cause some issues, like we've experienced yesterday:

1. One of our developers has preparared a Notebook that calls the Power BI Admin API, thorugh the sempy library. He hasn't the rights to call them for the client, so we preparared it, and uploaded to the Fabric Tenant
2. The client tested the notebook with a Power BI\Fabric administrator, and worked just fine
3. The client tried to schedule the notebook through a pipeline, and it didn't succeeded.

The error was a 401 Unauthorized. We quickly understood it was launched with the user owner of the notebook (the developer), and there was no way to take over of the notebook, or to set in the pipeline to launch it with the user who has scheduled the pipeline.

The only way was for the Fabric administrator to make a copy of the notebook (being himself the owner), and then everything worked fine.

HTH

Daniele Tiles

[Anonymous]

Hi @daniele_tiles 

Thank you very much for sharing! This helps more people solve problems.

Thanks also to spencer_sa .

Regards,

Nono Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[spencer_sa · Accepted solution]

We have noticed the same.  There is another way around if you want to change the whole workspace to be owned by a single user.  (We're looking at using service accounts)

If you have DevOps source control configured you can synch to a repo, break the connection, then as the user you want to own everything recreate the connection and synch from the repo to the workspace (overwriting everything)