Forum Discussion
Deployment Rules Setup Issue with SP-Owned Items
- 3 months ago
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,
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 🙂