Microsoft has confirmed it will once again push the Microsoft 365 Copilot application onto Windows PCs automatically, starting in mid-June 2026. The phased rollout, running through mid-July, will land on devices that already run commercial versions of Microsoft 365 desktop applications. This move rekindles the debate over unsolicited software installations, as IT administrators scramble to prepare for the potential impact.
The Microsoft 365 Copilot app, distinct from the consumer-facing Copilot discovered in Windows 11 and Windows 10, is designed to serve as an AI assistant within the Office suite. It integrates with Word, Excel, PowerPoint, Outlook, and Teams, offering generative capabilities powered by large language models. For organizations that have licensed Microsoft 365 Copilot subscriptions, the app enables features like summarizing documents, drafting emails, and analyzing spreadsheets directly from the desktop. However, its automatic deployment to machines where it may not be licensed or desired has drawn sharp criticism.
A Repeat of History
This is not the first time Microsoft has attempted to auto-install the Copilot app. In early 2024, the company began a quiet rollout of the Microsoft 365 Copilot sidebar across Windows 10 and 11 devices, only to pause the process after backlash from enterprise customers. Many IT departments reported finding the app suddenly pinned to the taskbar, consuming storage and creating confusion among users who were not provisioned for the service. Microsoft later promised to refine its deployment criteria, but the upcoming 2026 push suggests a renewed commitment to gaining a foothold on business PCs.
According to Microsoft’s latest advisory, the auto‑install will target Windows 10 and Windows 11 machines that are entitled to Microsoft 365 Apps for enterprise (formerly Office 365 ProPlus) or Microsoft 365 Apps for business. Devices running volume‑licensed, perpetual versions of Office (such as Office 2019 or Office LTSC) are expected to be excluded. The company is also carving out exceptions for systems that are managed through Microsoft Intune and have the “Do not download the boxed version” policy configured, as well as those enrolled in Windows Update for Business with specific feature deferral settings.
Rollout Mechanics
The new Microsoft 365 Copilot app will be delivered as a separate package via Windows Update, much like the PC Manager or the Windows Backup app that preceded it. It will appear in the Apps & features list under a distinct entry, and its icon will be pinned to the taskbar by default on new devices or after a feature update. The installation is triggered by the presence of any Microsoft 365 subscription-based desktop application, even if the organization has not purchased Copilot licenses. When opened by an unlicensed user, the app displays a “Get Copilot” screen with subscription prompt, adding to the frustration of having unwanted software on corporate devices.
The rollout begins on June 15, 2026, and will expand gradually over a four‑week period, concluding by July 15. Microsoft has indicated that the deployment will apply to the Monthly Enterprise Channel, Semi‑Annual Enterprise Channel, and Current Channel versions of Microsoft 365 Apps, though users on the Semi‑Annual channel may receive it later within the window.
IT Administrator Actions
For IT professionals, the main question is how to stop the automatic installation. Microsoft provides several levers:
- Group Policy: The policy “Do not install Microsoft 365 Copilot” is now available under Administrative Templates → Microsoft 365 Apps → Managed. Enabling this policy prevents the app from being installed alongside the Office suite.
- Intune: The same policy can be deployed via Intune device configuration profiles, applied to all managed endpoints.
- Microsoft 365 Apps admin center: A new toggle labelled “Block Microsoft 365 Copilot app installation” appears under Customization → Device Configuration.
- Registry key: Manually setting
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Common\OfficeUpdate\BlockCopilotInstallto 1 stops the installer. - Uninstall after the fact: If the app already lands, administrators can silently remove it using the command line:
"%ProgramFiles%\WindowsApps\Microsoft.MicrosoftOfficeHub…\AppPackage\Uninstaller.exe"or via PowerShell scripts.
It is critical to configure these blocks before mid‑June, as machines that receive the app before a policy is applied will need to be cleaned up post‑deployment.
For ease of reference, the following table summarizes the primary blocking methods:
| Method | Configuration |
|---|---|
| Group Policy | Enable "Do not install Microsoft 365 Copilot" under Administrative Templates → Microsoft 365 Apps → Managed |
| Intune CSP | Set ./Device/Vendor/MSFT/Policy/Config/Office/BlockCopilotInstall to 1 |
| Registry | Create DWORD BlockCopilotInstall = 1 under HKLM\SOFTWARE\Policies\Microsoft\Office\16.0\Common\OfficeUpdate |
| Apps admin center | Turn on the "Block Microsoft 365 Copilot app installation" toggle in Customization → Device Configuration |
End‑User Experience
Users who are not licensed for Copilot will see a new icon on their taskbar—a multicoloured ribbon resembling the Copilot logo. Clicking it opens a chat interface that invites them to upgrade. The app cannot be uninstalled by standard users; only administrators can remove it, adding to helpdesk burden. For licensed users, the app becomes a hub where they can access Copilot features across Office applications. It also surfaces prompts for “Microsoft 365 Copilot Chat,” the free tier introduced in late 2025, which offers limited interactions without a full subscription.
On the positive side, organizations that have embraced Copilot may welcome the streamlined installation, as it removes the need to package and deploy the app manually. But for the many businesses still evaluating AI copilots or those with licensing restrictions, the forced nature of the rollout is a headache.
The app adds about 250 MB to the installation footprint and registers a background service that runs at startup. While negligible on modern hardware, it can further clutter the taskbar and Start menu on devices already crowded with Office, Teams, and other line-of-business tools.
Industry Reaction and Compliance Concerns
System administrators have expressed frustration on online forums and social media. “Microsoft just doesn’t learn,” wrote a Reddit user on r/sysadmin. “We blocked the previous attempts via GPO, but now we have to revisit every policy because they keep changing the blocking mechanism.” Others worry about software compliance: having the Copilot app installed on a device may trigger licensing audits from Microsoft, even if the user never invokes it. Microsoft has not explicitly addressed this concern, but its official documentation states that merely installing the app does not consume a Copilot seat.
Financial analysts note that the aggressive push is part of Microsoft’s strategy to drive adoption of Copilot subscriptions. As AI features become a key differentiator, the company wants to ensure the app is visible on every business desktop. “The auto‑install is essentially a billboard for Copilot,” said one industry observer. “Even if only a fraction of users click the pitch, the subscription revenue uplift can be substantial.”
From a regulatory standpoint, the forced installation treads close to the same bundling practices that have drawn scrutiny from European Commission and other antitrust bodies. Microsoft’s previous integration of Teams into Office gave rise to a formal investigation; now, Copilot’s automatic presence may invite similar questions if competitors argue it unfairly leverages the Office monopoly.
What Makes This Time Different?
Compared to earlier, botched attempts, Microsoft appears to be giving administrators more advanced warning and ready-made tools to control the deployment. In 2024, the GPO to block the app only materialized weeks after the rollout began, leaving many organizations scrambling. Now, with the policy already published and documented, IT teams have a fighting chance to prepare. Additionally, the phased nature of the rollout—a full month—means that early adopters can serve as canaries for the rest of the fleet.
Nevertheless, past experience suggests that even well-intentioned blocklists can break after a later Office update changes the detection logic. Administrators should therefore not rely on a single blocking method; a defense-in-depth approach combining GPO, Intune, and registry settings is recommended.
Broader Context: The AI Operating System
The June–July 2026 rollout is just the latest chapter in Microsoft’s evolving AI strategy. With Windows 12 expected later in 2026 to embed Copilot even deeper into the operating system, IT departments must establish robust governance for AI‑enabled applications. The line between OS features and optional apps continues to blur, and administrators will need to stay vigilant as Microsoft expands the kinds of software delivered automatically via Windows Update.
Copilot’s automated presence on the desktop reflects a broader industry trend: AI is being transformed from an on-demand service into an ambient, always-available utility. Google’s Duet AI for Workspace takes a similar approach, but its deployment is generally opt-in through admin consents. By comparison, Microsoft’s push model is more aggressive, arguably because the company believes that habit formation requires an icon on the taskbar.
For organizations already invested in the Microsoft 365 ecosystem, the Copilot app can be a launchpad for exploring generative AI’s productivity benefits. It connects not only to Office files but also to external data sources via Microsoft Graph connectors, turning natural language queries into actionable insights. However, the automatic installation of a tool that requires a separate, often costly subscription does little to foster goodwill among budget-conscious IT departments.
Preparing for June 15
The immediate priority for IT teams is to audit existing environments, identify at‑risk devices, and deploy the blocking policies before the deadline. A quick script can check the current policy state across a fleet; Microsoft provides sample PowerShell cmdlets in its tech community blog. Those who want to allow the app for pilot users can also selectively exclude certain machines from the block, using device groups in Intune or organisational units in Active Directory.
Helpdesk teams should be briefed on what to expect and given a prepared script for calming users who call about the mysterious new icon. A simple internal communication stating “You may see a new Copilot icon—it is not a security threat, but you do not need to use it unless you have been issued a license” can prevent panic.
As the rollout nears, Windows News will provide step‑by‑step guides, deep dives into the policy configurations, and coverage of any last‑minute changes from Microsoft. In the meantime, administrators can consult the following official resources (links to be updated as they become available):
- Microsoft Tech Community blog: “Manage Microsoft 365 Copilot app installation”
- Microsoft 365 admin center documentation
- Group Policy reference for Office 2026
June 15 is just around the corner. For the millions of business Windows PCs out there, the countdown has begun.