Forum Discussion

db042190's avatar
db042190
Impactful Individual
17 days ago

this error seems to interfere with version control and deploy pipelines

I'm not sure why we built our pipelines under fabric instead of vanilla pbi, but it seems to us that changes in the ws's tied to pipelines cause this error to show (sometimes) when we are trying to make wor space settings relatyed to pipelines and version control.   the error seems to disappear (we think) a day later too.   does anybody know what this is all about?

 

Need Help

5 Replies

  • GilbertQ's avatar
    GilbertQ
    Super User
    17 days ago

    Hi db042190 

     

    What do you see when you click on the workspace tab? It should be either. Power BI premium per user or a fabric capacity.

    • db042190's avatar
      db042190
      Impactful Individual
      17 days ago

      we know the ws's being acted on by the pipeline are fabric which ive told my peers was unnecessary.  i cant imagine a reason for doing that unless we had fabric sms and we dont have those yet.   

       

      supposedly we could accomplish the same end goal by leaving them (dev,test and prod ws's) non fabric.    i have to admit i dont know if pipelines are even categorized as fabric or not.   

  • tayloramy's avatar
    tayloramy
    Super User
    17 days ago

    HI db042190, 

     

    Deployment Pipelines are a Fabric feature, there is no way to use them unless you have a fabric capacity backing the workspaces. 

    https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/get-started-with-deployment-pipelines?tabs=from-fabric%2Cnew-ui

     

    That error message is indicating that your workspace is not backed by a capacity, but rather is a pro workspace. TO use deployment pipelines, you will need to assign the workspace to a fabric/premium capacity as GilbertQ mentioned.  

  • v-sathmakuri's avatar
    v-sathmakuri
    Community Support
    7 days ago

    Hi db042190​ ,

    Could you check the suggestion provided above and let us know if you have any additional queries?

    Thanks!!

  • ShivekMaharaj's avatar
    ShivekMaharaj
    Impactful Individual
    13 days ago

    Hi db042190​,

    I think there are two slightly different things getting mixed together here: Fabric Git integration and the broader question of how you deploy Power BI content.

    The warning in your screenshot is coming from Git integration. Microsoft's current Git integration prerequisites require the workspace to be on Fabric capacity, so an ordinary Power BI Pro/shared-capacity workspace can't continue using that native Git connection.

    That doesn't necessarily mean you now need to move all of Dev, Test and Prod onto Fabric just because you want source control and CI/CD for Power BI.

    Microsoft also documents an alternative where Azure DevOps/Azure Pipelines deploy Power BI content directly using source files and the Power BI REST APIs. In its content lifecycle guidance, Microsoft specifically notes that this approach doesn't require Fabric/Premium capacity when you're publishing only Power BI Desktop files through the Power BI REST APIs.

    So I would frame the choices as:

    • Fabric-native Git + deployment experience: use eligible capacity-backed workspaces
    • Keep Power BI workspaces on shared/Pro capacity: manage source control in Azure DevOps/Git and deploy through Azure Pipelines/Power BI APIs instead


    The built-in Fabric experience is certainly simpler, but it isn't the only way to maintain separate Dev/Test/Prod environments for Power BI.

    Also, the wording “Premium license” in the Git warning is a little broader than the current documentation. For Fabric Git integration, I would check the actual Workspace type/capacity assignment rather than the individual user's Pro license.

    AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.