MS Fabric Data Migration to Service Principal
Budget / Salary₹600–1,500
TypeFreelance project
LocationRemote
Posted1 hour ago
Microsoft Fabric Pipeline & Notebook Ownership / Service Principal Migration
We are looking for expertise to help us migrate the authentication and execution model of our existing Microsoft Fabric Data Pipelines, Notebooks, Connections, and Scheduled Triggers from individual user accounts to a Service Principal.
Currently, several Fabric pipelines and notebooks are created, owned, and executed using individual user identities. Scheduled triggers and pipeline executions are also dependent on these individual accounts.
The key challenge is user dependency and ownership continuity. When an employee who created or owns a pipeline/notebook leaves the organization or moves to another role, the associated Fabric artifacts and scheduled processes may continue to be tied to that individual's identity. This creates an operational risk because the pipelines, notebooks, connections, and triggers may fail or require manual intervention when the user's access is removed.
What we need
We want to establish a Service Principal–based execution and authentication model so that our Fabric workloads are no longer dependent on individual users.
Specifically, we need help with:
Migrating existing Fabric Pipelines from individual user authentication to a Service Principal.
Migrating Notebooks and their authentication/connection dependencies to a Service Principal.
Migrating existing Fabric Connections to use Service Principal authentication wherever supported.
Updating Scheduled Triggers so that pipeline execution is independent of an individual's account.
Reviewing existing pipelines, notebooks, datasets, and other dependencies for any hidden user-level authentication.
Determining how ownership, permissions, workspace roles, and item-level access should be configured for the Service Principal.
Ensuring that existing workloads continue to run without interruption after the migration.
Establishing a standardized approach so that new Fabric pipelines and notebooks are also created/configured using the Service Principal model wherever appropriate.
Desired Outcome
The ultimate goal is to eliminate individual user-account dependency from our Microsoft Fabric data platform and move toward a service-account/service-principal-based architecture.
This will provide better continuity when team members leave or change roles, reduce operational risk, and ensure that scheduled data workloads continue to execute regardless of who originally created or configured them.
You dont have to work on actual project, just guite what can be done is enough
We are looking for expertise to help us migrate the authentication and execution model of our existing Microsoft Fabric Data Pipelines, Notebooks, Connections, and Scheduled Triggers from individual user accounts to a Service Principal.
Currently, several Fabric pipelines and notebooks are created, owned, and executed using individual user identities. Scheduled triggers and pipeline executions are also dependent on these individual accounts.
The key challenge is user dependency and ownership continuity. When an employee who created or owns a pipeline/notebook leaves the organization or moves to another role, the associated Fabric artifacts and scheduled processes may continue to be tied to that individual's identity. This creates an operational risk because the pipelines, notebooks, connections, and triggers may fail or require manual intervention when the user's access is removed.
What we need
We want to establish a Service Principal–based execution and authentication model so that our Fabric workloads are no longer dependent on individual users.
Specifically, we need help with:
Migrating existing Fabric Pipelines from individual user authentication to a Service Principal.
Migrating Notebooks and their authentication/connection dependencies to a Service Principal.
Migrating existing Fabric Connections to use Service Principal authentication wherever supported.
Updating Scheduled Triggers so that pipeline execution is independent of an individual's account.
Reviewing existing pipelines, notebooks, datasets, and other dependencies for any hidden user-level authentication.
Determining how ownership, permissions, workspace roles, and item-level access should be configured for the Service Principal.
Ensuring that existing workloads continue to run without interruption after the migration.
Establishing a standardized approach so that new Fabric pipelines and notebooks are also created/configured using the Service Principal model wherever appropriate.
Desired Outcome
The ultimate goal is to eliminate individual user-account dependency from our Microsoft Fabric data platform and move toward a service-account/service-principal-based architecture.
This will provide better continuity when team members leave or change roles, reduce operational risk, and ensure that scheduled data workloads continue to execute regardless of who originally created or configured them.
You dont have to work on actual project, just guite what can be done is enough
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.