Views:

Applies to Product - Dynamics 365 Lifecycle Services


What’s happening?
Customers seek confirmation on their ability to deploy a new sandbox environment for their second Lifecycle Services (LCS) project after successfully creating the first project with an existing sandbox environment.
 

Reason:
This arises from the need to verify the deployment capabilities of a new sandbox environment within the constraints of existing licenses and environment slots.
 

Resolution:

  1. Check Environment Slots: Ensure that additional add-on slots for the new sandbox environment have been purchased. This can be verified by visiting the Organization Offer Detail page in LCS.
  2. Validate Environment Setup: Confirm that the new sandbox environment is correctly set up and configured, including ensuring that the environment is prefixed correctly (e.g., "Addon" for additional sandboxes).
  3. Provision the Environment: Use the Lifecycle Services (LCS) to provision the new sandbox environment. Follow the steps outlined in the LCS documentation for provisioning a new environment.
  4. Deploy the Package: Apply the deployable package to the new sandbox environment using LCS. Follow the steps for applying a package to a non-production environment.
  5. Run Validation Tests: After deploying the package, run validation tests to ensure that the deployment is successful. This includes checking for any errors or issues during the deployment process.
  6. Monitor the Environment: Continuously monitor the new sandbox environment for any issues or performance concerns. Use the tools and services provided by LCS to keep track of the environment's status.
  7. If additional sandbox environments are needed and no more add-ons can be purchased, deallocate and delete a previously deployed sandbox to free up the slot for the new project.