Go-Live readiness review process

It is required to pass the Go-Live readiness review process when you are requesting the Production environment. Please find the questionnaire below.

Solution Scope

1. Describe the planned rollout schedule. For each rollout provide 1) go-live date, 2) number of users, 3) key functional areas and 4) countries with the number of legal entities.
2. Please describe the vision and goals for this project

LCS

3. Are you using a generic account as the environment’s administrator?
   • Generic account will not be used as environment administrator
   • Generic account will be used as environment administrator
4. Have the customer key stakeholders been added to the LCS project?
   • Key customer stakeholders are added to the LCS project
   • Key customer stakeholders have not been added to the LCS project
5. Are all your Microsoft Online Services running on the same Azure Active Directory tenant? If they are running on multiple tenants, indicate the tenant(s) where the services are running and share the reason why separate tenants are required.
6. Is the Go-live milestone date in LCS methodology matching the planned Go-live date? Please make sure that Go-live date in LCS in reflecting the real Go-live plans when users will start live operations in Production.
   • Go-live date in LCS is not updated
   • Planned Go-live date is correctly reflected in LCS methodology
7. Are Analysis, Design and Develop, and Test phases in the LCS methodology completed to request Production Environment?
   • LCS methodology phase(s) including Test are not completed
   • All LCS methodology phases including Test are completed
8. Are all required licenses available in LCS for the initial Go-live?
   • All licenses required for the initial Go-live are in place and correctly reflected in active Subscription estimator
   • Additional licenses will be purchased in the near future
9. Is the final version of the Subscription estimator uploaded to LCS project and marked as active?
   • Final subscription estimator is not yet uploaded and activated
   • Final version of subscription estimator is uploaded and marked as active

User Acceptance Test

10. Provide the start date and end date of the UAT
11. On which environment was UAT performed? Please provide the environment name.
12. Have the final security roles been defined?
    • Final security roles have not yet been defined
    • Final security roles are defined
13. Were the correct security roles assigned to all users during UAT?
    • UAT was not performed with final security roles
    • UAT performed with final security roles
14. Do UAT test cases cover the entire scope of requirements planned for the Go-live?
    • UAT test cases cover only part of requirements planned for the Go-live
    • UAT test cases cover the entire scope of requirements planned for the Go-live
15. What percentage of UAT test cases have been successfully completed and signed-off by the customer?
16. How many users participated in UAT?
17. Was migrated data used for UAT?
    • There is no legacy data, UAT was performed on test/dummy data
    • UAT was performed on migrated data
    • UAT was not performed on migrated data
18. Are there any open Go-live blocking issues? If yes, please share your mitigation plan.
19. Are you using Task Guides for end user training?
    • Task Guides are being used for end user training
    • Task Guides are not being used for end user training
20. Has user training been completed?
    • End-user training is complete or almost complete
    • End-user training has not yet started or is in progress
21. Has the entire solution been documented, approved, and signed off by the customer to confirm that it meets their business needs? If no, please share what is pending and what is the timeline for getting sign-off.

Performance Testing

22. Have you completed performance testing of all critical business processes and integrations including peak load volumes?
    • Performance testing is out of scope for the first roll-out, but is planned for the next phase
    • Performance testing is not complete but during UAT performance was acceptable
    • Performance testing has been successfully completed
    • Performance testing has not been completed
23. Have defined performance acceptance criteria for go-live been met?
    • Performance testing is out of scope for the first roll-out, but is planned for the next phase
    • Performance acceptance criteria have not been defined
    • Performance acceptance criteria have been met
    • Performance acceptance criteria have not been met
24. What type of activities have you conducted to evaluate the performance of the solution?
25. Provide the start date and end date of the performance testing for the first roll out
26. On which environment did you run (or plan to run) performance testing? Please provide the environment name.
27. Have you decided in which data center Production environment will be deployed? Please share which data center it will be.
28. Have you done the Latency test for all end user locations in the Data Center chosen for Production?
    • Latency testing has not been performed
    • Different data center with better latency has been identified
    • Latency test results are within recommended range
    • In some locations latency is above recommended range
29. Have you observed high database utilization in your Sandbox environment?
    • High database utilization is observed but the root cause is not investigated
    • High database utilization is observed, the root cause has been identified and is being mitigated
    • High database utilization has not been observed
30. Has the performance testing been signed off by the customer? If no, please share what is pending and what is the timeline for getting sign-off.

Integrations

31. Have all the integration scenarios been tested at volume to validate service protection limits (throttling, timeouts, payload size)?
    • Service protection limits are known and the integration scenarios have been tested at volume
    • Test not executed at volume – limits not validated
32. Have all integration performance acceptance criteria been met for peak load volume?
    • Performance acceptance criteria have not been met
    • Performance acceptance criteria have been met
33. Have you tested both happy path and edge cases for each integration?
    • All integrations test scenarios (including happy path and edge cases) are tested and signed-off
    • Integrations were not tested for edge cases
34. What’s the hourly peak extended record count (number of calls * average number of lines) of the OData calls and Custom Service calls combined?
35. What’s the maximum frequency (in minutes) expected for integrations using the Data management package REST API?
36. Is there a plan to use the Recurring Integration Scheduler that is available on GitHub as an out-of-the-box integration solution?
    • Recurring Integration Scheduler (RIS) will not be used in Production
    • Out-of-the-box Recurring Integration Scheduler (RIS) will be used in Production
37. What is the maximum number of fields in your custom/customized business event payload?
38. Does any of the business event payloads contain a full record or long text fields (descriptions notes etc..)
    • Business events are not including full records or large text fields in the payload.
    • Full record or descriptive fields used in business event payload
    • Business events are not planned to be used
39. Is any business event attached to high volume process which would trigger a huge amount of events at the same time?
    • Business events are not used in the context of high-volume processes
    • Business events triggered by high-volume processes
40. Is error handling logic in place to guarantee there is no data corruption?
    • Error handling logic is in place
    • Error handling logic is not in place
41. Are notifications set up to alert users to any integration failures?
    • Failure notifications are set up
    • Notifications are not set up
42. Do you have integration support in place with named contacts and owners?
    • There is integration support in place with named contacts and owners
    • There is no integration support in place with named contacts and owners
    • Have all integrations in scope for the Go-live been signed off by the customer? If no, please share what is pending and what is the timeline for getting sign-off.

Code Management

44. Please list the ISV solutions that are part of the solution (in scope for the first Go-live)?
45. Are you using version control system (ie Azure DevOps) to manage your code?
    • Version Control System is not used to manage customizations
    • Version Control System is used for managing customizations
46. How are you generating your application deployable packages?
    • Using build pipeline(s) and build agent(s)
    • Using Visual Studio to export packages
47. Does the Azure DevOps Organization connected to LCS implementation project belong to customer or partner?
    • Azure DevOps Organization connected to LCS implementation project belongs to partner
    • Azure DevOps Organization connected to LCS implementation project belongs to customer
48. Is the code promotion process between environments established and documented, and does the whole team know and understand the process?
    • Code promotion process has not been established and documented
    • Code promotion process between environments is established and documented
49. When will you finalize your release candidate?
50. Have you generated a Customization Analysis Report (CAR) for your models?
    • CAR has been generated
    • There is no custom code to analyze
    • CAR has not been generated
51. Are there any open issues from the customization analysis report (CAR)? If yes, when are you planning to fix them?

Data Migration readiness

52. Is the configuration data ready and tested? If not, please share with us the expected timeline.
53. Is the master data and security setup that you will migrate ready and tested? If not, please share with us the expected timeline.
54. Are the open transactions/balances data that you will migrate ready? If not, please share with us the expected timeline.
55. How are you planning to bring configuration data, master data, and transaction data (e.g. opening balances) into the Production environment?
56. How did you test data quality and your data migration approach?
57. Has the time needed for data migration, during cutover, been estimated and planned?
    • Data migration is not planned as there is no legacy data
    • Data migration duration has been tested on Sandbox
    • Data migration duration is not enough to fit all data to be migrated in the expected time-frame.
    • Data migration duration determination is pending

Cutover

58. Do you have a cutover plan that contains activity duration, responsibilities, dependencies, and a roll-back plan, signed off by the customer?
    • Cutover plan is not ready or not signed-off yet
    • Cutover plan is ready and signed-off
59. Are you planning to do a mock cutover?
    • Mock cutover has been completed
    • It is planned to do mock cutover
    • There is no plan to conduct a mock cutover
60. Are you familiar with the process of how to request a Production environment?
    • Project team is familiar with the process to request Production
    • Project team is not familiar with the process to request Production
61. Are you familiar with the processes and SLAs for servicing operations such as deployable package installation to Production, Sandbox DB copy to Production etc?
    • Project team is not familiar with the processes and SLAs for servicing operations
    • Project team is familiar with the processes and SLAs for servicing operations

Continues Updates

62. Is the team familiar with the Continuous Updates policy?
    • The project team is familiar with the Continuous Updates policy
    • Project team is not familiar with Continuous Updates policy
63. On which version do you plan to request Production environment?
64. Have you reviewed the Continuous Updates settings in your LCS project and made adjustments as needed?
    • Update settings in LCS project are reviewed and adjusted as needed
    • Project team has not reviewed Update settings in LCS project
65. Briefly describe your organization’s plan for Continuous Updates
66. Do you plan to use automated regression testing?
    • It is planned to use automated regression testing
    • There is no plan for automated regression testing
67. Are you using any tool for regression testing, like Regression Suite Automation Tool (RSAT) or a third party tool?
    • Third party regression testing tool is implemented
    • RSAT is implemented
    • Automated regression testing is not implemented yet

Production Support and Maintenance

68. Does the project team have a plan in place for regular Production environment monitoring and maintenance routines?
    • Project team have a plan in place for regular Production environment monitoring and maintenance routines.
    • Project team does not have a plan in place for regular Production environment monitoring and maintenance routines
69. Is the project team familiar with the LCS environment monitoring and diagnostics tools?
    • Project team is familiar with the LCS environment monitoring and diagnostics tools
    • Project team is not familiar with LCS environment monitoring and diagnostics tools
70. Has the project team defined post Go-live issue resolution and escalation process?
    • Project team does not have a defined process to report, triage, escalate and resolve issues in Production environment
    • Project team has a defined process to report, triage, escalate and resolve issues in Production environment
71. Has the project team verified that team members are able to submit support tickets to Microsoft in LCS under the correct support plan?
    • Project team has not validated the process of submitting support tickets to Microsoft in LCS
    • Project team members are able to log support tickets under the right support plan
    • Project team members have faced issues with submitting tickets to Microsoft support in LCS under the right support plan
72. Is the project team familiar with the process to report Production outage in LCS?
    • Project team is familiar with the process to report Production outage
    • Project team is not familiar with the process to report Production outage

Azure DevOps: Colorful logs from PowerShell output

My colleague Oleksandr Nikolaev has found out how to add colors to the PowerShell logs on Azure DevOps. In addition to this, it is also possible to make log groupings.

Dynamics 365 Customer Insights trial environment clean up

I’m playing with Dynamics Customer Insights. And find out that I can’t remove data source after data matching and unifying. In this case, it would be better to wipe out the whole environment.

Please find below how to remove the trial environment and create a new one.

Open Environments page

Truncate AxDB Transaction Log file

When you use the FnO for a while, you see how the transaction log file is growing. And you need to reduce it. Well, if you see how it is growing, then you probably need to configure Transaction Log backup. And you are lucky.

When you do not see how it grows and you are not lucky, you just see a red on the free disk space. And you understand that it’s your SQL AxDB Log file, that has 150 GB. And you have to truncate it somehow.

Call Microsoft Flow / Logic App from X++ code

This is a simple example of how to call external web services from D365FO without using any C# DLL files. Just plain X++ code. As sample External Web Service, I have selected Microsoft Flow. Azure Logic Apps will be similar.

Automatic Release Notes

It’s a good idea to have Release Notes. But how to build Release Notes in automatic mode?

The following post inspired by the https://marketplace.visualstudio.com/items?itemName=richardfennellBM.BM-VSTS-GenerateReleaseNotes-Task I didn’t implement this DevOps pipeline extension but took the idea and some PowerShell scripts.

Scenario

After every single successful Code Build on Build Server, I would like to save Code Build changesets and developer comments. Then I would like to add it to the Release Notes.

Reading OData from Dynamics 365

I’m going to show you a sample PowerShell script to read the data from Dynamics 365 products. And how to create Azure Active Directory Application and use it for authentication in Dynamics 365 for Sales and Dynamics 365 for Finance and Operations.

Create Azure Application

Open Azure portal. Find Azure Active Directory, then App registrations and click on +New application registrations.

Dynamics 365 for Operation and Chrome error

I have downloaded new Dynamics 365 for Operations Platform Update 5 AKA AX7. Unpack and install it. Everything is fine, except one thing.

I can log in through IE, but Chrome gives me error ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY.

After searching this error on the Internet I have found the solution. Just download IISCrypto from https://www.nartac.com/Products/IISCrypto/Download. Run it and select the best practices template. Then reboot your server.

That’s it.

 

Microsoft Dynamics AX 2009 and Microsoft SQL Server 2012 SP3

I would like to share some info about Microsoft SQL Server 2012 SP3 and Microsoft Dynamics AX 2009.
If you have the following error when Deploy SSRS Reports

StarWind iSCSI tips and tricks

When you create StarWind new HA disk for a 2000GB you have got a full sync. It take a time.

Create new disk for 1GB. Get your full sync. Then extend your StarWind disk size for 1999GB. And you get full synced HA disk for a 2000GB in a seconds.