Service the solution

Chapter 20

In this chapter, we discuss proactively monitoring the health of your solution implementation. We give an overview of the continuous updates provided by Dynamics 365 and share best practices for working this pattern into your project plan to minimize impact to the changes in your environment. We also encourage you to build a plan for continuous education in the trends and tools related to your business applications to maximize your organization’s Dynamics 365 investment.

Chapter objectives

  • Learn how to monitor your service health.

  • Plan for service updates.

  • Read about how to perform maintenance on your environment.

  • See how you can continue your business application journey.

What’s new

In addition to updated graphics, we’ve provided updated text for improved readability and updates to product names.

Case study

An agricultural business implemented finance and operations apps including some extensions that involved an ISV. They discovered the ISV provided updates later in the release cycle or sometimes not at all due to their own internal processes. Because of this, the organization found themselves unable to implement new features as they became available and had to manually apply Dynamics 365 updates to maintain operations properly. They were eventually able to work with their ISV to align their release schedule to Microsoft’s timeline, giving them enough time to test their solution during standard releases. Simply implementing and updating the solution wasn’t enough. Organizations must have awareness of third-party solutions that may have impact on the Dynamics 365 release cadence and how soon the updates can be applied in your environment to maximize the benefits from the latest Microsoft innovations as they become available.