[FEATURE] Add Artifact Ownership Account Change Privilege to CI/CD Pipeline

[saikumar1427]

Use Case / Problem

while deploying the artifacts using service principal it is showing owner as service principal.

for example: if we are running CICD pipeline using X account then after the deployment it is changing to X for the existing destination workspace artifacts.

Proposed Solution

while deploying the artifacts using service principal we need an option to change owner of the artifacts while running the fabric-cicd

Alternatives Considered

No response

Impact Assessment

• This would help me personally
• This would help my team/organization
• This would help the broader fabric-cicd community
• This aligns with Microsoft Fabric roadmap items

Implementation Attestation

• I understand this feature should maintain backward compatibility (if applicable)
• I understand this feature should not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cicd's established patterns and conventions

Implementation Notes

No response

[microsoft-github-policy-service]

Thank you for submitting this issue, @saikumar1427.
A member of the Fabric CICD team will review your submission and provide feedback shortly.

[github-actions]

AI Assessment: Needs Discussion

Changing artifact ownership programmatically during deployment is a significant capability that would require careful consideration. Fabric artifacts are owned by the identity performing the deployment, as enforced by the REST API and Fabric platform. Automating owner reassignment after creation or update is not supported by any public Fabric API as of the current REST documentation (see Fabric REST API docs). Implementing this would require an explicit API endpoint for re-assigning ownership, which does not exist.

Integrating such a feature could introduce security and compliance risks, since ownership semantics affect governance, access control, and auditing. Forcing ownership to change as part of a CI/CD flow may not be technically feasible without direct REST support and clear platform guidance from Microsoft Fabric.

Recommend raising the underlying use case (separation of deployer identity and artifact owner) with Microsoft Fabric product team for REST API support. Until then, this feature cannot be implemented in fabric-cicd. If additional context exists—such as an out-of-band process or a hidden API endpoint—please provide citation for feasibility review.

Next Steps
🔔 Escalated to team — This issue requires team review and has been flagged for attention.

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cicd to notify the team.

[github-actions]

🔔 @microsoft/fabric-cicd — This issue has been flagged by AI triage as requiring team attention. Please review the assessment above.