Microsoft is combining the consumer Copilot and Microsoft 365 Copilot apps into one interface. Personal and work accounts will share one app while chats, content and security boundaries remain separated by account type. The updated product uses the Microsoft Copilot name. Consumer and commercial assistants will appear in one app. The checked account from The Verge supports those points through reporting, records, or clearly attributed statements. Claims by governments, companies, police or participants remain identified as claims unless the source record independently verifies them.
Mobile and web rollout starts in mid-August. Windows and Mac rollout is planned for mid-September. Existing chats and content will migrate. Microsoft says enterprise security, compliance and government controls will not change. Together, those details establish what changed by the edition deadline. They do not convert an early estimate into a final count or a stated intention into a completed result. Later records may refine dates and quantities without erasing the confirmed core.
A unified shell can still preserve separate identity and storage domains. Migration quality matters as much as the new interface. Free capabilities remain, though usage limits may differ. This context explains the institutions, systems and constraints surrounding microsoft begins combining its copilot apps. It also keeps causation separate from correlation and prevents a broad trend from being used as unsupported proof about one event.
The rollout had not yet demonstrated migration reliability or data-boundary behavior at scale. The next documentary tests are user reports during the staged rollout and documentation and audits of account separation. Until those records appear, the responsible account is bounded: report the verified development, preserve attribution, state the unknowns and avoid filling gaps with a plausible but unproven narrative.