Deploy a new environment
Functionality noted in this article will be made available to users based on the geographic location recognized by Microsoft Azure.
This article walks through the process of deploying sandbox (Tier 2 and above) and production environments with the self-service deployment experience. Refer to the following procedure to deploy these environments.
Select Configure on the project dashboard page.
Select the Application and Platform version for the environment that you want to deploy.
Provide a unique name for the environment.
For US Government projects in the Government Community Cloud (GCC), environment names are limited to 15 characters for sandboxes and 23 characters for production due to the total length of the resulting URL.
Select the region where you want this environment to be deployed.
Starting July 2023 customers can deploy Microsoft managed finance and operations environments to any region from any Lifecycle Services instance (apart from US GCC and 21Vianet in China). Earlier it was only possible to deploy to regions which were data resident to the Lifecycle Services endpoint itself, for example France Lifecycle Services only allowed deployment in France geo. For more information about which regions are available and what you must consider when you make a selection, see Available geographies for Dynamics 365 finance and operations apps.
Select whether you want to load demo data in your environment or whether you want an empty database.
Select the BPM library to use as the Getting started library in the product.
If you want to apply customizations, select from a list of available AOT packages (customization packages) on the Software Deployable tabs in the Asset library. You should select only packages that are generated from a build environment on version 8.1 and later. Application of a package from an incompatible version will adversely affect the environment.
Specify two user email addresses that should receive notifications that are related to this environment. These users are in addition to the users who are already on the project team (such as an independent software vendor [ISV] or a partner).
Select the email address of the user to set as the system administrator in the product.
After you validate the configurations, select Submit to trigger the deployment.
If you plan to use channels, you must also initialize Retail Cloud Scale Unit.
The environment deployment starts immediately and could take anywhere between 30 minutes to 1 hour to complete for a sandbox environment and 1-2 hours for a production environment.
To closely monitor the deployment progress, you can view the Environment details page. The environment state should change to either Deploying or Deployed/Failed.
If the deployment succeeds, the environment state is Deployed, and the user set as the environment administrator is able to sign in to the environment.
If the deployment fails, then create a Microsoft support ticket and provide the Last Activity ID (available under Manage environment on the Environment details page) in the support ticket.
Delete an environment
You can delete an environment that is in the deployed state directly through the environment details page. To delete an environment, go to the environment details page and click the Delete button on the action bar. A confirmation dialog box prompts you to enter the name of the environment that you want to delete. After you enter the environment name and select Yes, the deletion operation will start. When the deletion operation is complete, the Configure button for this environment is enabled on the project dashboard if you want to redeploy the environment.
To redeploy an environment, you will need to delete the environment and then deploy it again using the steps listed above.
For existing customers using channel functionality in the cloud, to ensure continued and uninterrupted support for your business, we require that you Initialize Retail Cloud Scale Unit no later than January 31, 2020. There is no action required for customers who exclusively use Store Scale Unit. Contact your Microsoft FastTrack Solution Architect if you require an extension.