User Profile

ifeanyi

Frequent Visitor

Joined 1 year ago

9 Posts4 LikesLikes received

View All Badges

User Widgets

Contributions

Re: User with Contributor Role Unable to Checkout Branches or Create New Workspaces
Hi hernandezpaulms , Thank you for raising these important considerations. You're absolutely right — there is a potential maintenance challenge when managing multiple workspaces, especially when developers are contributing across several projects. The intention behind our current approach is to allow contributors to branch out from the collaborative workspace, where all users have admin rights. This enables them to create their own isolated workspaces without affecting the main dev branch. That said, we're still in the experimental phase and are hopeful that the native Git integration in Microsoft Fabric will soon evolve to better support the necessary functionality for contributor roles. In parallel, we're also exploring an alternative approach where, as an admin of the main dev branch, I create dedicated branches for individual contributors (e.g., feature-x, feature-y, feature-z). Each contributor can then link their personal workspace to their respective feature branch, work independently, and later merge their changes back into the dev branch in a more controlled manner. Hope this was helpful — I’d be keen to hear how others are approaching this as well.
1 year ago Place Data Engineering
3.3KViews
0likes
0Comments
Re: User with Contributor Role Unable to Checkout Branches or Create New Workspaces
You're absolutely right—this limitation can be quite frustrating, especially when trying to maintain a least-privilege access model. It's not as straightforward as it is in Synapse or Data Factory. To work around this, we’ve adopted a mitigation strategy by introducing an intermediary collaboration workspace. Here's how we approach it: We start with a primary workspace, for example, contoso_wsp[Dev]. As an admin, I create a secondary workspace named contoso_collaboration_wsp. I then assign contributor users as admins to this collaboration workspace—not to the original one. This setup gives them the permissions needed to create their own development branches or workspaces (e.g., contoso_collaboration_wsp_contributor1, contoso_collaboration_wsp_contributor2, etc.). Once their work is complete, I review and merge changes from these contributor workspaces back into the main contoso_wsp [Dev]. While it’s a bit of an overhead and certainly not ideal, this structure helps us maintain control over the dev environment while enabling contributor-level users to work independently. That said, I’d be keen to hear how others are overcoming this challenge and whether there are any updates on how Microsoft Fabric plans to mature its support for DevOps/DataOps and CI/CD workflows.
1 year ago Place Data Engineering
3.6KViews
1like
3Comments
Re: User with Contributor Role Unable to Checkout Branches or Create New Workspaces
Hi v-aatheeque , Thanks for following up. Anonymous response provided useful insights. However, some other user have also reported experiencing similar issues, indicating a gap between expected functionality and actual implementation. This concern needs to be raised with the Microsoft Fabric team for further clarification. You can also check out this discussion: https://www.skool.com/microsoft-fabric/new-video-3-of-the-dp-700-series-just-launched-on-cicd?p=0d0d466b
1 year ago Place Data Engineering
4.2KViews
0likes
1Comment
Re: User with Contributor Role Unable to Checkout Branches or Create New Workspaces
Thank you for sharing the link to the Microsoft documentation. I have reviewed the resource, and it confirms that workspace roles such as Admin, Member, and Contributor should have the ability to "Branch out to new workspace." Current Setup: As the Fabric Admin, I have enabled the organization-wide setting to allow workspace creation for all users. Issue Observed: Users with the Contributor role do not have access to the "Branch out to new workspace" option (it remains disabled). When I upgrade the user’s role to Member, the option becomes enabled, but attempting to use it results in an error. The feature functions only when the user is assigned the Admin role, which is not ideal from a security and governance perspective. Request for Further Assistance: Are there additional prerequisites or configurations required beyond the documented settings? Could this be a potential issue with role-based permissions or a system limitation? I would appreciate any further insights or troubleshooting steps to resolve this discrepancy. Thank you in advance for your support!
1 year ago Place Data Engineering
4.3KViews
0likes
4Comments
Re: User with Contributor Role Unable to Checkout Branches or Create New Workspaces
I am the administrator of a Microsoft Fabric workspace connected to an Azure DevOps repository, and I have encountered an issue with user permissions. Specifically, when adding a user with Contributor access, they are unable to perform the following actions: Check out a branch Create a new branch from the workspace These options remain disabled for the user, as shown in the attached image. However, when I update their role to Member, the options become enabled, allowing them to create a branch. Unfortunately, an error occurs during the process (details in the attached image). When I further upgrade their role to Admin, they can successfully check out and create a new branch without any issues. I want to adhere to the principle of least privilege, meaning I do not want users to have Admin access unless absolutely necessary. Ideally, I would like them to perform these actions as Contributors. Could you please confirm whether this is expected behavior or if there is a configuration setting that needs adjustment? Your guidance on resolving this would be greatly appreciated. Thank you in advance for your support!
1 year ago Place Data Engineering
4.3KViews
0likes
0Comments
Re: User with Contributor Role Unable to Checkout Branches or Create New Workspaces
Hi nilendraFabric , Thank you for the detailed explanation. To clarify, I have already assigned the user the Contributor role in the workspace and granted them Project Contributor access to the project from the Azure DevOps Git repository. I assumed that (Read=Allow) and (Contribute=Allow) permissions would be applied automatically, as this was the case in previous setups where users with the Contributor role in the workspace could perform Git operations without additional configuration. However, I reviewed the Azure DevOps Git repository settings under Project Settings --> Permissions --> Contributors and did not find the explicit (Read=Allow) option as described in the image below. Could you please confirm if these permissions are managed elsewhere or if there’s an additional step I might be missing? Thank you for your support!
1 year ago Place Data Engineering
4.3KViews
0likes
2Comments
Re: User with Contributor Role Unable to Checkout Branches or Create New Workspaces
Hi nilendraFabric , Thank you for your response. I understand that Contributors have limited permissions compared to Members and Admins. However, the Microsoft Fabric Git integration documentation suggests Contributors should be able to checkout branches and create workspaces as part of the Git workflow. Could there be additional settings or restrictions causing this, or is the documentation outdated? I’d appreciate further clarification. Thanks again!
1 year ago Place Data Engineering
4.4KViews
1like
4Comments
User with Contributor Role Unable to Checkout Branches or Create New Workspaces
I recently created a Microsoft Fabric workspace and added a user with the Contributor role. The workspace is connected to an Azure DevOps repository. However, we noticed that the user is unable to perform certain actions, specifically: Checkout a branch Branch out to a new workspace These options remain disabled for the user as shown in the image below. Interestingly, when I change the user’s role from Contributor to Admin, the options become available, and the user can perform the actions without any issues. Has anyone encountered a similar situation? Is this expected behavior for the Contributor role, or could there be a configuration issue? Additionally, could the integration with the Azure DevOps repository be impacting these permissions? Any insights or suggestions would be greatly appreciated. Thank you in advance!
Solved
1 year ago Place Data Engineering
Data Engineering
4.4KViews
2likes
19Comments
Inconsistent Execution Times in Microsoft Fabric Pipeline
Hello everyone, I’m currently using the Microsoft Fabric Free Trial and have been encountering an issue with a pipeline I developed for ingesting data from a web server. The pipeline intermittently experiences significant delays during execution. In most cases, the majority of the tasks within a "For Each" loop execute in less than 30 minutes. However, at random intervals, one of the notebook calls will take an excessive amount of time to complete—sometimes exceeding 4 hours. For example, as shown in the attached image, the pipeline was stuck on a single notebook execution for over 4 hours, even though the notebook successfully connected to the server and ingested the data. The pipeline seemed to be hanging at that same step, despite the data ingestion being complete. I eventually had to cancel the run after waiting for a long period. What makes this even more perplexing is that the issue occurs randomly. At times, the pipeline runs efficiently, while other times it drags significantly. Has anyone else encountered similar issues with Microsoft Fabric pipelines, particularly inconsistent or prolonged execution times? I’d appreciate any advice or troubleshooting tips that might help resolve this erratic behaviour. Thanks in advance for your help!
Solved
1 year ago Place Data Engineering
Data Engineering
Data Pipeline
Notebook
4.8KViews
0likes
6Comments

Data Privacy

Microsoft Fabric Community and Privacy

To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.