Systems Management

As you have probably experienced, the SW titles do not give you the architecture of MS Office, and in my situation, this is important because I have 1 piece of SW I deploy that must match a 32-bit or 64-bit installation of Office. In order to make this dynamic and allow the labels to do their work, I have to identify machines by that criteria. Sparing you the bore as to the reason why our environment uses both architectures, it just does, and thus creates this conundrum. 

I have this setup for Office 2016 and it works like a charm:

RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Outlook, Bitness, STRING)

Now as we migrate to O365

I tried this and it will not give a result, even though the string value is verified:

RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, Platform, STRING)

Any ideas?