This is not true if the policy only triggers if the value has never been set by the user, which it is not always possible to tell, but sometimes can be.
I have done exactly this with browser default home pages. I had an analysis pull back what home pages were set to, then figured out which home pages were browser defaults, NOT customized by the user, then I set the homepage ONLY if it was set to a default. This way the user could change it at any time and my policy would NOT reapply. I actually had 1 user report to me after I did this that their browser home page kept changing, and I was like, oh that is very odd, that shouldn’t be happening, then I looked into it and found that they kept setting it to
bing.com and I just assumed that was NOT a user doing it. I then made that check for that default more specific to avoid the case in which the user set the homepage to
bing.com and not something else. (I basically just had to make the URL check slightly more specific if set to
bing.com) I probably could have figured this out ahead of time if I had a larger sample size and checked the
multiplicity of unique values of… to realize it was only 1 user that had done this and it probably wasn’t a default value. I apologized to the user and had a laugh at my mistake.
Here is the 9 year old fixlet/task: https://bigfix.me/fixlet/details/3802