Forum Discussion
Microsoft EmployeeBranch Strategy and DevOps with current role limitations
Hi everyone,
I'm currently figuring out how to implement a simple branch strategy where each project developer is either a workspace member or contributor.
With these roles, developers are currently unable to create new branches.
The workspace admin role is too elevated for regular project developers.
An alternative that someone proposed was to pre-create a workspace for every project member so they can create branches on their own, but this strategy seems to have scalability issues.
Can someone share their experiences with me?
Hi hernandezpaulms ,
Yeah, I’ve run into this same issue before. The current role setup can be a bit limiting when it comes to branching. One thing we tried was having a small group of trusted devs with elevated roles who could help manage branches for others — kind of like branch gatekeepers. Not perfect, but it helped avoid giving full admin access to everyone.
Pre-creating workspaces for each dev sounds like a nightmare to scale, especially if your team grows or changes often. Another idea might be to use automation (like pipelines or scripts) to handle branch creation based on requests — keeps things controlled but still flexible.
Curious to hear what others are doing too!
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
3 Replies
- burakkaragoz
Super User
Hi hernandezpaulms ,
Yeah, I’ve run into this same issue before. The current role setup can be a bit limiting when it comes to branching. One thing we tried was having a small group of trusted devs with elevated roles who could help manage branches for others — kind of like branch gatekeepers. Not perfect, but it helped avoid giving full admin access to everyone.
Pre-creating workspaces for each dev sounds like a nightmare to scale, especially if your team grows or changes often. Another idea might be to use automation (like pipelines or scripts) to handle branch creation based on requests — keeps things controlled but still flexible.
Curious to hear what others are doing too!
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
KevinChantSure, at this moment in time devloping individual workspaces for the developers works in enterprises where they don't want developers to create their own workspaces.
However, it can be an issue if the developers are working on multiple projects at the same time. So you have to make a judgement call on the best approach.
v-karpurapudCommunity Support
Could you please confirm if your query have been resolved the solution provided by burakkaragoz and KevinChant ? If they have, kindly mark the helpful response and accept it as the solution. This will assist other community members in resolving similar issues more efficiently.
Thank you