What Is the Solution Health Hub?

The name is slightly misleading, so up front: the Solution Health Hub does not check the quality of your own solutions. It checks the overall health of a Dynamics 365 environment. That means whether the configuration and components of the Microsoft apps are in an expected state. Within this scope, it is useful and costs nothing.

What it does

The hub is a model-driven app that is present automatically in environments with Dynamics 365 apps. It runs rule sets whose rules detect typical environment problems. Examples are deactivated processes and flows that should be running, faulty configuration states of app components, processes whose owner is a deactivated user, or known problem patterns after updates.

You can start analyses per rule set on demand. Some also run automatically after certain events. The result is a list of analysis records with findings. Each has a description and, where possible, hints for fixing it. Some rules even offer automatic corrections.

On availability: the hub comes with the Dynamics 365 apps. Pure Power Platform environments without these D365 apps do not have it. There it would make little sense anyway, since there is nothing to check. If you cannot find it in the app list, you probably have no environment it was made for.

How to read the results

The list of findings needs some interpretation. Not every red entry is an acute problem. Some rules report states that are intended in the specific environment, for example deliberately deactivated processes of an unused module. The hub does not know the intent, because it only knows the target state of the Microsoft apps. So a one-time pass makes sense, in which each finding is either fixed or marked as accepted with a short note. In later runs, only what is new stands out. And that is the really interesting information.

What it is good for

Its best moment of use is after changes: after a big platform update, after installing or updating Microsoft apps. At these moments, it answers the question of whether the environment itself is fine, before you look for faulty behavior in your own customizations. That occasionally saves hours of troubleshooting in the wrong direction.

What it is not

The distinction in three sentences. It does not assess the quality of your own customizations, the Solution Checker is responsible for that. It says nothing about documentation, naming conventions, legacy or the handover readiness of a solution. That is the level of audit tools. And it needs access to the running environment. It cannot judge someone else's solution before installation.

In short: a tool for operating the environment, not for assessing solutions. In this role, it may well be better known than it is. In many environments the app has long been installed and ready, without anyone ever having opened it.