Unanswered

How to automate provisioning Power Apps portals Devops through azure devops?

(0) Share

Report

Posted on by SelCori

We are developing azure pipeline to replicate PowerApps environments. We have solution and portal app in our source environment. Using power devops extension, we are able to create and copy the source to new target environment through azure devops pipeline. However unable to provision the portal as part of the pipeline.

Please let us know the options to automate the provisioning of portals as we cannot manually create in every target environments.

Categories:

Power Apps portals

I have the same question (0)

All responses (5)

Answers (0)

oliver.rodrigues 9,368 Most Valuable Professional on at

Like (1)

Report

Hi @SelCori

Currently there is no way to automate those actions.

My understanding is that Microsoft has that in their roadmap, but would be still a way down the line.

------------
If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Was this reply helpful? Yes No
SelCori 7 on at

Like (0)

Report

@OliverRodrigues Thanks for the reply. For now we will keep that step manual after every pipeline run till copy environment is enhanced to include portal.

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (2)

Report

Hi @SelCori,
What is meant exactly by provisioning? If it's to create new instances of Power Apps portal, it's not yet possible as @OliverRodrigues mentioned, however if it's to automate the deployment of your portal configuration then yes you can automate that in Azure DevOps. I leverage the Microsoft.Xrm.DevOps.Data Powershell cmdlets to automatically export and generate my import files of all required portal configurations and then use ConfigurationMigration tooling to import to the destination environment...
Microsoft.Xrm.DevOps.Data : https://github.com/abvogel/Microsoft.Xrm.DevOps.Data
Microsoft.Xrm.Tooling.ConfigurationMigration: https://www.powershellgallery.com/packages/Microsoft.Xrm.Tooling.ConfigurationMigration/1.0.0.53

Was this reply helpful? Yes No
SelCori 7 on at

Like (0)

Report

@EricRegnierThanks for the reply. Yes to create new instance of Power Apps portal. My understanding is when we copy the entire environment we do not need to copy portal configuration as the entire CDS is copied. Whenever a solution is copied to target environment and when there is a change in portal, then we could use Microsoft.Xrm.DevOps.Data and Microsoft.Xrm.Tooling.ConfigurationMigration to deploy the portal configuration as you suggested.

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (1)

Report

Not quite... when you copy a CDS instance, yes the portal config is also copied but you still need to point the portal instance to the right environment so you'll need to set the portal settings to direct to the right CDS instance (https://docs.microsoft.com/en-us/powerapps/maker/portals/admin/change-dynamics-instance). Furthermore, full of other unwanted data is copied that you probably do not want to pollute your target environments.
I would recommend that you don't rely on copying instances to deployment portal config and settings. My recommendation would be rather, provision a blank vanilla portal instance per environment (dev, UAT, PROD, etc). Those are simple steps via make.powerapps.com. Ensure that your Dev environment is the source of truth for your portal config (actually suggest to pull from Dev into source control and have your source control the source of truth) and then deploy the latest and greatest config to the target environments via Azure DevOps with the tooling.

Was this reply helpful? Yes No