Forum Discussion
Need suggestions to run our production data pipelines
In our Dev environment, we currently use user-based authentication to run data pipelines in Fabric for Bronze, Silver and Gold. However, for the production environment, we are exploring best practices that do not involve service accounts. Can someone advise the best method/or available options to securely run data pipelines in production?
For production pipelines in Fabric, the best practice is to use managed identities or workspace-managed credentials instead of user-based authentication. This avoids dependency on personal accounts or service accounts. Here are your secure options:
- Workspace-managed identity: Fabric can use a system-assigned identity to authenticate securely with data sources (like Azure SQL, Data Lake, etc.).
- Linked services with credential store: Set up linked services using secure credential management and reuse them in pipelines and dataflows.
- Access control via Azure AD: Ensure all resources grant access to the Fabric workspace identity, not individual users.
This setup improves security, avoids credential expiration issues, and supports automation in production.
5 Replies
- AnonymousNot applicable
Hi ati_puri ,
Thank you for reaching out to us on Microsoft Fabric Community Forum!To securely run pipelines in production without user credentials or traditional service accounts, Microsoft recommends using Workspace Identity. Please refer the below links for more information.
https://learn.microsoft.com/en-us/fabric/security/workspace-identity-authenticate
Also refer the solved thread which might help you :
https://community.fabric.microsoft.com/t5/Data-Engineering/Connecting-to-Fabric-database-using-workspace-identity/m-p/4414936
Hope this answer help you to resolve the query.If so,give us kudos and consider accepting it as solution.
Regards,
Pallavi G. - BhavinVyas3003
Super User
Hi ati_puri
Use Managed Identity instead of user or service accounts.
- Enable Managed Identity in your production Fabric workspace (via Admin portal).
- Grant access to required data sources (e.g., Azure Data Lake, SQL) using RBAC or ACLs.
- Configure pipelines to use the workspace’s Managed Identity for authentication.
- ati_puri
Resolver III
Managed Identity is not supported with Azure Devops to trigger data pipelines
- Ilgar_Zarbali
Super User
For production pipelines in Fabric, the best practice is to use managed identities or workspace-managed credentials instead of user-based authentication. This avoids dependency on personal accounts or service accounts. Here are your secure options:
- Workspace-managed identity: Fabric can use a system-assigned identity to authenticate securely with data sources (like Azure SQL, Data Lake, etc.).
- Linked services with credential store: Set up linked services using secure credential management and reuse them in pipelines and dataflows.
- Access control via Azure AD: Ensure all resources grant access to the Fabric workspace identity, not individual users.
This setup improves security, avoids credential expiration issues, and supports automation in production.
- ati_puri
Resolver III
Can we use WS Identity in Azure Devops to trigger our data pipelines schedules or triggers?