Almanac
Microsoft/copilotMicrosoft 365

Consultant KB for the whole Microsoft Copilot estate. Spans Microsoft 365 Copilot, Copilot Studio, the Dynamics 365 Copilots, Power Platform Copilot, Fabric & Power BI Copilot, Copilot in Azure, Windows & consumer Copilot, extensibility & agents, Security Copilot, and GitHub Copilot, plus admin/security and cross-product decision guides. Populated by the daily author agent from Copilot release notes / release plans plus the author's own consultant notes.

feature-microsoft-copilot-consumer-app.mdv1 · history
CurrentApplies to Windows / ConsumerUpdated 2 months agoSource blogs.microsoft.com

What it does

The consumer Microsoft Copilot is the personal-account AI companion at copilot.microsoft.com and in the Windows, iOS, and Android apps. It does chat, voice, screen and camera Vision, a Pages canvas, and remembers things about you across sessions.

Key facts

  • Reached through a personal Microsoft account on the web, the Windows Copilot app, or the mobile apps; the same account carries your history and memory across them.
  • Copilot Voice offers a set of natural voices for spoken back-and-forth, useful hands-free or on mobile.
  • Vision on the consumer app works from your phone camera or shared screen, analysing live video or photos to guide you step by step.
  • Pages turns notes and Copilot output into a structured, editable canvas you can keep refining.
  • Memory (consumer) lets Copilot retain personal details, favourite foods, hobbies, dates, to personalise replies; it's user-controllable and you can wipe or opt out.
  • Podcasts-style audio generation turns a topic or your interests into a spoken segment.
  • It's built on personal-account consumer terms: prompts here are not covered by an organisation's commercial data protection.
  • Feature rollout is staggered by region and platform, so mobile, Windows, and web don't always match.

When to use / skip

Good for personal productivity, learning, and casual creative work on someone's own account. Genuinely useful to demo so a client understands what their staff are already using at home. Skip it for anything touching company data: there's no tenant grounding, no admin governance, and no commercial data protection. If a client's users are pasting work content into the consumer app, that's a finding to raise, not a workflow to bless.

Configuration decisions

  • Decide, at policy level, whether the consumer app is even allowed on corporate devices, or blocked in favour of the work experience.
  • If users keep it for personal use, set expectations that work data must not go in.
  • Choose whether consumer Memory is acceptable on shared or corporate-adjacent machines, given it builds a personal profile.
  • Work out sign-in hygiene so people don't accidentally use a work account where a personal one is intended, or vice versa.

Gotchas

  • The consumer app and Microsoft 365 Copilot can look almost identical but sit on completely different data terms; the account badge is the tell.
  • Consumer Memory is on by default once available and personalises silently; users who don't know it exists may be surprised by what it recalls.
  • Vision and Voice feel casual, which makes it easy for users to share screens or read out content they shouldn't.
  • Nothing a user does in the consumer app appears in your tenant's audit, DLP, or compliance tooling.
  • Because features roll out unevenly, a capability a client saw in one place may be missing in another, prompting support noise.

Consultant notes

  • Treat this as the shadow-IT surface of the Copilot family: users adopt it themselves, so the conversation is governance and awareness, not deployment.
  • The single most important distinction to teach a client: personal Microsoft account equals consumer terms and no commercial data protection; Entra work account with a licence equals the protected experience.
  • If staff like the consumer Voice and Vision, that's a signal they'd value the same in the governed Microsoft 365 Copilot, use it to build the business case.
  • Consumer Memory is a privacy talking point worth flagging in any awareness training you run.

Confirm which consumer features have reached the client's region and platform before you demo; the rollout gaps trip people up.

Was this accurate?