LCS Implementation Project Migration - Locus IT Services

LCS Implementation Project Migration

Locus IT ServicesMicrosoft Life Cycle ServicesLCS Implementation Project Migration
Posted by Akshay | , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,  |

LCS Implementation Project Migration

You can move your subscriptions and your Microsoft Dynamics (Life Cycle Services) LCS Implementation project to a different Microsoft Azure Active Directory tenant. For any new Microsoft Dynamics for Finance and Operations project, one Microsoft Dynamics Life Cycle Services (LCS) Implementation project is instantiated on a Microsoft Azure Active Directory tenant that provides access to one production instance.

In some cases, to handle the requirements of a specific implementation, you might require multiple production instances that run in parallel. By creating multiple MS Dynamics LCS projects against the same Azure AD tenant, you can have multiple production instances. Here are some of the most common scenarios where multiple production instances might be required:

  • A global implementation’s requirements for the data residency, latency, or data volume can’t be met by one instance.
  • Different business units in an organization are implementing the Finance and Operations separately as independent applications.

Every LCS Implementation project that runs on the same Azure AD tenant should satisfy the minimum licensing requirements. Because the licenses are associated with the Azure AD tenant, the Subscriptions available page for every MS Dynamics LCS project will show the total number of licenses, even though a given LCS project can use only the portion of the licenses that has been allocated to it. This allocation of license to the LCS projects must be documented outside the system.

Activate the Subscriptions for LCS Implementation Project

All subscriptions for the users, and for add-on environments, must be activated.

  • Cloud service provider

If licensed through a Microsoft Cloud Solution Provider (CSP) agreement, purchase the required subscriptions against the new tenant from your cloud service provider. If the new tenant is already present, the cloud service provider must request a reseller relationship.

  • Volume Licensing

If licensed through a Microsoft Volume Licensing agreement, you must call the Volume Licensing support center and ask that the subscriptions be remapped from the old tenant to the new tenant.

Configure LCS on the New Tenant for LCS Implementation Project

On the new tenant, you will get a new MS Dynamics LCS project that you must initiate and set up.

  • Fully configure LCS. As part of this configuration, you must add the users, a Microsoft Azure DevOps association, subscription estimates, the Asset library, Business process modeler (BPM), and so on.
  • Deploy all the non-production environments in the new LCS project.
  • Apply the required code packages to the environments.
  • Upload data to the environments. You can move the data through the data packages or by restoring the database. If you restore the database, additional steps are required in order to remap some of the properties to the new tenant.
  • Update your user information.
  • Re-import all other users that have the correct security identifier (SID) and identity provider.
  • Execute the following commands to update the tenant ID:
  • Fully configure the environments. In this step, configure the integration endpoints.
  • Carry out smoke tests on the user acceptance testing (UAT) environment in the new MS Dynamics LCS project.
  • If you already have a production environment deployed, you must open a support request to move it to the new tenant after you’ve finished moving all the sandbox environments and completed UAT.

Delete Environments on the Old Tenant

After the new LCS project against the new Azure AD tenant is fully functional, you must stop, de-allocate, and delete the environments on the old LCS project. Once finished, the Configure button becomes available for each environment. Save any remaining artifacts from the Asset library that might be required later.

Suspend Subscriptions on the Old Tenant

  1. After all the environments have been deleted, and all the LCS artifacts that are required are saved, work with your cloud service provider or Volume Licensing Support to suspend all the licenses on the old Azure AD tenant.
  • Cloud service provider: Suspend existing subscriptions against the old tenant.
  • Volume Licensing Support: Call the Volume Licensing support center to confirm that the work is completed and that, the subscriptions can now be suspended against the old tenant.

2. File a support ticket to delete the old LCS project.

Locus IT provides Dynamics LCS services like LCS Implementation Project Migration, LCS Implementation Project upgrade and support. We also provide Dynamics LCS training and implementation services. For more information please contact us.

Locus IT Project Management Office
What’s it?