Deploying an ISV solution into the new PPAC hosted environment

(6) Share

Report

Posted on by GB-22111519-0

I'm sure some people in the world must be experiencing the same.

We are going through the build phase of our D365FO project and have spun up the normal test, uat, etc. environments in the PPAC (Power Platform Admin Centre)

LCS is being moved away from and users will be on PPAC long term. We are facing come challenges with this new world of PPAC and one of them is finding out how to do things.

The big issue we have at the moment is deploying an ISV for document printing. The ISV vendor is not on PPAC so struggling to work out how to do it. We have tickets with them, we have tickets with Microsoft. The ISV vendor has tickets with Microsoft. How do we get from the normally supplied ISV zip that would be deployed by LCS. Into the PPAC hosted environment without using LCS.

Just thought would put it out there to see if any one experiencing the same or similar challenges. Microsoft documentation is sparce to say the least and cant find any steps that will take us from A to B.

Posed here as couldn't find specific forum.

Categories:

Power Platform integration

I have the same question (5)

All responses (4)

Answers (0)

Sort by

Martin Dráb 239,118 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

What is inside the ZIP file you receive from the ISV?

Was this reply helpful? Yes No
GB-22111519-0 22 on at

Like (0)

Report
Copy link

Link copied!

Hi...

The zip file contains the content that would normally be deployed using LCS. We cant find any reliable detailed documentation on if this can be deployed to a PPAC environment which has not links to LCS at all and brief documentation on converting the ZIP to a new format but then no further documentation for the next steps.

Was this reply helpful? Yes No
Martin Dráb 239,118 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I guess you mean a deployable package; you can't use that for the Power Platform environment. Ideally, the ISV should give you the Unified Packages instead; generating it can be as simple as checking a single checkbox (Create Power Platform Unified Package) in their build pipeline. If not, you can convert it on your own by using ModelUtil.exe with -convertToUnifiedPackage flag.

The way of deployment I'm aware of is using Power Platform Deploy Package task in a release pipelines. It's shown in Unified developer experience for finance and operations apps > Continuous integration and deployment.

1 people found this reply helpful.

Was this reply helpful? Yes No
André Arnaud de Cal... 304,121 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
Hi,

You can use the next command to convert the deployable package to a unified package, but I think you already were able to perform this task.

In Powershell:
.\ModelUtil.exe -convertToUnifiedPackage -file="C:\Temp\[DeployablePackageFileName].zip" -outputpath="C:\Temp\Uni"

You can also use a Powershell script to install the package, but release pipelines as mentioned by Martin will be a better and more robust option.

Command 1: Open a connection to a UDE environment

pac auth create --environment https://[environmenturl].crm4.dynamics.com

Command 2: Deploy the package

pac package deploy --logConsole --package C:\Temp\UNI\TemplatePackage.dll

A great help for getting started with the new UDE environments is a blog from Aurelien Clere: Dynamics 365 FinOps Unified developer experience — PowerAzure365

1 people found this reply helpful.

Was this reply helpful? Yes No