Microsoft 365 Normalization

[Lucas35]

Hello,

During the normalization process, it was identified that within the discovery model, the product "Microsoft 365 Apps for enterprise" is partially normalized. Therefore, how could the complete normalization be carried out, including version and edition?

Thank you.

[dreinhardt]

Hi @Lucas35,

for "M365 Apps for enterprise" the definition of a "fully normalized" discovery model (Status Manually Normalized or Normalized by ServiceNow) is based on Publisher, Product, Version and Edition. As you already mentioned, the version part is missing. What we've seen in the last month, based on our latest "Normalization Suggestions" is, that ServiceNow is adding the M365 "Channel Version" as version to most of the "M365 Apps for enterprise" discovery models. Details about the channel version and Builds can be found here -> Update history for Microsoft 365 Apps (listed by date) - Office release notes | Microsoft Learn.

Best, Dennis

[SN Arch Guy]

@dreinhardt should there be normalization suggestions for partially normalized models? we don't see any.

we see partially normalized models for mainstream products like Windows / Microsoft Office / Microsoft PowerPoint / Oracle Java that have the full Discovered version in the model record (for example, Windows 10.0.19044.4046 and Java 8.0.3510.10) but still miss other information like the Version and the Edition. do we just need to wait a few cycles for the content service to catch up?

[MikeW_SAMBeast]

Sometimes there is a delay content service providing the fully normalized discovery model. I find this happens most with M365, Visio and Project. The discovery model is partially normalized because the publisher and product has been normalized but there is no normalization rule for the version in the content library.