Microsoft 365 Apps on Windows 10 frozen: build 2608 is the last feature version — three deadlines by channel

Windows 10 reached the end of mainstream support in late October 2025. Microsoft 365 Apps continued to run on those devices in most organisations, which gave many IT teams reason not to treat the Windows 11 migration as urgent. That reasoning no longer holds. From August 2026, build 2608 is the last version of Microsoft 365 Apps to receive new features on Windows 10 devices — with enterprise channel deadlines following in October and January.

After the respective channel date, the Office apps remain fully functional and continue to receive security updates until October 2028. What stops is all new feature delivery — including every new Copilot integration Microsoft releases afterwards. Users on Windows 10 stay on the same version as the day of the freeze, while colleagues on Windows 11 receive new capabilities every month.

What a feature freeze means in practice

The term feature freeze sounds technical, but the practical consequences are concrete. Word, Excel, PowerPoint, Outlook, and the rest of the M365 suite remain open, saving, and collaborating. Existing Copilot functionality already on the device stays available. Everything Microsoft releases afterwards, the device misses. That includes new Copilot Agents, improved writing assistance in Word, more advanced Excel analysis, Teams extensions, and all other improvements released after the channel date.

The consequence is that employees on Windows 10 increasingly fall behind the rest of the organisation. A manager on Windows 11 can activate a new Copilot agent; an employee on Windows 10 simply does not see that option — even if the organisation has the right licence. In internal collaboration around new features, or in client conversations about AI productivity, the gap becomes noticeable.

Three channel deadlines you need to know now

The freeze applies per update channel, not to all devices simultaneously. This gives organisations on slower channels more preparation time, but also the risk of letting the date pass without action.

Current Channel, used frequently by individual subscribers and smaller business environments, is the first to be hit. The freeze is active in August 2026. For anyone following this channel, build 2608 is already the last feature version.

Monthly Enterprise Channel, the default channel for business Microsoft 365 customers who receive monthly updates, has a deadline of 13 October 2026. That coincides with the first Patch Tuesday of October. IT teams on this channel have until then to form and begin executing a plan.

Semi-Annual Enterprise Channel, the channel for organisations that want stable, delayed updates, reaches the freeze on 12 January 2027. Later, but this channel also requires action: a Windows 11 migration takes time and devices eligible for upgrade need to be identified before the date approaches.

Which features will users miss after the freeze?

The most visible consequences sit in Copilot. Microsoft releases new Copilot capabilities across all Office apps with every major update cycle. Everything released after the channel date is unavailable on Windows 10 — even if the organisation has an M365 Copilot licence. The licence remains active and the backend works, but the client does not support the new functionality.

Beyond Copilot, users also miss regular UX improvements, new options in OneDrive and SharePoint sharing menus, performance improvements that depend on newer Windows APIs, and adjustments to the calendar integration between Outlook and Teams. Individually these are modest changes, but over two years they accumulate into a noticeable difference in the daily working environment.

Which devices in your environment are affected?

In Microsoft Intune this is straightforward to map. Filter the device overview by operating system version Windows 10 and combine that with Microsoft 365 Apps version information via Microsoft 365 Apps Health in the Intune admin centre. Devices already running build 2608 or higher are already frozen or approaching the threshold.

In larger environments, Windows 10 is often more prominently represented than expected — in production environments, meeting rooms, reception desks, or with employees whose older hardware did not receive upgrade priority in earlier rounds. The report reveals the true scale of the issue.

Upgrade or replace: how do you decide per device?

Windows 11 sets hardware requirements that not all Windows 10 devices meet. Minimum requirements include a TPM 2.0 chip, UEFI Secure Boot, an Intel Core eighth-generation or newer processor, or an AMD Ryzen second-generation or newer. Devices older than 2018 almost never meet those requirements in practice.

Use the Windows 11 Compatibility Assessment in Intune or the Microsoft Endpoint Analytics dashboard to determine per device whether a Windows 11 upgrade is technically possible. Intune reports per device which blocking element prevents the upgrade, letting you directly distinguish between hardware that can be updated in software and hardware that must be replaced.

For devices that are compatible, Intune provides full support for an admin-driven upgrade via Feature Update Policies in Windows Update for Business. A phased rollout — with departments most dependent on the upgrade going first — limits operational impact and keeps fallback scenarios manageable.

Four steps for the coming weeks

As a first action, produce a device report: how many Windows 10 devices are there, which update channel do they follow, and which build are they on now? This establishes the urgency and gives direction to the planning.

Next, run the compatibility check and split devices into three groups: upgradeable to Windows 11, to be replaced, and exceptions that require a specific approach. Make this overview available to management and budget holders so that replacement hardware can be scheduled in time.

Then draw up an upgrade schedule per department, based on dependence on new Copilot features and operational risk. Departments that make intensive use of Word and Excel for analysis or reporting benefit most from new AI capabilities and deserve priority.

Finally, plan the replacement of incompatible hardware. Allow for lead times of two to three months and for budget cycles. Organisations that wait until after the channel deadline risk having to procure new hardware and run a rolling upgrade simultaneously — placing unnecessary pressure on the IT team.

The feature freeze on Windows 10 calls for a plan, not panic. Organisations that map out now how many devices are involved and what step each of those devices needs will prevent users from working with frozen productivity tools in 2027 while the rest of the market continues to evolve. Want support in inventorying your Windows 10 device fleet, planning a Windows 11 rollout, or assessing which hardware needs replacement? Contact Zarioh for a no-obligation analysis of your current situation.