Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
rxt
Frequent Visitor

mapping multiple folders in a devops repos with multiple powerBI get integration

I am able to map multiple folders in a devops repos with multiple PowerBI get Integration se picture below

rxt_0-1704832874867.png

 

Our dilemma revolves around configuring repository in DevOps in such a manner that individual/group within a PowerBI workspace 'salesforceDev' can access the DevOps folder 'salesforce'  and individuals/group within a PowerBI workspace 'OneView Github Test' only access DevOps folder 'Oneview' within a CSG-DS-PBI repository. In other word, does devops Repository allows folder level permissions ? or is there another alternative idea ? the closest solution I see would be creating multiple repositories for mutlple workspaces ? https://www.kevinrchant.com/2023/08/30/working-with-microsoft-fabric-git-integration-and-multiple-wo...

I would appriciate someone insight.

Thanks

RT

1 ACCEPTED SOLUTION
rxt
Frequent Visitor

Many thanks Team_Caitlyn for such a detail response, really appriciate it.

View solution in original post

2 REPLIES 2
rxt
Frequent Visitor

Many thanks Team_Caitlyn for such a detail response, really appriciate it.

v-xiaoyan-msft
Community Support
Community Support

Hi @rxt ,

 

You grant or restrict access to repositories to lock down who can contribute to your source code and manage other features. You can set permissions across all Git repositories by making changes to the top-level Git repositories entry. Individual repositories inherit permissions from the top-level Git Repositories entry.Permissions are typically set at the repository level rather than at the folder level.

You can give permissions to specific branches in a repository. Each team could work on a separate branch that corresponds to their workspace. Or You could create separate repositories for each workspace. This way, you can manage permissions at the repository level, which is more straightforward in Azure DevOps.

If you’re using Git, consider using submodules and restricting access to referenced repositories.

You may also restrict access to work items and features based on Area Paths.

 

For more details:

Get started with permissions, access levels, and security groups - Azure DevOps | Microsoft Learn

permissions - How to manage Azure DevOps security on level deeper than Project level? - Stack Overfl...

azure devops - One or multiple git repositories for independent small parts of one larger project? -...

azure devops - Setting permissions on branch folders rather than specific branches - Stack Overflow

Set Git repository permissions - Azure Repos | Microsoft Learn

 

 

Best regards.
Community Support Team_Caitlyn

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

Jan NL Carousel

Fabric Community Update - January 2025

Find out what's new and trending in the Fabric community.