With the introduction of proactive quality updates, it has become even more important to understand what is added between Microsoft platform and application builds. One suggestion was to sign up for Community Driven Engineering (CDE), however this requires a CxO sponsor and was originally intended to enable partners to submit code changes directly to Microsoft, so the form is understandably full of legalese. I think it's important to provide a tool which anyone can understand without a special registration, to be able to see which fixes were delivered between 2 builds on the same service update.

To explain further and highlight business impact, please consider the following example scenario:

- Contoso company is in the middle of UAT for a large set of changes; Production and UAT builds were 10.0.xxxx.yy.

- An automatic Quality Update was recently applied by Microsoft to UAT, which brought UAT up to a higher build of 10.0.xxxx.zz with Production remaining on 10.0.xxxx.yy.

This means that the last test cases in their final UAT cycle are being tested on a Microsoft build which is not consistent with the Microsoft build of Production or previous test cases.

Everything must be tested on UAT before the next release, not just for best practice and quality purposes, but because it's physically enforced by the way Production deployments work:

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/updateenvironment-newinfrastructure#promote-an-update-to-production-environments

"...To address these challenges, Microsoft has introduced the image-based, update process. As was discussed earlier in this article, as packages are applied to sandbox environments, Microsoft creates images that are given an Update name value. This value represents the whole runtime, including Microsoft code and all custom code as a single unit. " 

Therefore, we need to identify which KBs are between 10.0.xxxx.yy (Production) and 10.0.xxxx.zz (UAT), so it can be risk assessed and any individual KBs which may have a business impact can be tested before going live with the next set of changes.