How to Uninstall LISA Enterprise from Microsoft Dynamics 365 Finance and Supply Chain Management

This article explains how to safely remove an LISA Enterprise solution from a Microsoft Dynamics 365 Finance and Supply Chain Management environment. The process uses a deployable package that instructs the system to remove the specified module during deployment.

Important: Before uninstalling LISA Enterprise solution, ensure that the module is no longer required and that any dependent customizations have been reviewed.

Uninstall Procedure

Step 1: Remove model references

1. Remove all references on other modules to the LISA Enterprise module (BFTLicensing).
2. If you have extension modules which only contain extensions for LISA Enterprise, then you would also need to uninstall these modules.
3. Verify that no other models or packages depend on the module.
4. Build and deploy any models that were updated to remove these references.
5. Verify that the module(s) are not included in the deployable package that will be used for the uninstall process.

NOTE: If you use a standard build pipeline connected to source control to generate the deployable packages, you will also need to remove the module(s) from source control and adjust the pipeline to not build these module(s).
If the pipeline adds the license files for LISA Enterprise to the package, make sure to also alter the pipeline to not do so, as otherwise deployment of the package would fail.

Step 2: Create the Module Removal File

Create a text file named:

ModuleToRemove.txt

Add the name of each module that should be removed, using one module name per line.

So if you only want to remove the LISA Enterprise module the text file should just contain:

BFTLicensing

However if you also have module(s) which only contain extensions for LISA Enterprise which you also want to remove, the file should contain the below.

LISAExtA
LISAExtB
BFTLicensing

NOTE: In the above example, “LISAExtA” and “LISAExtB” are examples of modules containing LISA extensions which we also want to remove. The name of these module(s) will be different based on how the extension module(s) were named in your scenario.

Step 3: Prepare the Deployable Package

Create a valid deployable package

Copy the ModuleToRemove.txt file into the [packageName.zip]\AOSService\Scripts folder within your deployable package.

Once added, verify that the package structure is correct before continuing.

NOTE: If you use a standard build pipeline, you can generate the package via the pipeline regularly but then take the package from the pipeline and manually add the ModuleToRevomve.txt file in the correct folder.
If you use a release pipeline, for this specific package you would not be able to use it and must manually deploy the package via LCS

Step 4: Upload the Package to LCS

1. Open your Lifecycle Services (LCS) project.
2. Navigate to Asset Library.
3. Upload the updated deployable package.
4. Wait for package validation to complete.
5. Review any warnings or validation messages before proceeding.

Step 5: Deploy the Package

Install the deployable package using the standard deployment process to your Sandbox/UAT environment.

Step 6: Verify Module Removal

After deployment:

1. Log in to Dynamics 365 Finance and Supply Chain Management.
2. Verify that the module Enterprise Subscription Automation or Enterprise Automation is no longer available from the side menu.
3. Confirm that no menu items, security roles, or integrations related to the module remain active.
4. Perform validation testing before applying the same process to production environments.

Expected Outcome

Upon successful deployment, all LISA Enterprise and TAPP functionality will be removed from the environment and will no longer be available to users within Dynamics 365 Finance and Supply Chain Management.

References

Microsoft documentation on removing a module: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/uninstall-deployable-package