Despite months of public retreat and quiet mea culpas, Microsoft has revived one of its most controversial enterprise IT habits: silently pushing software onto Windows machines without user consent. This time, the target is the Microsoft 365 Copilot app — and the rollout, which began mid-June and runs through mid-July 2026, is set to hit millions of business PCs across the globe.
Déjà Vu in the Admin Portal
In a message buried in the Microsoft 365 admin portal (message center reference MC1152323), Microsoft quietly confirmed that the Microsoft 365 Copilot app will automatically install on eligible Windows PCs that already carry Microsoft 365 desktop apps. The activation requires no interaction from users or administrators. It is, in the company’s own framing, “enabled by default.”
“Starting June 2026, we will resume the automatic installation of the Microsoft 365 Copilot app to eligible devices with the Microsoft 365 desktop apps,” Microsoft stated in the updated admin documentation. The stated rationale: “This change simplifies access to Copilot and ensures users can easily discover and engage with productivity-enhancing features.”
For IT departments that had spent months carefully managing Copilot deployment — blocking it via policy, removing it via registry tweaks, or simply waiting for Microsoft to respect their configurations — this announcement landed like a system update they never approved.
What Gets Installed, and on What
The rollout is not universal. Microsoft specifies that the auto-install targets devices running Microsoft 365 Apps for enterprise or Microsoft 365 Apps for business — subscriptions that come with Word, Excel, PowerPoint, Outlook, Teams, and their cloud-connected backends. Devices running perpetual, volume-licensed versions of Office, such as Office 2019 or Office LTSC editions, are expected to be excluded.
Critically, the European Economic Area is entirely exempted from this wave. This is not coincidental — EU digital market regulations have imposed strict requirements around default software installation and user consent, and Microsoft appears to be threading that needle carefully. For the rest of the world, however, consent appears to be optional.
The mechanism bypasses the Microsoft Store entirely. Instead, Microsoft is routing the installation through the same Office Apps updater that silently handles patches and feature additions across the Microsoft 365 suite. This means that standard enterprise tools for blocking Store installs will not catch it.
A Pattern of Aggressive Defaults
This is not the first time Microsoft has quietly flipped a switch to expand Copilot’s footprint across the enterprise. Earlier in 2026, the company rolled back several Copilot interface elements after sustained user backlash — removing the “Ask Copilot” button from Snipping Tool and the Photos app, toning down the persistent Copilot logo in Notepad, and briefly halting automatic Copilot deployments following enterprise complaints.
That retreat, it turns out, was temporary.
What’s happened since March 2026 is a steady creep. Copilot buttons returned to Word, Excel, PowerPoint, and Outlook ribbons via routine Office updates. A floating Copilot action button appeared — and was then pulled back — in several apps. And now, with the resumption of the auto-install campaign, Microsoft is placing the full standalone Copilot app on business desktops whether administrators asked for it or not.
Critics have pointed out that Microsoft’s controlled vocabulary in these announcements is doing considerable work. Words like “resume,” “eligible,” and “simplify access” obscure what is, functionally, a software installation that happens without user action and requires organizational effort to prevent. The opt-out is real — but it must be actively located, configured, and applied before the deployment window closes.
How Admins Can Fight Back
Microsoft has provided a formal opt-out path, but it is deliberately not the path of least resistance. Enterprise administrators who want to block the Copilot app install must navigate to the Microsoft 365 Apps admin center, locate Customization > Device Configuration > Modern Apps settings, and toggle off the Microsoft 365 Copilot app option before devices in their organization are reached by the rolling deployment.
For users who prefer per-app approaches, Microsoft does offer Copilot toggles within individual Office applications. In Word, Excel, PowerPoint, and OneNote, navigating to File > Options > Copilot and unchecking “Enable Copilot” disables the integration for that application. Outlook requires a separate setting and, notably, Microsoft has not yet provided an equivalent toggle for Outlook Classic for Windows, with no estimated delivery date given.
Group Policy provides a deeper lever. IT administrators with access to Microsoft’s Office ADMX templates can disable connected experiences across Office apps via User Configuration > Policies > Administrative Templates > Microsoft Office 2016 > Privacy > Trust Center, setting *Allow the use of connected experiences in Office that analyze content* to Disabled. This does not prevent the Copilot app from being installed, but it does block many of its functional entry points from activating.
For personal Microsoft 365 subscribers, Microsoft has made available a “Classic” plan without Copilot in select regions. Users in the United States who cancel their current subscription may be offered this alternative during the cancellation flow — though availability is inconsistent.
The Consent Problem Microsoft Won’t Acknowledge
What makes this deployment strategy particularly contentious is not the software itself but the philosophy it embodies. Microsoft’s framing consistently treats Copilot presence as the default state and non-adoption as an administrative preference requiring active management. Users and organizations must opt out; they are never asked to opt in.
This is especially fraught in enterprise environments. IT teams that manage fleets of thousands of Windows PCs now face a narrowing window to configure the block, educate end users on what appeared on their machines, and field help desk tickets from employees confused about a new app they didn’t request. For organizations in regulated industries — healthcare, finance, legal — the sudden appearance of an AI-connected application raises immediate questions about data handling, compliance posture, and audit trails.
Microsoft’s decision to exempt the EEA while proceeding with the rest of the world also implicitly acknowledges that this deployment model would not survive regulatory scrutiny in markets with robust digital consent requirements. Whether other jurisdictions will take note remains to be seen.
What Comes Next
Microsoft 365 Copilot’s forced installation rollout is scheduled to complete by mid-July 2026. After that, the app will be present on eligible machines unless manually removed or proactively blocked.
Given the company’s track record in 2026 — including force-upgrading Windows 11 PCs to version 25H2 ahead of the 26H2 release, killing Edge features in favor of Copilot integration, and folding AI entry points into virtually every surface of its productivity suite — this deployment is unlikely to be the last of its kind. The question for enterprise IT departments is not whether the next forced integration is coming, but how much lead time they will have to prepare for it.
For now, Microsoft’s message to its enterprise customers is clear: Copilot is coming, whether you invited it or not.
