When using service account to automatically deploy Fabric pipelines from Dev workspace to upper environments,
the owner of pipelines in target envionment remain unchanged.
In some situations, personal account has made logged in and PL's owner maybe transferred to the personal account, eg. click on "Update All" to resolve source control conflict;
When owner of the PL is under personal account instead of service account, it causes issue when running it, since personal account won't have permission to perform the defined tasks.
If take over ownership of Fabric pipeline is available, it will be very helpful to automatic the deployment process. Which can reset all pipelines in target environment to the service account, to ensure PLs are run under the service account.
ToddChitt
on:
Copy Job needs more functionality
on:
Support for Signed GitHub Commits
on:
Bug: Web URL Conditional Formatting Ignores "Show ...
on:
Apply Conditional Formatting to All Columns/Series...
yicw
on:
In Fabric view, let us assign workspace colors bas...
on:
Introducing Excel-Style Table in Power BI