Microsoft folds two Copilot apps into one, and hands IT the data-boundary question

Microsoft is merging its consumer Copilot app and Microsoft 365 Copilot into a single app that accepts personal, work, or school sign-in, with rollout scheduled to begin in mid-September ^[1][2]. The consolidation cleans up Microsoft's product surface; the two awkward parts, keeping work and personal data apart in one client and covering three retired features, land on IT and on individual users ^[5][6][7][8].

The current arrangement is two apps across Windows, macOS, iOS, Android, and the web: the consumer Copilot app for individuals, and the Microsoft 365 Copilot app for organizations and professional accounts ^[3]. After the merge, users switch between personal and work identities with an account switcher inside Copilot, and Microsoft promises that the two environments stay separate with no data flowing between them ^[4][5]. That promise is the load-bearing element of the whole change, and as reported by ZDNET it is stated as a promise rather than as a described control ^[5]. Anyone running a managed fleet with confidential files now owns the job of confirming what the boundary actually is, because the same binary will be signed into both a corporate tenant and a consumer account ^[4][5].

The retirements are more concrete and land sooner. Group chats stop being accessible after August 18, and any messages, conversations, or images have to be copied into a separate document before then ^[6]. Podcasts go the same way: after August 18 you cannot create new ones or reach ones you already generated, and the only preservation route is downloading them from your library first ^[7]. Deep Research mode disappears on the same date; existing reports stay readable, new ones stop, and the continuation path for in-depth reports is the Researcher tool, restricted to Microsoft 365 Premium subscribers ^[8]. For a team that built any recurring process on Deep Research, the documented replacement is a paid tier ^[2].

August 18 sits roughly four weeks ahead of the mid-September rollout, so users lose capability before the app that replaces it arrives ^[1]. That gap is where support tickets get filed.

The migration mechanics vary by how each person uses Copilot today, which is its own communications problem. Personal-account users on desktop or web move to an updated version, with chat history and "most content" carried across ^[9]. Mobile users have to download an updated app, or in some cases receive it automatically or request it ^[10][11]. People using both apps with a personal account get history and content migrated into the unified app ^[12]. Work and school Microsoft 365 Copilot users see the icon and name change while the experience mostly stays the same ^[13], web users are redirected ^[14], and Microsoft says it will contact customers before rollout begins ^[15]. Paid Microsoft 365 subscribers keep higher usage limits and reach into Word, Excel, Outlook, and their files from within Copilot ^[16]; personal-account users of the Microsoft 365 Copilot app get visual and navigational changes plus Copilot Chat at no extra cost ^[17].

Worth tracking: whether admin controls for the account switcher are documented before mid-September rather than after ^[4][5]; whether the August 18 cutoff holds or slips, since it is the only date requiring customer action ^[6]; how much "most content" excludes in practice ^[9]; and how many helpdesk calls come purely from the taskbar icon and name changing on managed Windows devices ^[13].