![The Microsoft Copilot Bible: [3 in 1] A Beginner's Guide to Harness AI in Office 365 to Automate Workflows, Generate Content, Analyze Data, and 10x Your Productivity](https://m.media-amazon.com/images/I/6137D0WO3TL._AC_UY218_.jpg)
Microsoft 365 Copilot App Updates: IT and Employee Guide
Microsoft's Microsoft 365 Copilot app now goes by a different name: Microsoft Copilot. That's not just cosmetic. As part of the same round of Microsoft 365 Copilot app updates, Microsoft is merging existing Microsoft Copilot and Microsoft 365 Copilot installations into one client on managed Windows and Mac devices, and the company said broad rollout to commercial customers would begin in September, according to Microsoft Learn, published last month.
That single fact creates two different jobs. IT admins need to review rollout policy with September's start date in mind, while employees on managed devices need to know what they can and can't control once the app on their machine updates. This article treats those as separate questions rather than one shared checklist.
The scope is narrower than it might sound. This unification mechanism covers managed Windows and Mac devices specifically. Mobile apps go through separate Intune deployment guidance, and Microsoft's own documentation states that "your experience is the same" even as unrelated chat and Outlook features ship in the same window (Microsoft Learn; Microsoft 365 Copilot release notes).
Which managed devices get the unified Microsoft 365 Copilot app experience
Microsoft's deployment guidance describes organization-managed Windows and Mac devices as the target for this rollout and lays out the policy process for reaching them (Microsoft Learn). Phone and tablet deployment runs through separate Intune-based articles, so mobile users aren't part of this specific rollout mechanism (Microsoft Learn).
Microsoft's documentation doesn't explain how unmanaged personal devices or consumer accounts outside an organization's Entra ID setup will be handled. That question stays open in the guidance supplied here, so a personal device shouldn't be assumed to follow the same rollout path as a managed one.
A secondary outlet frames the broader change differently, describing it as folding Word, Excel, PowerPoint, Outlook, cloud files, and custom agents into a consumer and enterprise "super app," and reports that Microsoft planned to retire Group Chat, Podcasts, and Deep Research around the same time (Secure Bulletin, reported last month). None of that appears in Microsoft's own documentation supplied here. It reads as one outlet's characterization of Microsoft's broader direction, not a confirmed feature retirement, until Microsoft's release notes say otherwise.
For IT admins: what to configure before September's rollout
Microsoft said broad rollout to commercial customers would begin in September (Microsoft Learn), so organizations that haven't reviewed their deployment settings should treat this as a review to complete now, not a task to defer.
Three controls determine when a managed device actually receives the updated app:
- Preview or delay control. Enabling the Copilot Unification Allowed policy lets admins decide when devices receive the updated app. If AutoUpdateCheckPeriodMinutes is set to 0, previewing the new app is blocked entirely, so confirm that setting before assuming a delay is already in place.
- Manual versus progressive rollout. Once Microsoft begins the broad rollout, admins can manage deployment manually or let Microsoft handle it progressively by enabling the Updater Experimentation And Configuration Service Control policy.
- Automatic download risk. If neither approach is configured, devices with an existing Copilot app may download the update automatically as Microsoft works through the rollout. Admins who need more time on Windows devices specifically can set the Pause Copilot App Unification Rollout registry key, which Microsoft's guidance describes as a Windows control.
Network access matters in the same pass. copilot.cloud.microsoft needs to stay unblocked, and Microsoft says it plans to consolidate Copilot traffic under the broader *.cloud.microsoft domain, a future simplification rather than something already in effect (Microsoft Learn, published earlier this month).
Beyond rollout policy, Microsoft's admin guidance names several license and configuration checks that apply to Copilot generally, not to this app merger specifically (Microsoft Learn, published earlier this month):
- Review Microsoft 365 Apps privacy settings, which Microsoft's setup guidance lists as standard configuration for any Copilot deployment.
- Confirm update channel settings, since Microsoft's licensing guidance recommends reviewing them in the same admin pass (Microsoft Learn, published earlier this month).
- Check whether Microsoft 365 Apps for enterprise deployments use device-based licensing. Microsoft's requirements page states Copilot isn't available under that licensing model, regardless of app name.
- Verify third-party cookies are enabled in the browser for any user who relies on Copilot inside Word Online, Excel Online, or PowerPoint Online.
None of those four items trace back to the unification itself. They're prerequisites that can block Copilot access no matter which app name shows up on a user's desktop, which makes them worth confirming in the same session as the rollout policies above rather than as a separate project.
For employees on managed devices: what to check
Microsoft frames the rollout controls as settings organizations configure, not options built into an individual account, so the timing on a given device depends on how IT has set it up rather than anything a user can toggle (Microsoft Learn).
Employees can still verify a few things once the app updates:
- Confirm whether the device is organization-managed or personal.
- Check which account is signed in after the update lands.
- Note the Work IQ toggle's current state rather than assuming it.
- Ask IT whether a specific feature, like the AI SKU search pane, is enabled for the account's license.
A few access rules apply regardless of the rename. A Microsoft 365 license must be assigned to the account, and Microsoft points to a specific list of eligible base licenses rather than treating every Microsoft 365 subscription as automatically qualifying. A Microsoft Entra ID sign-in is also required, and Copilot support covers primary Exchange Online mailboxes only, not archive, group, or shared and delegate mailboxes (Microsoft Learn, published earlier this month). These prerequisites predate the merger, so a missing feature more likely traces to licensing than to anything the rename changed.
Secure Bulletin raised additional concerns worth tracking: identity switching between personal and work accounts on shared devices, and a call to re-validate data loss prevention rules and agent permissions against the unified interface (Secure Bulletin, reported last month). Microsoft's supplied documentation doesn't address either scenario, so these stay open questions rather than confirmed problems.
Separate Microsoft 365 Copilot changes shipping the same month
A few feature changes are listed in the release notes for this same window, but Microsoft documents them as ordinary product updates, not consequences of the app unification (Microsoft 365 Copilot release notes, published earlier this month).
Web and work chats are now unified into one interface, with a Work IQ button in the top-left of Chat that switches access to work data on and off. Microsoft's release notes don't specify Work IQ's default state or whether organizational policy can override it, so users should confirm those details with an administrator before treating the toggle as a privacy boundary rather than an access switch.
The right-hand Copilot Chat pane inside Copilot Search is documented as available to users with the AI SKU. That's one named licensing gate for that specific pane; the release notes don't rule out other requirements tied to a broader Microsoft 365 Copilot license, so a missing pane doesn't necessarily point to a problem beyond the SKU itself.
Admins should treat the unification policy, update channel, privacy settings, licensing mode, and endpoint access as one review to complete now, since September's rollout timing runs on each organization's own configuration rather than a fixed switch-flip date. Employees on managed devices can't choose that timing themselves. Once the app changes, the useful move is checking the signed-in account and flagging any missing feature to IT rather than assuming the rename touched permissions. Work IQ, in particular, should be treated as an access toggle until Microsoft's release notes spell out its default state and whether policy can override it, not as a documented privacy guarantee.
Comments
Be the first, drop a comment!