MicrosoftHi everybody, we are facing the same issue as mentioned earlier by lachvit, JaredA58 and SimoMoti. The "FetchInterval" has the value 0 (zero) on our clients, so the clients do not seem to contact the Office Cloud Policy service at all and no policies are deployed to our clients.
This problem is blocking us from rolling out Microsoft Information Protection and sensitivity labels to an environment of 10k users, because we want the cloud policy to enforce the setting "Use the Sensitivity feature in Office to apply and view sensitivity labels" instead of using the legacy AIP add-in for Office.
Anyways, after we deleted the whole HKCU\SOFTWARE\Microsoft\Office\16.0\Common\CloudPolicy\ registry key on some of our clients, these clients successfully fetched the desired registry settings from the Office Cloud Policy service, and the "FetchInterval" was set to 90 minutes.
Nevertheless, after we removed again the clients/users from the group, which is in scope of our cloud policy, these clients got the FetchInterval = 0 setting again. Consequently, the clients are now stuck in the bad state again. We would need to delete the whole ...\CloudPolicy\ thing again, before we were able to deploy new policies via config.office.com to the clients.
In summary, we are not happy with this workaround. We do not want to be required to delete the ...\CloudPolicy\ registry key on clients, which have not been in scope for a cloud policy before.
Is there any better solution Microsoft can offer to us? DaveGuenthner Do you already have some news from the team you got in contact with?
Thanks a lot for any further help.
