# D365 Finance and Supply Chain Implementation Health Assessment > Source: https://netray.co/tools/d365-fno-implementation-health-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten-question self-assessment of customization load, update discipline, security, data quality and reporting for a D365 F&O environment. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain ## Audience - D365 F&O owner - IT manager - CIO ## Tool **Kind:** assessment **Questions:** #### How much of your business logic depends on custom X++ extensions or ISV solutions? **Options:** ##### Very little, mostly standard and configuration **Score:** 3 ##### Moderate, extensions are documented and tested **Score:** 2 ##### Heavy, partly documented **Score:** 1 ##### Heavy and undocumented **Score:** 0 #### How do you handle the service updates Microsoft releases? **Options:** ##### Planned, regression tested and applied on schedule **Score:** 3 ##### Applied on schedule with limited testing **Score:** 2 ##### We postpone updates as long as allowed **Score:** 1 ##### We are surprised by them **Score:** 0 #### How well is your security role design maintained? **Options:** ##### Role based, reviewed at least twice a year with segregation of duties checks **Score:** 3 ##### Role based but reviewed rarely **Score:** 2 ##### Many users have custom or copied roles **Score:** 1 ##### Broad access is common, no regular review **Score:** 0 #### How reliable are your batch jobs and integrations? **Options:** ##### Monitored with alerts and documented recovery steps **Score:** 3 ##### Monitored manually each day **Score:** 2 ##### Failures are noticed when users complain **Score:** 1 ##### No clear owner **Score:** 0 #### How is master data quality managed (products, customers, vendors)? **Options:** ##### Defined owners, validation rules and regular clean-up **Score:** 3 ##### Owners exist, but quality checks are occasional **Score:** 2 ##### Duplicates and incomplete records are common **Score:** 1 ##### No ownership **Score:** 0 #### How do users get reports and answers from the system? **Options:** ##### Governed reporting model with self-service for most needs **Score:** 3 ##### Mix of standard reports and a few custom ones **Score:** 2 ##### Mostly exports to Excel with manual work **Score:** 1 ##### Reporting requests queue for weeks **Score:** 0 #### How current are your inventory dimension and costing settings relative to the business? **Options:** ##### Reviewed after each business change and understood by finance **Score:** 3 ##### Generally fine, with a few workarounds **Score:** 2 ##### Frequent negative on-hand or costing adjustments **Score:** 1 ##### Unclear who owns these settings **Score:** 0 #### How is the application lifecycle managed (source control, build pipeline, test environments)? **Options:** ##### Source control, automated build and test environments in place **Score:** 3 ##### Source control and builds, limited automated tests **Score:** 2 ##### Manual deployments between environments **Score:** 1 ##### Changes are sometimes made directly in production **Score:** 0 #### How well do users adopt the system and its standard processes? **Options:** ##### High adoption with few shadow spreadsheets **Score:** 3 ##### Good adoption with some workarounds **Score:** 2 ##### Many side tools used for core tasks **Score:** 1 ##### Users avoid the system where possible **Score:** 0 #### How clear is the support model and who owns the roadmap? **Options:** ##### Named product owner, support team and backlog **Score:** 3 ##### Support exists, roadmap is informal **Score:** 2 ##### Mostly reactive support from the partner **Score:** 1 ##### No clear ownership **Score:** 0 **Bands:** #### At risk **Min:** 0 **Max:** 30 **Verdict:** Your environment shows several weaknesses that will make updates, audits and reporting harder over time. **Recommendations:** - Run an independent health check of customizations, security and integrations. - Assign a named product owner and a monthly governance meeting. - Put a baseline regression test suite around finance and supply chain processes. - Document every integration and batch job with an owner. #### Needs attention **Min:** 31 **Max:** 55 **Verdict:** The basics work, but gaps in testing, security review or data ownership are likely to cost time at the next update or audit. **Recommendations:** - Review roles for segregation of duties and remove unused access. - Create a repeatable update test plan before the next service update window. - Identify the three most manual reports and decide how to automate them. - Review customizations for any that standard features now cover. #### Healthy **Min:** 56 **Max:** 80 **Verdict:** Your D365 environment is generally well run, with some areas to tighten. **Recommendations:** - Automate regression tests for your top processes. - Add alerts for batch and integration failures if not present. - Review master data ownership and run regular duplicate checks. #### Strong **Min:** 81 **Max:** 100 **Verdict:** You have disciplined governance, lifecycle management and adoption. Focus on continuous improvement. **Recommendations:** - Keep reviewing customizations against new standard features each release wave. - Invest in self-service analytics to reduce report backlog. - Share your practices across other business units or legal entities. ## Content **Intro:** This ten-question assessment helps D365 Finance and Supply Chain owners judge the health of their environment after go-live. It covers the areas that most often cause cost and risk: customization, updates, security, integrations, data, reporting and ownership. **Sections:** #### How to use the assessment **Body:** Answer based on what is true today, not on what is planned. It works best when the product owner, an IT lead and a finance or supply chain key user answer together, because they often see the situation differently. Take the result as a starting point for a conversation, not a grade. Repeat it every six months to see whether changes are moving the score. **Bullets:** - Answer with evidence in mind. - Involve both IT and business. - Record the date and compare to the previous run. #### What the questions measure **Body:** The questions follow the factors that determine total cost of ownership on a SaaS ERP. Customization load drives the effort of each continuous update, so it is weighted by two questions. Security and master data influence audit exposure and day to day errors. Integrations and batch jobs decide whether the business trusts the data. Reporting and adoption show whether the investment is delivering value to users. #### Interpreting the bands **Body:** The result is a percentage of the maximum possible score. A low score usually reflects missing governance more than missing technology: no named owner, no regression tests, no review cycle. The recommendations for each band are practical first steps. If you land in the At risk band, begin with a short independent health check so the work is prioritized by risk rather than by who shouts loudest. #### Common mistakes **Body:** Organizations often assume that SaaS means no maintenance. Continuous updates still need testing and ownership, and many projects lose their delivery team right after go-live. **Bullets:** - Treating the implementation partner as the product owner. - Skipping update testing because the environment is cloud hosted. - Letting security roles drift with every new request. - Solving reporting gaps with manual exports indefinitely. **Cta:** If your score points to reporting backlog or manual data work, Netray can show how read-only AI assisted access to ERP data can reduce it without adding customization. **Faq:** #### Is this assessment an official Microsoft health check? **Answer:** No. It is an independent self-assessment built from common practice for D365 Finance and Supply Chain owners. It is not a Microsoft tool and it does not replace a formal review of your environment. #### How often should we review the health of our D365 environment? **Answer:** Twice a year is a sensible baseline, plus a review before major releases, acquisitions or new legal entities. Quick checks of security roles and integration errors can be done monthly. #### What is the biggest driver of update effort? **Answer:** The number and complexity of extensions and ISV solutions, combined with how well they are tested. Each one adds regression testing at each service update, so reducing unneeded customization is often the best saving. #### Who should answer the questions? **Answer:** Ideally a product owner, an IT or technical lead and at least one finance or supply chain key user. Different roles see different problems, and combining views gives a more honest score. ## Search terms d365 health check, dynamics 365 finance health assessment, d365 f&o post go-live review, d365 customization review, d365 f&o assessment questionnaire, erp health check template, d365 environment health, d365 one version readiness --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json