Targeted Release retires from Microsoft 365 in January 2027: Frontier, Standard or Deferred?

What changes between November 2026 and January 2027

On October 7, 2026, Microsoft confirmed the retirement of Targeted Release in Microsoft 365. Assignments are frozen in November 2026 and the mechanism disappears in January 2027. The real question: who gets new features first, and who gets them last.

Message MC1490899 sets two dates. In November 2026, admins can no longer add, remove or modify users in Targeted Release. A unified release preferences page arrives at the same time in the Microsoft 365 admin center.

In January 2027, Targeted Release is retired. Users who were in it fall back to the organization's general availability preference: Standard release or Deferred release. The change covers Teams, SharePoint Online, OneDrive, Outlook on the web, new Outlook for Windows, Office for the web and the admin center.

What is not affected: Microsoft 365 Apps update channels, Windows update channels and the Microsoft 365 Insider program. Your desktop apps deployment strategy stays the same.

A three-tier model that has existed since April 2026

The Frontier, Standard, Deferred model is not new. Microsoft announced it on April 16, 2026 (MC1282306), starting with Microsoft 365 Copilot. What is new in October is its extension to all Microsoft 365 services and the end of the old mechanism. Many organizations never opened these settings because they sat under Copilot. They now have to.

Frontier, Standard, Deferred: who goes where

• Frontier: access to features before general availability, AI and non-AI. For IT, champions and testers. Off by default.
• Standard release: features arrive as soon as they are generally available. This is the default, and what Microsoft recommends for most organizations.
• Deferred release: eligible major features arrive about 30 days after Standard rollout begins. For sensitive teams: customer service, finance, regulated roles.

Frontier does not replace Targeted Release

Targeted Release gave early access to features already generally available. Frontier gives access to previews. It is not the same level of risk, and not the same audience.

Targeted Release retirement: the mapping for your configuration

Microsoft's documentation offers a simple mapping.

• Targeted Release for the whole organization: move to Standard release. If you want time to prepare for major changes, choose Deferred release.
• Targeted Release for a pilot group: set the organization to Deferred release and add the pilot group to Standard release. The group keeps a one-month head start to validate.
• Standard release for everyone: nothing to do, it is already the default.

The scenario to favour

The second scenario is the most useful. It recreates what most organizations expected from Targeted Release: a group that sees changes before everyone else, with real lead time to train users and update documentation.

Pitfalls to avoid

• Doing nothing. Your pilot users lose their early access in January 2027 without anyone noticing. The help desk discovers new features at the same time as users.
• The exception limit. The admin center accepts up to 100 exceptions to the organization preference, and each member of a security group counts. For a large pilot, pick the organization preference accordingly rather than stacking exceptions.
• Turning Frontier on for everyone. Previews for hundreds of users mean help desk calls and compliance questions. Keep Frontier for a small, named group.
• Forgetting your processes. Change management procedures, user communications and help desk documentation often mention Targeted Release. They need to be updated.

Action plan before January 2027

• Inventory: in the admin center (Settings > Org settings > Organization profile > Release preferences), note who is in Targeted Release.
• Decide: Standard or Deferred for the organization, and which groups are exceptions.
• Configure: under Copilot > Settings > View all, set the general availability preferences and, if needed, Frontier.
• Communicate: notify help desk, security, compliance and pilot groups. Watch the Message center, which shows for each feature whether it falls under Frontier, Standard or Deferred.

Our recommendation

For most organizations, the best setup is Deferred release for everyone, Standard for a pilot group (IT, help desk, a few business champions) and Frontier for a handful of testers. It costs nothing and gives a month of preparation on every major change.

If your change management still relies on Targeted Release, now is the time to revisit it. io4 can run this inventory and configuration with you as part of a Modern Work engagement or your io4 360 managed service.