The plans about OneVersion for Microsoft Dynamics 365 applications are already announced. While OneVersion is enabling Customers, Microsoft and Partners to respond the ever-changing market and business demands in an agile way using all the hidden possibilities of a modern managed software ecosystem; It is important to ensure the smooth transitions between the frequent periodic and regular (monthly) updates. Therefor the need to have a “hit-map” to show which areas of the application/functionality is affected by each update wave is a big accelerator in this direction. Having the fact that nowadays we have the application usage intelligence based on the collected telemetry data as well as the fact that business processes can be modelled in the Life Cycle services, it should be possible to create such a hit-map, which is even interactive and is tailored to the specifications and usage of a customer environment. This will be a guide for Customers and Partners to know where to start when a periodic update needs to be validated by them before giving the approval for deployment to the Production.