Last updated: 23 June 2026
Quick answer: Microsoft 365 now has three release tracks: Frontier (early access, pre-GA), Standard (general availability, default), and Deferred (30-day buffer after Standard GA). Deferred is brand new. Frontier replaces what was previously called Targeted Release. The new model currently applies to Microsoft 365 Copilot features, with broader rollout to follow.
| Old Model | New Model |
| Preview / Targeted Release | Frontier |
| General Availability | Standard |
| (no equivalent) | Deferred |
| Tenant type | Frontier | Standard | Deferred |
| Commercial (Worldwide) | Available | Available | Available |
| GCC | Limited / delayed | Available (delayed) | Available (delayed) |
| DoD | Not available | Available (further delayed) | Available (further delayed) |
| Education (EDU) | Varies by feature | Available | Available |
Note: Exact eligibility and timing varies by feature and is confirmed in individual Message Center items. This table reflects the general pattern; always check the MC item rollout schedule for your specific tenant.
A real-world example of how this plays out: some organisations run both a commercial tenant and a GCC High tenant. Because GCC High receives features later, their internal policy is to manage everything based on the GCC High release date — if a feature hasn't landed in GCC High yet, they disable or defer it on the commercial side too. That's a deliberate process decision, not a default. It's the kind of governance call that only works if you're actively tracking dates across both environments.
A few practical constraints worth knowing:
A release model only helps you if you're actively deciding who goes where. If you don't map your audiences, review incoming Copilot changes, and make deliberate rollout decisions, the differing audience-based tracks become labels that mean little in practice.
Microsoft is rebuilding the Message Center experience to be more structured, more actionable, and designed to help admins quickly extract the compliance and operational details that matter.
The intent is to make it easier to understand:
This is a welcome improvement, although it doesn't solve the volume issue.
Better-formatted posts help significantly with understanding the impact of changes, but it doesn't change anything if they sit unread alongside hundreds of others. Whether the quality of information has improved or not, IT teams will still struggle if they don't have a system for catching, triaging, and acting on what matters before the deadline passes.
Map which teams in your organisation fall into Frontier, Standard, and Deferred categories.
Microsoft ships many Copilot features on by default e.g. Flex Routing, Anthropic models, Copilot agent capabilities.
If your team doesn't actively review them, those defaults become your organisation's policy without anyone making a deliberate decision.
Microsoft's modernisation initiative improves the upstream model through clearer comms, release control and AI-assisted retrieval.
The downstream risk still sits with IT teams:
ChangePilot is built for that operational layer. It monitors the changes landing in your M365 environment, filters for impact and urgency, and makes it visible so your team can act before the incident, not after the ticket.
Microsoft's modernising change management initiative introduces three core changes to how Microsoft 365 updates are released and communicated: an audience-based release model (Frontier, Standard, and Deferred), a restructured compliance-first Message Center experience, and AI-powered tooling via MCP servers. The initial scope is focused on Microsoft 365 Copilot features, with broader rollout expected to follow. You can view the associated Message Center item at MC1282306.
Frontier replaces what was previously called Preview or Targeted Release. It is an opt-in track for early adopters who want pre-GA access to evaluate Copilot features before they reach general availability.
Standard replaces the previous GA track and is the default for organisations that want access to new features as soon as they are generally available.
Deferred is a net-new addition - a 30-day buffer after Standard GA for regulated or complex environments that need more time before deployment. It is GA quality and fully supported, but does not offer indefinite deferral or feature-by-feature control.
Note that during the transition period, you may still see the old terminology (Targeted, GA) in some Message Center items as Microsoft migrates features to the new model.
Microsoft is restructuring the Message Center to use a more compliance-first, actionable format designed to help admins quickly identify what's changing, who it affects, and what action is required. The goal is to make it easier to extract security, legal, and helpdesk-relevant information without having to read through every post in full.
Copilot-related changes often land as default-on settings with compliance, data residency, or governance implications. If your team doesn't have a consistent process for reviewing Message Center items before their deadlines, those defaults become your de facto policy without any active decision being made.
Recent examples include Flex Routing (MC1269223), where EU tenants had until 17 April 2026 to opt out before data processing moved outside the EU Data Boundary.
What is the difference between Targeted Release and Frontier in Microsoft 365?
Frontier is the direct replacement for Targeted Release. Both give early access to features before general availability, but Frontier is specifically focused on Microsoft 365 Copilot and AI features. Targeted Release was a broader early-access programme; Frontier is more structured, opt-in at the tenant level, and designed around a feedback loop with Microsoft before features reach GA. During the transition period you may still see "Targeted Release" language in some Message Center items and admin centre settings as Microsoft migrates everything to the new model.
Does Deferred release remove admin controls or security policies in Microsoft 365?
No. Deferred release does not remove existing admin controls, policies, or security baselines. It provides a 30-day buffer after Standard GA for major feature releases; it is not a way to block specific features indefinitely, and it does not reduce your governance surface. Your existing controls remain in place regardless of which release tier your organisation uses.
How many users can be on Deferred release in Microsoft 365?
Currently, when your organisation is on Standard release, you can place a maximum of 100 users on Deferred release. Group-level support is on the roadmap but not yet available. Microsoft recommends keeping IT professionals and champions on Standard release even if the wider organisation is on Deferred, so your team sees changes before end users do.
Yes — the tenant types are a fixed, definitive set: Commercial (Worldwide), GCC, GCC High, DoD, and Education. There is no additional category beyond these. Some large organisations operate across more than one type simultaneously — for example, running both a commercial tenant and a GCC High tenant — but the taxonomy itself is closed. Each tenant type receives releases on its own schedule, and the availability of Frontier, Standard, and Deferred varies across them as shown in the table above.
Organisations that operate more than one tenant type, for example, a commercial tenant alongside a GCC High tenant, need to manage release dates across both environments independently. Because GCC High receives features later than commercial, a common approach is to base internal rollout decisions on the GCC High release date: if a feature hasn't landed in GCC High yet, it gets disabled or deferred on the commercial side too, regardless of which release tier that tenant is on. This is a deliberate governance decision, not a default behaviour. It requires active tracking of release dates across both tenants and a clear internal process for when and how to enable features consistently.
ChangePilot can help surface the relevant dates across both environments so your team isn't manually cross-referencing two Message Center instances.
The new release model is rolling out to worldwide commercial tenants first. Government cloud tenants (GCC, GCC High, DoD) operate on separate timelines and Frontier is generally not available in those environments. Standard and Deferred release are available in government clouds but features arrive later than in commercial tenants. Some organisations manage both a commercial and a GCC High tenant and base their internal rollout decisions on GCC High release dates — disabling features in their commercial environment until they are confirmed available in GCC High. Always check the rollout schedule section of individual Message Center items for your specific tenant type.