Describe the FastTrack go-live assessment and Production environment request
X++ Programming Language > Managing Applications in Dynamics 365 Finance and Operations > Managing Applications in Dynamics 365 Finance and Operations
207
Answer:
Describe the FastTrack go-live assessment and Production environment request
Microsoft FastTrack for Finance and Operations apps is a customer success service that is designed to help you move smoothly and confidently to Finance and Operations apps so that you can realize business value faster.
When participating in the FastTrack program, you receive guidance about implementation best practices, planning for successful rollouts, and expanding capabilities. However, you can implement at your own pace. You also have access to Microsoft Solution Architects who are committed to making your experience with Finance and Operations apps a success.
All Finance and Operations apps customers need to complete a go-live review 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, go to Welcome to FastTrack for Dynamics 365.
About eight weeks before go-live, the FastTrack team will ask you to fill in a go-live checklist:
-
If you have a combined annual adjusted revenue of 300,000 U.S. dollars (USD) or more, a Microsoft Solution Architect is assigned to your project, who drives various workshops with Customer and Partner during the implementation.
-
If you have a combined annual adjusted revenue of less than 300,000 USD, all the communication with the FastTrack team is via email.
To learn more about FastTrack eligibility, review the Customer eligibility and partner qualifications.
You can also download a FastTrack pre-go-live checklist.
The project manager or a key project member needs to complete the go-live checklist during the pre-go-live phase of the project. Typically, the checklist is completed four to six weeks before the proposed go-live date, when UAT is completed or almost completed.
After the checklist is submitted, a Microsoft solution architect will review the project and provide an assessment that describes the potential risks, best practices, and recommendations for a successful go-live of the project. In some cases, the Solution Architect might highlight risk factors and ask for a mitigation plan. When the assessment is completed, the Solution Architect will indicate that you're ready to request the production environment in LCS.
If you request the production environment before the assessment is completed, the deployment will remain in the Queued state until the assessment is successfully completed.
You can cancel an environment deployment request while it is in a Queued state by following these steps:
-
Select Queued.
-
On the Customer sign-off tab, select Clear sign-off.
This will set the environment back into a state of Configure and allow you to make changes to the configuration, such as selecting a different data center or environment topology.
Request a production environment
After you've completed the analysis, design and develop, and test phases in the LCS methodology, and the go-live assessment has concluded that the project is ready, you can request your production environment.
We recommend that you select a service account, for example a generic user account, as the Admin user of the environments that you deploy. If you use a named user account, you might not be able to access an environment if that user isn't available.
The following are scenarios where the Admin user needs to access an environment:
-
First sign in to any environment after initial deployment - In this case, 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 - In this case, all user accounts except the Admin account are unable to sign in.
Your production environment should be deployed to the same datacenter where your sandbox environments are deployed.
After you've signed off on the request for the production environment, Microsoft is responsible for deploying the production environment for you. The Microsoft service level agreement (SLA) for deployment of a production environment is 48 hours. The production environment can be deployed at any time within 48 hours after you submit the request, provided that your usage profile doesn't require additional information. You can view the progress of the deployment in LCS. Typically, the status of the production environment request remains Queued for a few hours before it's changed to Deploying.
When you submit the deployment request, a service request for the Microsoft Dynamics Service Engineering (DSE) team is automatically created. You can view this service request in the Service requests list in LCS. If the DSE team has questions that prevent them from deploying the production environment, they will add a comment to the service request.
For example, the DSE team might ask that you update the subscription estimate or change the datacenter. In some cases, you might have to clear the sign-off from the production deployment request to make changes.
You can clear the sign-off only while the status of the production environment request is Queued. To clear the sign-off, select the Queued button. The status of the request is returned to Configure. You can then make any changes that are required and sign-off again.
Request a production environment
After you've completed the analysis, design and develop, and test phases in the LCS methodology, and the go-live assessment has concluded that the project is ready, you can request your production environment.
We recommend that you select a service account, for example a generic user account, as the Admin user of the environments that you deploy. If you use a named user account, you might not be able to access an environment if that user isn't available.
The following are scenarios where the Admin user needs to access an environment:
-
First sign in to any environment after initial deployment - In this case, 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 - In this case, all user accounts except the Admin account are unable to sign in.
Your production environment should be deployed to the same datacenter where your sandbox environments are deployed.
After you've signed off on the request for the production environment, Microsoft is responsible for deploying the production environment for you. The Microsoft service level agreement (SLA) for deployment of a production environment is 48 hours. The production environment can be deployed at any time within 48 hours after you submit the request, provided that your usage profile doesn't require additional information. You can view the progress of the deployment in LCS. Typically, the status of the production environment request remains Queued for a few hours before it's changed to Deploying.
When you submit the deployment request, a service request for the Microsoft Dynamics Service Engineering (DSE) team is automatically created. You can view this service request in the Service requests list in LCS. If the DSE team has questions that prevent them from deploying the production environment, they will add a comment to the service request.
For example, the DSE team might ask that you update the subscription estimate or change the datacenter. In some cases, you might have to clear the sign-off from the production deployment request to make changes.
You can clear the sign-off only while the status of the production environment request is Queued. To clear the sign-off, select the Queued button. The status of the request is returned to Configure. You can then make any changes that are required and sign-off again.
This Particular section is dedicated to Question & Answer only. If you want learn more about X++ Programming Language. Then you can visit below links to get more depth on this subject.
Join Our telegram group to ask Questions
Click below button to join our groups.