Prepare for go-live

This article provides guidance about how to prepare for the go-live for finance and operations apps.

To ensure that the production environment is used for live operations, Microsoft provisions the production instance when the solution is ready and after project readiness is validated as part of the Go-live Readiness Review with Microsoft. For more information about the environments in your subscription, see the Licensing guide.

For answers to common questions about go-live, see the Go-live FAQ.

The following table lists the key steps in the go-live process.

Go-live Readiness Review prerequisites

The project team should validate solution readiness. The following prerequisites must be met before the Go-live Readiness Review with Microsoft can be initiated. The production environment can be deployed after the Go-live Readiness Review with Microsoft is successfully completed.

• User acceptance testing (UAT) and performance testing is complete or almost completed in a Tier-2 (or higher) environment. Tier-1 environments must not be used for UAT or performance testing. For more information, see Tier-1 vs. Tier-2 and higher. For information about how to identify the correct sandbox environment tier, based on your transaction volumes, see Selecting the correct Tier-2 or higher environment.

  During the UAT phase, test all the business processes that you've implemented and any customizations that you made.

  • Test cases should cover the entire scope of requirements.
  • Use migrated data for testing. This data should include master data and opening balances, even if they aren't yet final.
  • Use the correct security roles for testing, including default roles and custom roles that are assigned to users.
  • Make sure that the solution complies with any company-specific and industry-specific regulatory requirements.
  • Obtain approval from the customer.

  Performance testing is a crucial part of validating the readiness of your solution. For detailed guidance about the recommended practices, review the Performance Testing Techtalks.

• The environment version that is planned for the go-live complies with the Software lifecycle policy. If you use Commerce Scale Units (CSU), the CSU version must be in sync with the environment version. For more information, see Component dependencies.

• Key customer team members are added to the Lifecycle Services project.

• A generic service account that's used to deploy the production environment is added to Lifecycle Services.

• All licenses that are required for go-live were purchased in the correct tenant.

• After all licenses are purchased, the final subscription estimator is uploaded and activated in Lifecycle Services. For more information, see Subscription estimator in Lifecycle Services.

• The Customization analysis report (CAR) is run, and critical issues are addressed. For more information, see Customization Analysis Report (CAR).

• The go-live date in Lifecycle Services correctly represents the go-live date that you're targeting. This date is the date when end users start live operations, not cutover activities.

• All relevant tasks and phases in the Lifecycle Services methodology are complete. Production can be deployed only after all phases, including the Test phase, are complete. To complete a phase in Lifecycle Services, first complete every required step in that phase. When all the steps in a phase are complete, you can complete the whole phase. You can always reopen a phase later if you must make changes. The process of completing a step has two parts:

  • Do the actual work, such as a fit-gap analysis or UAT.
  • Mark the corresponding step in the Lifecycle Services methodology as you complete it.

  Complete the steps in the methodology as you make progress with the implementation. Don't wait until the last minute.

Go-live Readiness Review with Microsoft

All finance and operations apps customers must complete a Go-live Readiness Review with the Microsoft FastTrack for Dynamics 365 team before production environments can be deployed. The main purpose of the review is to assess project readiness and help you have a smooth and successful go-live experience. Lifecycle Services project users receive an email reminder about the Go-live Readiness Review, based on the go-live date in Lifecycle Services.

The review might require up to three business days for the initial report, plus more time for any risk mitigation that is required. Determine an appropriate time to start this review, so that you can meet the go-live timeline.

For most projects, the Go-live Readiness Review is done in the FastTrack for Dynamics 365 implementation portal.

Initiate the Go-live readiness review in the portal

There are two options to proceed with the Go-live readiness review. You can choose either one of the following options.

• Option 1 - Self-Service Create/Join the Project in the Dynamics 365 Implementation Portal.

• Option 2 - Share details with Microsoft to create the Project

  Note

  Option 2 will be deprecated in the future.

Option 1 - Self-service create/join the project in the Dynamics 365 Implementation Portal

Submitting the Go-live readiness review can be performed by partners and customer in the Dynamics 365 Implementation portal without involving Microsoft. The Onboarding Wizard in the Implementation portal has simplified the steps to create the project, add the admin and users, and submitting the Go-Live review for self-service.

1. Create the project in Implementation portal. For more information about creating and joining the project, see Create or join a project in the Implementation Portal.
2. Ensure that the project admin on the project is from the customer organization. This user from the customer organization can then add more users and serve as the key participant in the Go-live readiness review. For more information about adding users, see Admin section.
3. Once the project is created, the project team can create and perform the Go-live readiness review in the portal using the guidance in the Portal Help article. All users who have registered on portal can access this article.

Option 2 - Share details with Microsoft to create the Project

Follow the below steps if you have any issues creating the project via the Dynamics 365 Implementation Portal/blocked from creating project due to any other reason. This option will be deprecated in the future, and we highly encourage you to follow Option 1 whenever possible.

1. The project team decides who from the customer organization is the admin for the project on Portal and a key participant of the Go-live Readiness review. Admin access to the project on Portal can be granted only to the member of the customer organization. Microsoft grants access to this user and this user manages access for other team members.

2. Project team sends an e-mail to d365fogl@microsoft.com and includes the following information:

   • Confirmation that the project is ready to start the Go-live Readiness Review. Carefully review prerequisites for the Go-live readiness review that are described in the earlier section of this article.
   • Confirmation of the Lifecycle Services project ID or Lifecycle Services project URL.
   • Confirmation of the planned Go-live date (when live operations start in Production). Make sure this date is reflected in the Lifecycle Services correctly.
   • Confirmation by when it's required to have Production environment deployed. Building a cutover plan allows to determine by which date environment should be available.
   • Confirmation who should be granted admin access for this project on Portal. It's required that admin access is granted to the member of the customer organization (unless it's an internal implementation by the partner).
   • Indicate in the e-mail if it's an internal implementation for a partner organization.

3. Microsoft grants the key review participant from the customer organization admin access to the project and confirms that this task is completed by responding to the email.

4. The admin adds more project team members.

5. Project team creates the review in the portal by following the guidance in the Portal Help article. All users who have registered on portal can access this article.

Submit the review

• The project team should provide answers to all questions in the review. The review process in the portal supports multi-user scenarios. Multiple team members can provide details for the go-live review at the same time.
• When answers are provided to all the questions in the Go-live Readiness Review, submit the review to Microsoft by selecting Submit.

After the review is submitted in the portal

• Microsoft FastTrack reviews the project and provides a report that describes the potential risks, best practices, and recommendations for a successful go-live of the project. The review might require up to three business days for the initial report, plus more time for any risk mitigation that is required.
• Users who are selected as Review participants in the portal receive email communication that provides updates about the review.
• When all critical risks are addressed, and the review is completed, Microsoft enables the production environment slot in the Lifecycle Services project. The customer/partner can then trigger the production environment deployment.

Production environment deployment

We recommend that you select a service account for environment deployment. For example, select a generic user account as the admin user of the environments that you deploy. If you select a named user account, you might not be able to access an environment if that user is unavailable. Here are some examples of scenarios where the admin user must access an environment:

• First sign-in to any environment after initial deployment – The admin user is the only user who can access the environment.
• First sign-in to a sandbox environment after a database refresh from the production environment – No user accounts except the admin account can sign in.

The production environment should be deployed to the same datacenter where your sandbox environments are deployed, and where UAT and performance testing were done. For information about network requirements and how to do latency testing, see Network requirements.

Production deployment takes approximately 30 minutes. When deployment is completed, an email notification is sent to the environment administrator.

The production environment is sized based on the number of licenses that are allocated to the Lifecycle Services project and the transaction volumes in the Subscription estimator.

After production is deployed, the project team can apply the deployable package by following the instructions in Promote an update to production environments and then migrate the data. For data migration, we recommend that you prepare and validate data in a nonproduction environment and then copy the sandbox database to production.