Describe the Go-live process for Finance and Operations apps.

X++ Programming Language >   Managing Applications in Dynamics 365 Finance and Operations >   Managing Applications in Dynamics 365 Finance and Operations  

371

---

Answer:

Describe the Go-live process for Finance and Operations apps.

The Go-live process is shown in the following image.

The Go-live process consists of the following actions, which should be considered as sequential steps in a checklist:

1. Update the Go-live date in LCS: Throughout project implementation, make sure that the milestone dates are continuously kept up-to-date. Start this step, at the latest, two to three months prior to Go-live. You need to closely engage with customer key stakeholders during this period in case anything unusual happens

2. Complete and send Pre-Go-live checklist: You can perform this task after all User Acceptance Tests (UATs) are completed and signed off by key stakeholders. All Finance and Operations apps customers must complete a Go-live assessment with the Microsoft FastTrack team before their production environment can be deployed. This assessment should be successfully completed before you request your production environment. If you aren't familiar with Microsoft FastTrack, refer to Welcome to FastTrack for Dynamics 365. You can also download the checklist from FastTrack Resources page.

3. Project assessment (Fast Track Essentials): The architect will deliver the assessment after the checklist is received and will then continue reviewing until questions are clarified and mitigations are in place, if applicable. It should take a few days for the initial report, plus additional time for mitigation, if necessary. This task is the responsibility of a FastTrack Architect. Project workshop (FastTrack): A FastTrack Architect uses a project workshop to coordinate activities for assessment.

4. Release for production deployment: If the production deployment request has already been submitted, deployment will start. However, we request that you only submit the production request after the assessment has been successfully completed. Perform this task upon a successfully completed assessment.

5. Request production deployment: This is a self-service task and the responsibility of your customer, though it can be done with your help. The customer should request the production deployment and submit it to Microsoft only after the FastTrack Architect has finished the assessment.

   As an earlier part of this step, the sizing team should have informed the customer about the topology needed in a pricing option. Automatic sizing is based on a subscription estimate by default, while manual sizing is based on exception.

   In the case of automatic sizing, the timing for sizing is immediate, but it could take longer if it requires further clarification of the subscription estimate.

   Finally, the Dynamics Service Engineering (DSE) team performs the deployment, which can take up to 48 hours to complete. The Status field in LCS reflects the deployment progress. Any questions that you might have about your request will be posted as comments on the service request.

6. Submit deployable package installation request: Your customer should be aware that applying packages causes system downtime. All relevant services will be stopped, and they won't be able to use the environments while the package is being applied. You should plan accordingly and perhaps perform this task during off hours. For package installation, depending on number of packages, it could take a minimum of five hours lead time and four hours downtime for each package.

   Generally, 95 percent of the updates are applied in less than one hour. However, we still recommend that you provide a downtime window of four hours in case a rollback is required for any reason.

   When the package deployment succeeds, the environment will be available as soon as the package deployment has finished, which means that the longer downtime window does not have any negative effect on system availability.

7. Submit request to copy database from sandbox (if applicable): You need to follow the instructions exactly as they are documented in Refresh database.

   Also, you need to request copy database to restore it to the sandbox environment. Once requested, Dynamics Service Engineering (DSE) will copy the production database and make it available in the LCS project's asset library. Note that it might need five hours lead time and result in two hours downtime.

   Generally, the database copy is completed in less than one hour. We still recommend that you provide a downtime window of two hours in case a rollback is required for any reason.

8. Production ready: In this task, you and your customer can take control of the production environment after all previous steps have been completed. Depending on the project, some cutover activities might need to be performed.

9. Go-live: Depending on the project, the customer can go live with Finance and Operations apps, hosted in the production environment.

---

---

Join Our telegram group to ask Questions

Click below button to join our groups.