Root cause analysis

VSTS should be used for all your project activities, goals, deliverables, code, documents, and collaboration as well as for your single source of support. We recommend the following steps in performing root cause analysis along with problem isolation, as follows:

Once the issue is available in VSTS, it should be classified and updated with more details. All ownership, assignments, and linking with existing BPM artifacts are recommended to be done in VSTS.

Advisor/partners/implementation team members must recreate the issue in a non-production environment, isolate the problem, and capture issue insights. The identified root cause should be updated in the VSTS work item for resolution.

Following a screenshot shows an issue ...

Get Implementing Microsoft Dynamics 365 for Finance and Operations now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.