I would imagine this isn't going to go over very well with a lot of companies. I would bet many already ban employees using copilot or other AI assistants because they don't want their company's proprietary data being sent to Microsoft or Google or whoever. Stick a key on the keyboard that, if accidentally hit, brings up copilot (and maybe sends data to Microsoft), and those keyboards might be banned.
Some companies will probably just deal with it by setting up their PCs so that copilot is disabled and that key does something else. But, other companies will either not be technically savvy enough to do that, or will not want to take a risk of someone accidentally reverting to the default behaviour.
Just from a naming things point of view, that's sad. Much as I dislike Microsoft, and was never interested in Halo, it's fun that one of the voice-assistant things was a nod to a video game character. It's sad to have that replaced by something boring.
I can only speak for my own company, but you're absolutely right, there are severe limits on how we interact with AI and what data can be fed into it.
I also can't imagine any company with their own interest in AI, your Intels, Oracles, Nvidias, Googles, etc. allowing their employees a 1 click access to Microsofts version.
I was going to say, currently working in K12 & this key would be a nightmare for us. We definitely can't pay Microsoft's minimums - disabling/remapping the key wouldn't be hard, but it's obnoxious it becomes a priority.
I really hope startups are using Copilot and stuff as much as possible because so much of that code is absolute bloatware trash and it'll make Copilot worse with time. Or maybe it won't. Would be funny if it did, though.