PENDING Moving from SCCM to Intune for 365 Updates

[MicrosoftCloudRegKey]

Piloting machines to move workloads over from SCCM to Intune
These machines are now co-managed and have the workloads of Office 365 Click-to-run workload transferred over to Intune
For the first week, it worked great. I saw that in word / excel / etc, "managed by your system administrator" went away and I could manually update this or allow Microsoft to update this via the servicing profile of config.microsoft.com
The past few days I noticed our machines have reverted back to "managed by your system administrator" and SCCM was taking control of updates.
I confirmed here that the key for "OfficeMgmtCOM" was set to 0:
hkey_local_machine\software\policies\microsoft\office\16.0\common\officeupdates
However, I found a NEW location on our machines where the "OfficeMgmtCOM" is set to 1 at this location:
hkey_local_machine\software\wow6432node\Policies\Microsoft\cloud\office\16.0\common\officeupdates
If I revert that from 1 to 0, Office is no longer managed by SCCM. The problem is that after a few hours, it reverts itself back to 1 again.

I have confirmed that we do not have any group policies applying this key, nor do we have any policies / scripts creating this key. I cannot find any real documentation on the "cloud\office\" location either. Why is this key here and how do I stop "OfficeMgmtCOM" from updating to 1 in this location?

It almost looks like this registry key location can be coming from config.office.com but we have ZERO policies created aside from a servicing profile that only allows me to specify what machines I want updated.

 

[Prajwal Desai]

I am not sure about this, but let me take a guess. In ConfigMgr client settings, is the setting enabled for enable management of the Office 365 Client Agent?

 

[MicrosoftCloudRegKey]

Hi Prajwal. I actually thought of that as well, so I set a client setting with the highest priority to disable Office 365 Management and applied it to the device. The only registry key this affected was:
hkey_local_machine\software\policies\microsoft\office\16.0\common\officeupdates

It did not touch or affect the registry key here:
hkey_local_machine\software\wow6432node\Policies\Microsoft\cloud\office\16.0\common\officeupdates

Now I do have a theory. MS Support has no idea and I can't find any documentation that discusses this registry key location or anything that backs up my theory.
Here's my theory:
I wonder if this is working as intended. I wonder if the fact that you turn servicing profile on (in config.office.com) enables OfficemgmtCom to 1 in the registry under this "cloud\office" key. Maybe OfficeMgmtCOM here is to ENABLE Servicing Profile for Office management whereas the original location is for SCCM? I'm not sure, but it's just a theory.
Does anyone here use servicing profile, have used it or has any thoughts?