Word 365 does not respect alt text checker disable policy set via registry.

Hey all.

Couldn't help but notice that we were all unwittingly having all of our images sent up to Microsoft's cloud without notice, which is frustrating, if expected. Anyways, I looked at the GPOs for this and noticed that Word would only sometimes respect the registry setting for this, located at:

Group Policy: `User Configuration > Administrative Templates > Microsoft Word 2016 > File Tab > Check Accessibility > Stop Checking for alt text accessibility information`
Registry Path: `HKCU:\SOFTWARE\Policies\Microsoft\office\16.0\word\accchecker`
DWORD: `alttext`
Value: `0`

I tried with both values, 0 and 1, and nothing of interest occurred. In both cases, Word uploaded my test image to Microsoft's Computer Vision cloud and I got alt text information. I do not want alt text information. I'd prefer it if my software asked me before uploading voluminous amounts of our business data to the cloud controlled by the developers, but I guess that's just me hoping too much for a bygone era.

When I set the GPO to "Enabled", the corresponding registry DWORD is set to "0", which is peculiar for an "Enabled" value, but indeed it didn't immediately generate alt text. However, when I simply set the GPO to "Not Configured", and manually created the registry entry (our preferred way of setting Group Policy across numerous machines, as we do not have an Active Directory server in our environment - this may change), Word did not respect that policy, and did indeed generate alt text for my test image.

It would be helpful if Microsoft could be transparent about what they're doing, and provide clear and concise information, both in human- (documentation) and machine-readable (.json) forms about their web services, their IPv4 and IPv6 ranges, what they do, and what processes from both Office and Windows connect to them for and why - so that administrators like myself could block them. I suspect that's probably why they're not transparent about that, though, and choose instead to disrespect users' privacy desires for their own uses.