What it does
Copilot in Windows is the in-OS assistant that ships as an app on Windows 11. It handles chat, voice, and screen-aware help, and on Copilot+ PCs it ties into on-device features like Click to Do and screen translation.
Key facts
- Copilot on Windows is now a standard app (updated through the Microsoft Store), not the old docked sidebar that Microsoft retired.
- The Copilot key on newer keyboards launches the app; without one, Win+C opens a lightweight prompt box. On managed devices Win+C can be pointed at Microsoft 365 Copilot Chat instead.
- "Hey Copilot" wake-word voice activation and Copilot Vision on Windows are both live; Vision can see open app and browser windows and walk you through a task, with Highlights pointing to where to click.
- Vision on Windows runs in 170+ markets through the app, and a taskbar share-screen button makes handing it your screen quicker.
- Click to Do is a Copilot+ PC feature (Windows key + trackpad click, or Win+Q) that acts on text and images on screen, including on-screen translation.
- Click to Do and other Copilot+ features need the NPU-equipped hardware; they don't appear on ordinary Windows 11 PCs.
- Signed-in behaviour splits by account type: a personal Microsoft account gets consumer Copilot; an Entra work account with the right licence gets the protected commercial experience.
When to use / skip
Fine for a client's users who want quick on-screen help, voice queries, or Vision-guided walkthroughs on their own kit. Skip it as a serious productivity story for the enterprise: the in-Windows app is not the same as Microsoft 365 Copilot grounded on tenant data, and the flashier bits (Click to Do, Recall-adjacent features) are gated behind Copilot+ hardware. For managed fleets, treat the app as something to govern, not deploy.
Configuration decisions
- Decide whether Win+C launches consumer Copilot or Microsoft 365 Copilot Chat on managed devices, and set the policy to match your licensing.
- Choose whether "Hey Copilot" wake word and Vision screen-sharing are allowed on corporate devices, or turned off via policy.
- On Copilot+ fleets, decide if Click to Do and screen translation stay on, and how that sits with your data-handling stance.
- Pick which account users sign Copilot in with, because that single choice decides consumer vs commercial data protection.
Gotchas
- A personal Microsoft account in the Windows Copilot app means consumer terms apply, even on a corporate laptop, so prompts can be outside your commercial data protection boundary.
- Click to Do, Recall, and other headline Copilot+ features only exist on NPU hardware; don't promise them on standard PCs.
- The app updates through the Store on its own cadence, so what a user sees can drift ahead of your documentation.
- Vision needs the user to actively share a window; it isn't silently watching the screen, but users often assume the worst, so set expectations.
- Feature availability varies by market and by Insider channel, so a demo build may show things your client's stable build doesn't.
Consultant notes
- The cleanest lever you have is account type: commercial data protection follows the signed-in Entra account, not the device, so govern sign-in first.
- For a client worried about screen capture, separate the always-on fears from reality: Vision is opt-in per session, but Copilot+ Recall is the feature to actually scrutinise in a data-protection review.
- If the client already has Microsoft 365 Copilot, position the Windows app as the convenience front door, not the value driver.
- Check hardware before scoping any Copilot+ dependent work; the AI PC marketing blurs which features need the NPU.
Re-check Win+C routing and Vision availability against the current Store build before you brief a client; this app moves fast.