Version control

[mjoseph111]

Our organization operates under a Microsoft P1 license, without access to Fabric. Git integration is limited within our P1-backed workspace, Editing is fine, but version controlling and real collaboration is limited with P1 access. Any thoughts on how effectivily can use the pbip file ?
or the best strategies to enhance version control and enable real collaboration among developers in different department. What options are available to us?
Thank you in advance.

[v-venuppu]

Hi @mjoseph111 ,

I hope the information provided by Tutu_in_YYC is helpful.If this answers your question, please accept it as a solution,so other community members with similar problems can find a solution faster.

Thank you.

[v-venuppu]

Hi @mjoseph111 ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[mjoseph111]

Sure, I haven’t found a solution yet and am still working on it. I’ll mark it as resolved once it’s done

[v-venuppu]

Hi @mjoseph111 ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @Tutu_in_YYC @Greg_Deckler for the prompt response.

I wanted to check if you had the opportunity to review the information provided. If the responses has addressed your query, please accept it as a solution, so other members can easily find it.

Thank you.

[Tutu_in_YYC]

Can you elaborate what "collaboration among developers in different department" in your use case?

As far as i know, P1 doesnt limit collaboration. You can still use azure devops, branching etc. and leverage pbip and version control in git repo. What are the limitations that you are encountering?

Also, sooner or later you will need to move to F-sku, as P-sku is not being offered anymore. Once your current P sku contract ends, you can only continue on F sku.

[mjoseph111]

Do you have a guide or documentation I can follow? I haven't used Azure DevOps or branching before, but I'm interested in trying it out.

"collaboration among developers in different department" means , We need to collaborate with developers from different departments located in various regions.

[Tutu_in_YYC · Accepted solution]

Are they going to be working on the same semantic model? or they will be creating their own reports and semantic model? The approach will be different. However, here is a good place to start.

https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started?tabs=azure-devops%2CAz...

[mjoseph111]

@Tutu_in_YYC  We are working on the same semantic model. THanks for the document,but  this document is for fabric users. Our organization operates under a Microsoft P1 license, without access to Fabric. And we dont have the workspace setting option to continue. 

[Greg_Deckler]

@mjoseph111 You could leverage OneDrive. It has built in version control. I've seen people save their PBIX files as templates, PBIT and store those in OneDrive to do basic version control. Also, check out this video: