The Microsoft 365 Targeted Release channel for Office apps is being retired, and administrators have only months to adjust how their organizations receive new features. If your company currently uses Targeted Release to roll out Office updates to a select group of users ahead of everyone else, it’s time to plan a migration.
Microsoft confirmed the change, noting that the Targeted Release option for Office apps will no longer be available, forcing admins to move their settings to one of the remaining update channels. The window to do so is short, so organizations haven’t got much time to get it right.
What the Microsoft 365 Targeted Release channel did
Targeted Release (also referred to in the admin center as “First Release for Targeted Groups”) let organizations give a chosen subset of users access to new Office app features before they reached the wider population. Instead of waiting for an update to hit everyone at once, admins could point it at specific people or groups and watch how the new build behaved in a controlled environment.
That made it a testing ground of sorts. IT teams could validate compatibility with internal tools, third-party add-ins, and custom configurations before committing to an org-wide rollout. For many admins, it was the safest way to try new features without risking a broken experience across the entire company.
What’s changing
With the channel being retired, that targeted early-access option will disappear. Organizations currently on Targeted Release will need to pick a different update channel for their Office apps and re-point their update settings accordingly. In practice, that means the controlled, group-by-group rollout you relied on will no longer be available through that feature.
Microsoft is asking admins to act within the remaining months rather than waiting until the switch flips. The earlier you migrate, the more time you have to validate new features under whatever channel you move to.
What this means for you
If your organization isn’t using Targeted Release, this change won’t touch your day-to-day. You’ll keep receiving Office updates through your current channel as normal. The impact falls squarely on the admins who configured the targeted early-access group.
For those admins, the immediate task is straightforward but time-sensitive: identify your current Targeted Release configuration, decide which remaining update channel fits your rollout strategy, and move the settings over. Because the deadline is close, it’s worth treating this as a near-term to-do rather than something to defer.
How to prepare
Start by reviewing your existing Targeted Release setup in the Microsoft 365 admin center so you know exactly which users and groups are enrolled. Then evaluate your remaining update-channel options and pick the one that best matches how quickly you want features to arrive. Once you’ve chosen, re-point your Office app update settings to that channel and confirm the targeted groups are receiving updates as expected.
Give yourself enough lead time to test new features on the new channel before relying on them, since you’ll lose the gradual, controlled rollout that Targeted Release provided. Building that buffer into your timeline is the practical way to avoid a rushed migration.
The broader update-channel picture
Office apps for enterprise have long shipped through a set of update channels that control how often and how broadly new features are delivered. These channels let organizations balance freshness against stability — some teams want the latest features fast, others prefer a slower, more predictable cadence.
Consolidating or retiring certain options is part of Microsoft’s ongoing effort to simplify its update-management model. The practical upshot is that admins should keep an eye on their channel settings and confirm their rollout strategy still fits their needs as Microsoft reshapes what’s available.
Bottom line: the Microsoft 365 Targeted Release channel for Office apps is going away, and the clock is ticking. If your org relies on it, treat the migration as a priority this quarter and give yourself room to test before you commit.
Source: Neowin
Over to you: Is your organization currently using Targeted Release for Office apps, or have you already migrated to another update channel?
