Forum Discussion
How to deploy OrgApp and OrgAppAudience from one workspace to another workspace using GitHub Actions
Hi Team - I was looking to achieve the CI/CD for OrgApp and OrgAppAudience. I have a workspace-Dev which is Git Integrated and has the OrgApp and OrgAppAudience in below structure format.
Sales Results.OrgApp
├── .platform
├── definition
└── .children
└── Sales Results.OrgAppAudience
├── .platform
└── definition
I'm trying with to achieve this deployment automation with GitHub actions. Steps performed are
1. Install fabric-cli
2. Login using Managed Identoty to fabric CLI
3. Deploy using fab deploy with config file with Items in scope as "OrgApp" and "OrgAppAudience"
Observation Error - It looks the Fabcric CLI does not support this type of deployment. Please let me know the possibilities to achieve this deployment using GitHub actions only.
FAQ on the Fabric User Groups
As we have the gap (the usage of Managed Identity for updating OrgApp and OrgAppAudience is not supported), we moved in creating the OrgApp and OrgAppAudience manually in target workspaces.
Thank you for sharing the required information and hoping to see this [FEATURE] Reintroduce org apps · Issue #1026 · microsoft/fabric-cicd as closed in the near future
11 Replies
As we have the gap (the usage of Managed Identity for updating OrgApp and OrgAppAudience is not supported), we moved in creating the OrgApp and OrgAppAudience manually in target workspaces.
Thank you for sharing the required information and hoping to see this [FEATURE] Reintroduce org apps · Issue #1026 · microsoft/fabric-cicd as closed in the near future
v-saisrao-msftCommunity Support
Hi mohan072,
Thanks for the update. It’s good to hear that you found a workable path by creating the OrgApp and OrgAppAudience manually in the target workspaces. Thank you as well for sharing the fabric-cicd issue hopefully OrgApp support is reintroduced in a future release.
Thank you.
- v-saisrao-msft
Hi mohan072,
Consider keeping the documented .children structure for OrgAppAudience and using fabric-cicd for the Git-based CI/CD workflow, as Microsoft documents fabric-cicd for complex multi-workspace and Git-based Org App deployments. Also, ensure the OrgApp uses definition version 2.0.0 and that the OrgApp and audience definitions follow the documented Git structure. If fab deploy is still failing, review the exact error and deployment configuration before concluding that OrgAppAudience isn't supported.
CI/CD for org apps in Fabric - Power BI | Microsoft Learn
Plan CI/CD for Microsoft Fabric Solutions - Microsoft Fabric | Microsoft Learn
Items - Create Org App Audience - REST API (OrgAppAudience) | Microsoft Learn
Thank you.
Hi v-saisrao-msft,
I did check, captured the error and posted in this forum to get other possible solutions to keep this working. I recommend you to share if you have achieved the OrgApp deployments through CLI. Check this below error which clearly indicates that it has no such option to support the OrgApp deployments.- Invalid item type 'OrgApp'. Available types: ApacheAirflowJob, CopyJob, DataAgent, DataBuildToolJob, DataPipeline, Dataflow, Environment, Eventhouse, Eventstream, GraphQLApi, KQLDashboard, KQLDatabase, KQLQueryset, Lakehouse, MLExperiment, Map, MirroredDatabase, MountedDataFactory, Notebook, Ontology, PaginatedReport, Reflex, Report, SQLDatabase, SemanticModel, SparkJobDefinition, UserDataFunction, VariableLibrary, Warehouse
- Invalid item type 'OrgAppAudience'. Available types: ApacheAirflowJob, CopyJob, DataAgent, DataBuildToolJob, DataPipeline, Dataflow, Environment, Eventhouse, Eventstream, GraphQLApi, KQLDashboard, KQLDatabase, KQLQueryset, Lakehouse, MLExperiment, Map, MirroredDatabase, MountedDataFactory, Notebook, Ontology, PaginatedReport, Reflex, Report, SQLDatabase, SemanticModel, SparkJobDefinition, UserDataFunction, VariableLibrary, Warehouse
The document says may be REST API's support if we use user Identity (Though it is not consistent). Why would I use user Identity approach in CI/CD automated workflows instead of Managed Identity ?
I appreciate you for sharing the links (REST API though), however those clearly indicates to create the OrgAppAudience and at the moment i'm not looking to create it and my intention is to deploy the existing OrgApp from workspace to another workspace.
Let me know your thoughts.- v-saisrao-msft
Hi mohan072,
Have you had a chance to review the solution shared by ShivekMaharaj? If the issue persists, feel free to reply so we can help further.
Thank you.
- v-saisrao-msft
Hi mohan072,
Checking in to see if your issue has been resolved. let us know if you still need any assistance.
Thank you. - ShivekMaharaj
Memorable Member
Hi mohan072,
Your Invalid item type 'OrgApp' result looks valid. I don't think this is just a configuration issue on your side.
The fabric-cicd project previously removed OrgApp support, and there is still an open request to reintroduce Org Apps. That seems to conflict with the newer Org App CI/CD documentation, which currently says fabric-cicd can consume Org App definitions.
I also don't think you should need to switch to an interactive user identity just because this is CI/CD.
The current OrgApp REST APIs and OrgAppAudience REST APIs explicitly list service principals and managed identities as supported identities, including the definition create/update operations.
There is a separate limitation documented for Fabric deployment pipelines, where Org Apps can't currently be deployed across stages using a service principal. I wouldn't apply that limitation to the dedicated REST APIs, since Microsoft documents SP/managed identity support there.
So for a non-interactive GitHub Actions deployment today, I would probably bypass fabric-cicd for these two artifacts and call the OrgApp/OrgAppAudience REST APIs directly. The Org App source-control format already gives you the OrgApp definition plus the .children audience definitions, and the audience parentAppId is tied to the parent Org App logical ID.
I'd deploy the referenced workspace content first, then the OrgApp, then its audience definition(s).
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
Yes we could use REST API's that supports creation of Org App, but I could not find the REST API to just update the existing OrgApp. Does this supports in deploying the OrgApp and OrgAppAudience ?
- v-saisrao-msft
Hi mohan072,
Microsoft has REST APIs available for updating existing OrgApp and OrgAppAudience definitions. Both APIs also list service principals and managed identities as supported identities.
Items - Update Org App Definition - REST API (OrgApp) | Microsoft Learn
Items - Update Org App Audience Definition - REST API (OrgAppAudience) | Microsoft LearnThank you.
