You’re offline. This is a read only version of the page.
Hello everyone!
I don't have experience with PowerApps in GCC/GCCH tenant, but tasked with creating a GCCH environment lab in a commercial tenant.
Basically, my client has a PowerApps in GCCH tenant and would like to develop apps in the commercial tenant, then migrate it to the GCCH tenant. To ensure the process of importing to GCCH tenant, I need to setup a "GCCH Lab" environment in commercial tenant providing highest compatibility and compliances as GCCH tenant, but I have no idea what that entails and I do not have access to a GCCH tenant to try it out.
Does anyone have any experience or information on the subject? Is it even possible? Any replies would be appreciated, including "not possible".
As stated, GCC High is not in Azure Commercial and is also not on the same schedule and there is not a guaranteed feature parity between the two environments, to include security features. They are at different states in build and even if a button is displayed in GCC high....it doesn't mean that it works. We refer to them as 'ghost buttons' (These are reported in and usually fixed or addressed shortly).
While the Microsoft employees do their best to update documentation, documentation isn't a guarantee for accuracy in what features are available and which ones are not.
From what I was told by a Microsoft Partner, is there is no way to import Commercial PowerApps to GCC high. However....there is a migration tool the Microsoft Partner used called, AvePoint Fly...I believe.
Migrating PowerApps went really well. I had prior experience with GCC high and understood to avoid using any 3rd party connectors or features in any built solutions. If I had used 3rd party connectors or features, the app would not have migrated well.
Approvals also do not work the exact same way in GCC high. You don't have dynamic email changes. When an Approval is sent using the Approval Connector, you receive an email with a button, however, that will take to you the Power Automate Approval page. From there you select your response and "Confirm".
You also won't be able to track certain properties of the approval. Ex: if you selected "Everyone must approve", you can't actually view who has or has not responded like you can in commercial.
The Approvals tab is also not available in Teams in GCC High.
Not related to Power Apps, but one seemingly small yet impactful difference we ran into, was the fact that MS Forms does not have the ability to send to external users in GCC high. You also can't migrate forms. You have to rebuild them.
So, re-solutioning flows around forms sending to external users, was a challenge.
These are just a few instances....and they change as updates/improvements are pushed to production. Best bet would be to either prototype in GCC High or check out a migration tool like Avepoint (Transform Power Platform Business Solutions | AvePoint)
Besides what Derek indicated, the other fundamental difference between commercial and GCC-High is that GCC-High uses Azure Government, not Azure Commercial. If you are leveraging any Azure services, be sure to confirm their availability in Azure Government.
There maybe a difference between commercial and GCCH the connectors available. You can view what connectors are available from the following link - List of all Power Apps connectors | Microsoft Learn.
You can also review some of the difference between clouds at - Product Availability by Geography | Dynamics 365 (microsoft.com)
We also have a feature parity document. https://aka.ms/BAPFunctionalParity
Share
Report
7
All responses (
Answers (
