Forum Discussion
Deployment Rules Setup Issue with SP-Owned Items
Hi,
I am setting up a Deployment Pipeline and triggering it using a Service Principal (SP) so that the SP is the owner of the deployed items. Among these items are semantic models that require connection updates, which I intended to manage through deployment rules.
However, I’ve encountered an issue: when the SP owns the items, I am unable to configure deployment rules. Conversely, if I take ownership of the objects to set up the rules, I cannot transfer ownership back to the SP afterwards.
Has anyone experienced a similar issue or can offer advice on how to manage deployment rules when the SP is the owner?
Thank you for your support!
Hi oldz26,
Hope you are doing well!
As I know, deployment rules can only be configured by the item owner, and the UI doesn't allow a human user to set rules on SP-owned items, nor does it allow transferring ownership back to a SP after a human takes over.
Try this step by step:
- Set the deployment rules first (as a human user who owns the items), configure all your connection/parameter rules in the pipeline
- Then trigger the deployment via the SP, the rules are stored at the pipeline level, not tied to the owner, so they will still be applied during SP-triggered deployments
- Ownership of deployed items will transfer to the SP after it triggers the deployment, but the rules remain intact and continue to execute
Remember that deployment rules are a pipeline-level configuration, so they survive ownership changes. You only need human ownership temporarily to set up the rules, not to run them.
If you need a fully automated setup, you can also configure deployment rules via the Fabric REST API (PUT /deploymentPipelines/{id}/stages/{stageId}/items), which can be called using the SP itself, bypassing the UI restriction entirely.
Hope this helps! Don't forget to accept as solution and thumbs up, that's motivate me to keep helping 🙂
3 Replies
Hi oldz26,
Hope you are doing well!
As I know, deployment rules can only be configured by the item owner, and the UI doesn't allow a human user to set rules on SP-owned items, nor does it allow transferring ownership back to a SP after a human takes over.
Try this step by step:
- Set the deployment rules first (as a human user who owns the items), configure all your connection/parameter rules in the pipeline
- Then trigger the deployment via the SP, the rules are stored at the pipeline level, not tied to the owner, so they will still be applied during SP-triggered deployments
- Ownership of deployed items will transfer to the SP after it triggers the deployment, but the rules remain intact and continue to execute
Remember that deployment rules are a pipeline-level configuration, so they survive ownership changes. You only need human ownership temporarily to set up the rules, not to run them.
If you need a fully automated setup, you can also configure deployment rules via the Fabric REST API (PUT /deploymentPipelines/{id}/stages/{stageId}/items), which can be called using the SP itself, bypassing the UI restriction entirely.
Hope this helps! Don't forget to accept as solution and thumbs up, that's motivate me to keep helping 🙂
Hi oldz26,
Thank you oussamahaimoud for your response to the query.
Following up to check whether you got a chance to review the suggestions given. If the issue still persists please let us know. Glad to help.Thank you.
Hi oldz26,
We haven’t heard from you on the last response and was just checking back to see if your query was answered.
Otherwise, will respond back with the more details and we will try to help .Thank you.
