Targeted release locks in November: rebuild your M365 pilot group

What Microsoft is changing

Microsoft will retire Targeted release for Microsoft 365 services in January 2027, and the first hard step falls this month. Microsoft's retirement guidance says administrators can't add users to Targeted release, remove them or change enrolment in any way from November 2026. Microsoft hasn't published an exact day for the freeze. Any tenant that still relies on Targeted release should assume the setting could lock any day now. The Message center notice MC1490899 went out on 7 October with an act-by date of 31 October, and plenty of small IT teams won't have got to it in time.

For years Targeted release has been the usual way to give a small group of staff new Microsoft 365 features before everyone else. That group worked as an early warning for the service desk. Its job now passes to three audience-based release preferences. Standard release is the default and delivers features once they're generally available. Organisations that want more time to prepare can switch some or all users to Deferred release, which holds back eligible major updates for roughly 30 days after rollout to the Standard audience begins. Microsoft's configuration guide, updated on 3 November, sets this out, and Frontier sits alongside both as an opt-in preview program. Windows Report covered the Message center post and reported the same timeline.

Why the service desk should care

The change applies to Teams, OneDrive, SharePoint Online, Outlook on the web, the new Outlook for Windows, Office for the web and the Microsoft 365 admin center. Microsoft 365 Apps update channels and Windows update channels aren't affected, according to the retirement guidance. Desktop Office patching stays as it is. The browser and Teams changes behind most "where did that button go?" calls move to the new model.

Microsoft's own definition of a major update shows why ITSM teams should pay attention. The list in the configuration guide covers changes to inboxes, meetings, delegation and sharing "that might result in help desk calls". Deferred release can hold those updates back, and a Targeted release pilot group used to catch them early. An organisation that does nothing will see its Targeted release users switch in January to whatever general availability preference the tenant already has, Standard or Deferred. Nobody will have actually decided that, and the service desk will find out from the first confused caller.

Deferred release has its own catch. Microsoft warns that users moved from Standard to Deferred may lose access to features that haven't reached Deferred yet. A careless reassignment can therefore cause the very calls it was meant to prevent. Updates that aren't eligible for deferral still arrive on the Standard schedule, so Deferred release slows the bigger visible changes and leaves the rest of the release stream untouched.

Frontier needs a separate decision. Under MC1529472, published 28 October, Frontier expands this month beyond Copilot to public previews in Teams, the new Outlook, OneDrive and SharePoint. Frontier is off by default, and enrolled users need licences for the products they're previewing. Microsoft's comparison table describes Frontier features as preview, subject to change and outside general availability SLAs. An IT team testing changes on behalf of the business is a sensible Frontier audience. A payroll team in the middle of year-end processing is a poor one.

What it means for NZ organisations

Many NZ businesses run a small internal IT team or depend on a managed service provider. In those setups, Microsoft 365 release decisions often live in one person's memory rather than in a documented process. The retirement exposes that gap. Microsoft is moving the release controls themselves: the current Standard and Deferred settings sit under Copilot > Settings and will be retired when a unified release preferences page appears in November. The guidance says Microsoft will update its documentation with the new navigation, so any internal runbook that points to the old screens will soon be wrong.

Timing makes things harder for NZ teams. Targeted release retires in January, when many organisations are coming back from the summer break with thin IT and MSP cover. Microsoft hasn't published the January date. With a 30-day deferral, a major change that reaches Standard over the Christmas shutdown would land for Deferred users in late January, when staff are back and busy. Deferral gives the service desk time to prepare only if someone actually uses the window to write knowledge articles and brief users.

In ITIL 4 terms, the retirement is a release management and change enablement decision, and the business should make it on purpose. Teams that already run a light change process can fold Microsoft 365 release preferences into it. Teams without one could use this deadline to set one up, and our ITIL 4 framework page outlines how we approach those practices.

Practical next steps

• Record current Targeted release assignments now. Look under Settings > Org settings > Organization profile > Release preferences and export the list before enrolment locks. Once the freeze applies, you won't be able to edit that list.
• Choose the general availability default on purpose. Microsoft's mapping table suggests Standard or Deferred for tenants that had Targeted release for everyone. For tenants that used Targeted release for selected users, it suggests Deferred for the organisation with pilot users added as Standard exceptions.
• Rebuild the pilot group as a security group. Create a Microsoft Entra ID security group with IT staff, service desk agents and a few experienced users from each business unit, then assign the group to Standard. You can add up to 10,000 exceptions, and changes can take up to 24 hours to apply.
• Check admin roles. Configuring Standard and Deferred release requires the Office Apps Admin, Security Admin or AI Admin role. Make sure the person or MSP doing the work holds one of them.
• Make a separate, narrow Frontier decision. Enrol named testers only, and write down who's in Frontier so the service desk knows which callers may see preview features.
• Route Message center into change management. Filter for posts tagged "Major update" and "Deferred feature", log them, and use the 30-day deferral to prepare knowledge articles and user notices.
• Update documentation and contracts. Replace references to Targeted release in runbooks, onboarding guides and MSP service descriptions, and ask your provider in writing which release preferences they've set for your tenant.
• Plan January cover. Make sure someone can triage Microsoft 365 change calls in the weeks after the retirement, even if the rest of the team is still on leave.

The work is small if you start now and gets messy once enrolment is locked. If you'd like help bringing Microsoft 365 release decisions into a wider service management process, see our digital transformation services.