Microsoft 365 Targeted Release Retirement: Move to Frontier, Standard or Deferred Before November 2026

One detail matters before anyone opens the admin center. Despite the "Office apps" framing in some coverage, this change is not about the update channels for desktop Word, Excel and Outlook. More on that below.

The timeline​

Neowin reported that starting from November 2026, Microsoft will not allow enrollment into Targeted Release, and will instead make the "unified release preferences" the only available option. Microsoft's own documentation confirms the schedule. The Microsoft Learn page on the new release options states that in November 2026, administrators can no longer add users to, remove users from, or modify Targeted release enrollment. In January 2027, Targeted release will be retired and no longer available to use.

PupuWeb's copy of the notice lists MC1490899 as published Oct 7, 2026. It carries the tags Major change, Admin impact and Retirement, with an "Act by Oct 31, 2026" date. Until the switchover, Microsoft says that if your organization has configured Targeted release in the Microsoft 365 admin center, you can continue using your existing configuration until its retired.

You have roughly three weeks before the act-by date and about a month before the enrollment freeze. Plan accordingly.

This is not your desktop Office update channel​

Neowin's headline says "Office apps," but MC1490899 covers Microsoft 365 services, not Click-to-Run desktop builds. According to the reproduction of the notice published by Modern Workspace Pro, the affected platforms are:

• the Microsoft 365 admin center
• Microsoft Teams
• new Outlook
• Outlook on the web
• Office for the web
• OneDrive
• SharePoint Online
• some components of Exchange Online

Microsoft Learn manages desktop Microsoft 365 Apps updates through a separate system: Current Channel, Monthly Enterprise Channel and Semi-Annual Enterprise Channel. They're set per device through the Office Deployment Tool, Group Policy, Configuration Manager or Intune. Microsoft's documentation notes that those update channels are device-specific and don't follow a user from machine to machine. Targeted Release and its replacements are assigned to users and groups in the tenant.

In practice:

• Moving users from Targeted Release to Deferred won't change their desktop Office build.
• Changing devices from Current Channel to Semi-Annual Enterprise Channel won't satisfy MC1490899.
• If you use preview channels such as Current Channel (Preview) as your desktop pilot, keep using them. They're a different mechanism.

The desktop channels are changing as well. Microsoft Learn says that starting in July 2026, Semi-Annual Enterprise Channel gets monthly feature and security updates. That's a separate project.

Frontier, Standard and Deferred​

The MC1490899 text defines the three options as follows:

• Frontier: Opt in to preview eligible AI and non-AI features before general availability.
• Standard release: Receive updates at general availability.
• Deferred release: Receive eligible major updates approximately 30 days after Standard release begins, allowing additional time for validation and readiness activities.

Three parts of the documentation deserve a closer read.

Frontier is not Targeted Release under a new name. Microsoft Learn describes Frontier features as preview builds that may change and aren't covered by general-availability SLAs. Users can be opted into Frontier and still be assigned to Standard or Deferred. Features outside Frontier then arrive according to that GA preference.

Deferred is not a blanket 30-day delay. It applies to eligible major updates. In Message Center, those are tagged both "Major update" and "Deferred feature." The 30 days start when the rollout to Standard begins, not when it finishes. The documentation also warns that moving users from Standard to Deferred can cause them to lose access to features that haven't reached Deferred yet.

Standard is the default. Microsoft recommends it for most organizations, and tenants are configured as Standard release unless an admin changes that.

In short, Targeted Release used to cover early access. That job now goes to Frontier, which is preview-only. Deferred adds something Targeted Release never had: a delay for major updates.

Government cloud tenants​

GCC, GCC High and DoD tenants get fewer options. Microsoft states that for customers in GCC, GCC High, and DoD environments, Standard release (general availability) remains the supported release option following the retirement of Targeted release. Currently, Deferred release and Frontier aren't available in government cloud environments.

That means government tenants lose their early-access pilot ring and get no deferral ring to replace it. For now, every user receives GA features at the same time. If your agency relied on Targeted Release users to catch problems before the rest of the workforce, you'll need another approach, such as reading Message Center and roadmap items more closely or testing in a separate tenant. Microsoft says it will update the documentation if availability changes.

How to migrate before the November freeze​

These steps follow the MC1490899 guidance and Microsoft Learn's configuration instructions. Interface labels may change when the unified experience launches in November, so check them against the notice in your own tenant.

Prerequisites: Microsoft Learn says you need the Office Apps Admin, Security Admin or AI Admin role to configure Standard and Deferred release. For group-based exceptions, create or identify a dedicated Microsoft Entra ID security group.

1. List your Targeted Release users. In the Microsoft 365 admin center, go to Settings > Org settings > Organization profile > Release preferences. Note whether the tenant uses Targeted Release for everyone or for selected users only, and record who those users are.
2. Decide what each group needs:
   • Users who test early: consider Frontier.
   • Everyone else: Standard.
   • Business-critical users who need extra time before major changes: Deferred.
3. Set the GA preference. Microsoft Learn says to expand Copilot, select Settings, and on the All Settings tab open Copilot release preferences: General Availability. Choose Standard release or Deferred release as the tenant default, then add user or group exceptions.
4. Watch the exception limit. Microsoft allows up to 100 exceptions, and every member of a security group counts toward that limit. A 400-person group won't fit, so a large Deferred group is easier to manage by making Deferred the tenant default and adding a smaller Standard group as the exception.
5. Enroll Frontier users if needed. The notice points to Copilot > Settings > View all > Copilot Frontier. Microsoft's Frontier program has its own license and eligibility requirements, so check these first.
6. Allow time for changes to apply. Microsoft says changes can take up to 24 hours.
7. Tell the affected teams. The notice recommends informing change management, the help desk, security and compliance, pilot groups and other IT stakeholders.

When the unified release preferences experience launches in November, the current Standard/Deferred settings pages will be retired as well. Microsoft says it will describe the admin-experience changes in a later Message Center post. Expect some of the menu paths above to move.

What the change means for admins​

The upside: the new model is clearer. Targeted Release combined "I want to test" and "I want to be first" into one setting. Separating preview access (Frontier) from GA timing (Standard or Deferred) is a more honest design. Deferred also gives regulated organizations a 30-day buffer on major changes, which is the kind of protection they have long asked for.

The downside: Targeted Release users received features that were close to GA, ahead of everyone else. Frontier users receive preview features that aren't covered by GA SLAs, and much of Frontier is centered on AI. Some IT teams just want to see next month's SharePoint change a couple of weeks early. They may find Frontier more experimental, or more Copilot-focused, than they need.

The menus also show where Microsoft is heading. GA release preferences for Teams, SharePoint and Outlook on the web now sit under a Copilot node in the admin center. Microsoft increasingly treats Copilot as the place where change management lives.

The government-cloud gap is the biggest concern. Organizations with the strictest change-control requirements will be left with a single GA ring and no official early-access or deferral option, at least for now.

Summary​

• What's retiring: Microsoft 365 Targeted Release for services such as Teams, SharePoint, OneDrive, new Outlook and Office for the web. It is not a desktop Office update channel.
• When: enrollments freeze in November 2026, the program retires in January 2027, and Message Center lists an act-by date of October 31, 2026.
• Replacements: Frontier (preview opt-in), Standard (GA, the default) and Deferred (about 30 days later for eligible major updates).
• Government clouds: only Standard is available for now.
• Action: inventory your Targeted Release users, assign each group a preference, note the 100-exception limit, and check MC1490899 in your tenant's Message Center for the compliance considerations.

Admins who leave this until January will probably find that their pilot group has quietly become Standard users. Better to make the change deliberately before the freeze.