Publishing as Service Principal

[Anonymous]

I’m trying to solve the following issue:

We have a shared workspace that’s managed by a service principal. Our team works collaboratively on the same dashboards, and we want to avoid having to constantly take over the semantic models.

How can we publish reports on behalf of the service principal? Or is it possible to assign the service principal as the model owner?

Currently, we have several users with admin rights in the workspace, along with the service principal having the same permissions.

Thank you!

[v-echaithra]

Hi @Anonymous ,

We wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,
Chaithra.

[v-echaithra]

Hi @Anonymous ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,
Chaithra.

[mohitkumawat]

There is no direct way to reassign a dataset's owner to a service principal after publishing.

But you can try these options 

Option A: Use Deployment Pipelines with the Service Principal

Option B: Publish via Power BI REST API

Option C: Use Power BI Deployment Automation (e.g., Azure DevOps or Git Integration)

Option D:- Create one generic ID for all team members 

[Deku]

If you use pbip and publish only with fabric API using the service principal it would have ownership, unless someone takes it over.

You need to take ownership to setup connections or refresh schedule, unless you are going to use the power bi APIs to update these.

Why do you want it to retain ownership?

[Anonymous]

Right now, we’re publishing from Power BI Desktop. Our goal is to avoid individual ownership so the semantic model isn’t tied to a specific user, since team members may change frequently. We’ve already noticed that when someone does a take over, things like scheduled refresh get disabled.

[lbendlin]

That's a double edged sword.  You need an owner for auditing purposes, and to yell at when the semantic model causes too many CUs.

[lbendlin · Accepted solution]

and we want to avoid having to constantly take over the semantic models

That is not something you can avoid at the moment.

If this is important to you please consider voting for an existing idea or raising a new one at https://ideas.fabric.microsoft.com