ISV solution upgrade

(1) Share

Report

Posted on by CU29041349-0

626

Hello,

We have an upgraded ISV solution package in LCS which we'd like to review in our sandbox. I'm looking for documentation to help initially deploy this upgrade (binary) to sandbox but also would like to see steps to move it to production if the time comes.

I have the same question (0)

All responses (3)

Answers (2)

Sort by

Verified answer

Anton Venter 20,694 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

Please have a look this article, it explains a bit how deployments are handled.

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/aio-deployable-packages

Was this reply helpful? Yes No
Verified answer

Anthony Blake 3,154 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi

To be applied to a sandbox, and eventually production, you will need to make the ISV package a part of you single deployable package. There are a few ways to do this, the most common is probably still to add the binaries to source control, and use Azure DevOps build pipelines to create the single package.

Read about the process here: All-in-one deployable packages - Finance & Operations | Dynamics 365 | Microsoft Learn

.and about the source control process here: Manage third-party models and runtime packages by using source control - Finance & Operations | Dynamics 365 | Microsoft Learn

Was this reply helpful? Yes No
Suggested answer

Assisted by AI

CU27011421-0 on at

Like (0)

Report
Copy link

Link copied!
For an upgraded ISV solution delivered as a deployable package (binary), the process is handled through LCS, not manual installation.

Sandbox deployment

In LCS, go to Asset library and confirm the ISV deployable package is uploaded.

Navigate to the sandbox environment.

Use Maintain > Apply updates to deploy the ISV package.

Monitor the deployment and validate functionality after completion.

Production deployment

Deployment to production cannot be done manually.

The ISV package must be:

Approved and linked to the project in LCS

Deployed through Microsoft-managed servicing

This is done by scheduling the update in LCS, and Microsoft applies it during the maintenance window

Important notes

Always validate thoroughly in sandbox before requesting production deployment.

Check ISV documentation for any post-deployment steps (data upgrade scripts, feature toggles).

If the ISV includes schema changes, ensure database sync is completed as part of the process

Microsoft documentation to reference:

Deploy updates to environments using LCS

Deployable packages in Dynamics 365 Finance & Operations

Was this reply helpful? Yes No