ADO to Workspace blocker

[GovContractor89]

I’m currently facing a challenge with integrating my Power BI project files into our workspace and would appreciate any guidance or suggestions you might have.

Here’s a bit of context:
My team is managing source control by saving Power BI files as project files, and we are using an Azure DevOps (ADO) instance to store all our code in the repository. Our goal is to connect ADO to our workspace for automating the deployment of updates to the code files.

However, I’ve encountered a roadblock as the feature to connect ADO to the workspace seems unavailable within our current GCC contract. I was wondering if you could offer any insight into potential workarounds or solutions that would allow us to achieve this integration despite the limitation?

Any advice or suggestions would be highly appreciated.

Thank you for your time and assistance!

[Anonymous]

Hi @GovContractor89 ,
Thank you @pborah for the accurate response.

I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped or share your solution and accept it as solution. It would be greatly appreciated by others in the community who may have the same question.

Thank you for being a valued member of the Microsoft Fabric Community Forum!

[pborah · Accepted solution]

If you're talking about the git integration feature (which has the option to sync with ADO) then there is no workaround if your GCC doesn't support it. 

That being said you can still keep your project files in ADO just without the PowerBI sync feature. It will have to be manual either using git GUI or CLI. We used to do that before the feature became available in PowerBI service. It all comes down to establishing a protocol and following it religiously.