Hi,
Had raised the support ticket with Microsoft team and shared the details and SCCM client systems logs.
Got the below response from Microsoft support.
Temporary fix suggested by Microsoft:
So until it got fixed we have to go for a compliance rule to check the presence of update using the other registry key (ClientVersionToReport)
Hello Manzoor,
I have a call with a Office 365 and also looked at the logs, and found that there is bad design with will be change in the near future.
The problem is regarding the detection logic on office deployment. because different products share the same registry key, it will generate that error.
This is actually schedule for the next year, so I don't have a expected timeline, of when this will be corrected.
Until then I will actual go for a compliance rule to check the presence of update using the other registry key (ClientVersionToReport)
Thank You,
