We started this chapter by learning about one of the final phases of the implementation project, go-live. Go-live is exciting but is also the most hectic and intense period of the project. The cloud has changed the way a production environment is managed and updated. Roles and responsibilities have changed. We started by understanding how a production environment's responsibilities vary based on the deployment model you selected for your project. We discussed go-live activities to understand what goes on during the go-live phase of the project. The decision of going live or not is not easy and needs many considerations. We went through everything you need to understand to make that decision, the different sign-offs you need, how it can be difficult for project managers and stakeholders to make a decision to not go live if things are not good, and the importance of planning business contingency. In the end, we discussed how you can put together a plan and mitigate the risks through multiple simulations and reviews. This was followed by tips for the execution of a go-live plan and the importance of managing communication.
Later, we learned about post-go-live activities, support planning, issue management, and the tools to use throughout the life cycle of an issue. We covered capabilities in LCS, such as Issue Search, Work items, Support, and various other kinds of services requests. We also touched upon hotfixes and the three types – binary, X++ application, and metadata – which will be covered in the next chapter in detail. We also covered the steps of submitting product-related issues to Microsoft using support tooling in LCS, as well as how to raise various kinds of service requests related to your production environment on Azure when managed by Microsoft. We also covered various options regarding how to manage your environment, such as monitoring, diagnostics, and analytics. The resources that were shared in the first section of this chapter are your knowledge repositories for any support situation and your continuous learning.
In the next chapter, we will look at the One Version update process of Dynamics 365 for Finance and Operations.