I agree 100% not documented enough.. I'm working with the folks who manage docs.microsoft.com to include additional information and of course posted this blog to address some of the routine questions I receive each day. UpdateChannelChanged is a Microsoft internal and managed value which is why its not documented broadly. It simply toggles to True on a change request like channel change. Office will reset this to False after the next successful update, like going from build 1 to build 2. Once False, another change request can be issued. (it should be a non-issue for you to be concerned about) However, if you at one time set a custom update path like \\O365\Updates and never populated share with newer builds and disabled Automatic Updates, clients can become orphaned because they will never receive a successful update, ever. Since this value is True, the Office client may not respect a new GPO for channel assignment because it believes the original change remains pending. This was more of a troubleshooting tip to help the few unwind custom configuration in favor of CDN or SCCM.