Forum Discussion

ua77's avatar
ua77
Frequent Visitor
3 months ago
Solved

Org app with PPU license

We are trying to publish a new org app (https://learn.microsoft.com/en-us/power-bi/explore-reports/org-app-items) in a PPU workspace.

We are using Git integration and have created the new org app in a workspace connected to the DEV branch. This works fine; however, after merging to the main branch, we get an error when trying to update the PROD workspace:

Workload Error Code InsufficientCapacitySkuForGenericArtifacts

 

 

Is there any known limitation with org apps in PPU workspaces (or when using Git integration)?

Need Help
  • v-moharafi-msft's avatar
    v-moharafi-msft
    3 months ago

    Hi ua77 ,

     

    Thankyou for choosing Microsoft Fabric Community and thanks GilbertQ for sharing meaningful insights .

    Thanks for the clarification. Based on the behavior and the error.

     InsufficientCapacitySkuForGenericArtifacts, this appears to be a current limitation when using Org Apps with Git integration in PPU workspaces.

     

    According to the Microsoft documentation, Git integration requires a Fabric or supported Premium capacity context for supported items and deployment operations. While PPU provides Premium features for individual users, a PPU workspace is not fully equivalent to a dedicated Premium/Fabric capacity workspace for all CI/CD and Git-integrated scenarios.

    This explains why:

    • Creating the Org App directly in the DEV workspace works successfully.
    • Updating the PROD workspace through Git integration fails during deployment validation.

    At the moment, Org Apps appear to have limited support in Git-based deployment workflows when the target workspace is backed only by a PPU license instead of a dedicated Premium/Fabric capacity.

    As possible workarounds, you could consider:

    • Managing the Org App separately in the PROD workspace outside the Git deployment flow,
    • Moving the PROD workspace to a Premium/Fabric capacity,
    • Or excluding the Org App artifact from Git promotion until broader support becomes available.

    For more information, please refer to the following documentation:

    Best Regards,

    Abdul Rafi

5 Replies

  • GilbertQ's avatar
    GilbertQ
    Icon for Super User rankSuper User
    3 months ago

    Hi ua77 

     

    From my understanding this is a current limitation with the org apps in terms of using the git integration. What happens if you just try and create a new org app in your prod workspace? Does it then work?

    • ua77's avatar
      ua77
      Frequent Visitor
      3 months ago

      Hi,

      I assume that would work, but the problem is that our main branch is protected, so we can’t commit the changes. In that case, the org app will be overwritten every time there are new changes.

      • v-moharafi-msft's avatar
        v-moharafi-msft
        Icon for Community Support rankCommunity Support
        3 months ago

        Hi ua77 ,

         

        Thankyou for choosing Microsoft Fabric Community and thanks GilbertQ for sharing meaningful insights .

        Thanks for the clarification. Based on the behavior and the error.

         InsufficientCapacitySkuForGenericArtifacts, this appears to be a current limitation when using Org Apps with Git integration in PPU workspaces.

         

        According to the Microsoft documentation, Git integration requires a Fabric or supported Premium capacity context for supported items and deployment operations. While PPU provides Premium features for individual users, a PPU workspace is not fully equivalent to a dedicated Premium/Fabric capacity workspace for all CI/CD and Git-integrated scenarios.

        This explains why:

        • Creating the Org App directly in the DEV workspace works successfully.
        • Updating the PROD workspace through Git integration fails during deployment validation.

        At the moment, Org Apps appear to have limited support in Git-based deployment workflows when the target workspace is backed only by a PPU license instead of a dedicated Premium/Fabric capacity.

        As possible workarounds, you could consider:

        • Managing the Org App separately in the PROD workspace outside the Git deployment flow,
        • Moving the PROD workspace to a Premium/Fabric capacity,
        • Or excluding the Org App artifact from Git promotion until broader support becomes available.

        For more information, please refer to the following documentation:

        Best Regards,

        Abdul Rafi

  • v-moharafi-msft's avatar
    v-moharafi-msft
    Icon for Community Support rankCommunity Support
    3 months ago

    Hi ua77 ,


    Thank you for reaching out to Microsoft Fabric Community 


    Just wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. 

     

     Best Regards,

    Abdul Rafi.

  • v-moharafi-msft's avatar
    v-moharafi-msft
    Icon for Community Support rankCommunity Support
    3 months ago

    Hi  ua77  ,


    We wanted to check if your question has been resolved or if you are still facing any confusion feel free to reach out. Providing an update can be beneficial for others who might be experiencing similar challenges.

     

    Best Regards,

    Abdul Rafi