Microsoft is freezing Targeted Release assignments in November 2026 and retiring the option in January 2027. Organizations must move their validation strategy to Frontier, Standard Release, and Deferred Release.
What is changing
Starting in November, administrators can no longer add, remove, or modify Targeted Release users. Existing assignments remain until January 2027, after which delivery follows modern release preferences. The change covers the Microsoft 365 admin center, Teams, OneDrive, SharePoint Online, Outlook on the web, new Outlook for Windows, and Office for the web. Microsoft 365 Apps channels, Windows channels, and Insider programs are unaffected.
The new release model
- Frontier (preview): pre-GA experimentation; do not treat it as production-stable.
- Standard Release (GA): the default delivery path at general availability.
- Deferred Release (GA): delays eligible major features by approximately 30 days.
Deferred and Frontier are currently unavailable in GCC, GCC High, and DoD; those environments remain on Standard Release.
Why architects should care
Targeted Release commonly served as a pilot ring. Without explicit remapping, organizations can lose the intended order between validators and the broad population. That affects integration testing, training, support readiness, compliance reviews, and change communications.
Recommended migration plan
- Inventory every user and group currently assigned to Targeted Release.
- For a production pilot, place the broad population in Deferred and validators in Standard.
- Use Frontier only for lab users or early adopters who can tolerate preview changes.
- Update runbooks, communications, and approval criteria before January 2027.
- Use Message Center to identify changes that support deferral.
Governance perspective
Treat each audience as a deployment ring with an owner, entry and exit criteria, and validation evidence. For adjacent identity governance planning, see our Microsoft Entra PIM API migration guide.