What Microsoft is changing

Microsoft will retire Targeted Release for applicable Microsoft 365 services in January 2027. From November 2026, administrators can no longer add users to Targeted Release, remove them or change the existing enrolment.

People already assigned to Targeted Release continue receiving eligible features through that route until retirement. After it ends, their modern release preference determines when they receive new features.

The change applies to services including the Microsoft 365 admin centre, Teams, OneDrive, SharePoint Online, Outlook on the web, New Outlook for Windows and Office for the web. Microsoft 365 Apps update channels, Windows update channels and Microsoft 365 Insider programmes are separate and are not affected by this retirement.

Microsoft: plan for the retirement of Targeted Release

Why businesses and schools used Targeted Release

Many organisations placed IT staff, support teams or a small group of confident users into Targeted Release. They could see certain changes before the wider organisation, prepare guidance and identify support issues.

That early warning can be valuable when a change alters a menu, moves a familiar setting or affects a documented process. Schools may also need to brief teaching and office staff before a visible change reaches everyone.

The retirement does not remove the need for testing. It moves that planning into a new audience based model using Standard, Deferred and Frontier preferences.

Understand the three replacement preferences

Standard Release is the normal default. Users receive features when Microsoft makes them generally available to customers.

Deferred Release gives eligible major features approximately another 30 days after general availability. This can provide time to review the change, update instructions and prepare support before it reaches the wider organisation.

Frontier provides eligible preview features before general availability. It is intended for experimentation, validation and feedback. Preview features can still change, so Frontier should normally be limited to suitable test users rather than applied to everyone without a clear reason.

Not every Microsoft 365 change follows every preference, and release dates remain best effort rather than a guaranteed appointment. Administrators should still review Message centre notices and the Microsoft roadmap.

How to preserve a sensible pilot group

If the organisation previously used Targeted Release for selected users, Microsoft recommends placing the wider organisation on Deferred Release and assigning the validation, support or pilot group to Standard Release. This lets the pilot group receive eligible generally available features before the wider audience.

Frontier can be considered for selected people who genuinely need preview access. It is not a direct replacement that every former Targeted Release user must receive.

Choose named users or managed groups with a clear owner. Include the people who write internal guidance and support colleagues, then review membership as roles change. A pilot group that nobody monitors provides little benefit.

What administrators should check now

Review the current Targeted Release configuration and record which users or tenants were included. Then review the modern release preferences in the Microsoft 365 admin centre. Microsoft currently directs administrators to the release preference controls under Copilot settings, although the exact navigation can change as the unified experience rolls out.

Agree whether the organisation wants new features at general availability, wants extra preparation time for major changes, or needs a small preview group. Update internal support notes that still refer to Targeted Release.

Use an appropriately limited administrator role where possible. Microsoft lists Office Apps Administrator, Security Administrator and AI Administrator among the roles that can work with relevant release settings, while some older configuration steps may still require Global Administrator. Avoid using a Global Administrator account for routine work when a narrower role is suitable.

  • Identify existing Targeted Release users and the reason they were selected.
  • Choose Standard or Deferred Release for the wider organisation.
  • Create a small validation group using Standard Release where useful.
  • Use Frontier only for suitable preview testing and feedback.
  • Review Message centre notices and assign an owner for important changes.
  • Update support documents and tell staff how visible changes will be communicated.
  • Check the preferences again after January 2027 to confirm the intended result.

How Bury I.T. Support can help

Bury I.T. Support Ltd can review your Microsoft 365 release preferences, existing pilot users and change communication process. We can help businesses and schools choose a practical arrangement that gives support staff useful notice without exposing every user to preview features.

We can also review the Message centre, administrator roles and wider Microsoft 365 security settings while the change is being planned. The aim is a controlled transition before January, not a rushed change after familiar menus and features begin appearing at the wrong time.

Official Microsoft guidance was checked on 17 November 2026. Microsoft may refine the admin centre navigation and eligible features, so administrators should check their own tenant notices before making changes.

Official sources and further reading

These primary sources were checked when this article was last reviewed.

Written by

Christopher Lomax

Director of Bury I.T. Support Ltd, with more than 20 years of practical experience supporting business IT, Microsoft 365, networks, servers and cyber security.

About the team