The announcement itself is short. The timing makes it matter more than it looks. It lands in the same month that Microsoft freezes Targeted release enrollment, ahead of that option's retirement in January 2027. Admins now have two related changes to handle together.
What's actually changing
This is not a new program. Microsoft describes it as the same Frontier, now covering more of Microsoft 365. Its pitch is that previews for different products used to live in different places, and Frontier replaces that with one program, one admin setting and one place to test features and send feedback before general availability (GA).
The practical points:
- Products in scope from November: enrolled users get eligible preview features across Copilot, new Outlook for Windows, OneDrive, SharePoint, and Microsoft Teams.
- Users who aren't enrolled: nothing changes. They keep getting features based on their Standard release or Deferred release setting.
- Current Frontier users: If you're already enrolled in Frontier for Copilot features, you don't need to re-enroll. Starting in November, those users will also get eligible preview features across all of the products listed above.
- Still optional: enrollment remains an admin-controlled opt-in.
Watch the word "eligible." Microsoft gives no exact November start date, names no specific features and doesn't promise that every preview for these products will go through Frontier. It tells admins to watch Message center for future additions. It also says Frontier features ship before GA and may never reach Standard or Deferred release at all.
Microsoft Learn's release-options documentation reflects the wider scope. It says Frontier provides preview access to innovative and emerging AI and now non-AI capabilities in Microsoft 365 before those features reach general availability. The words "non-AI" are the real news. Frontier is no longer just Copilot's test area.
Section summary: From November, a single Frontier enrollment covers eligible previews in Copilot, new Outlook for Windows, OneDrive, SharePoint and Teams. Existing members join the expanded scope automatically. Everyone else keeps their current release setting.
How Frontier fits with Standard and Deferred release
Microsoft now uses what it calls a new three-tier, audience-based release model—Frontier, Standard release, and Deferred release—so organizations can balance early access with readiness and control. It's easy to read that as a pipeline where users move from Frontier to Standard to Deferred. Microsoft says that reading is wrong.
| Option | What it governs | Timing |
|---|---|---|
| Frontier (opt-in) | Eligible preview features | Before GA |
| Standard release (default) | GA features | When features become generally available |
| Deferred release | Eligible major changes at GA | About 30 days after the Standard rollout begins, according to Microsoft Learn |
According to Microsoft Learn's Frontier setup guide, a user can be enrolled in Frontier and also assigned to Standard or Deferred release. Frontier delivers eligible features before GA. For anything outside Frontier, the user's Standard or Deferred setting still decides when GA features arrive. Microsoft describes Standard and Deferred as preferences for GA features, not stages a user passes through after Frontier.
Don't confuse Frontier with the Microsoft 365 Insider program either. Microsoft says organizations using Microsoft 365 Insiders (for business) to validate production builds should keep doing that. Frontier is cloud-delivered preview access controlled by a tenant setting, while Insider covers client builds. Microsoft Learn adds that some Microsoft 365 AI features on Windows, Mac, iOS and Android are still released through the Insider program.
Section summary: Frontier is pre-GA access. Standard and Deferred control when GA features arrive. Insider builds remain a separate program.
Licensing: enrollment doesn't grant product access
Enrollment and product entitlement are separate. Per Microsoft, a Microsoft Copilot license is not required to enroll in Frontier. Admins must assign users licenses that provide access to the products they want to preview. In practice, to use Copilot-related Frontier features, users need a Microsoft Copilot license or a license that includes access to Copilot. To use Frontier features for Teams, users need a license that includes access to Microsoft Teams.
This is a change from Frontier's earlier days. When Microsoft opened the program to consumers in 2025, it described Frontier as the program that gives commercial Microsoft 365 Copilot customers early access to exciting, cutting-edge capabilities. Organizations without Copilot can now use Frontier to pilot Outlook, OneDrive, SharePoint and Teams previews.
Microsoft Learn also says that users enrolled without a qualifying license simply don't see the related Frontier features. If a pilot user says "I don't see anything," check their license first. The guide further warns that an admin's own account may need matching product licenses, or some Frontier settings and agents might not appear in the admin center.
How to enroll a pilot group
Microsoft encourages a staged rollout. Frontier enrollment is controlled by your admin, and you don't need to enroll your whole tenant. You can start with a pilot group, such as IT staff, an innovation team, or employees who want to test the latest features, and expand over time.
Microsoft Learn's current Frontier setup guide gives this procedure:
- Sign in with an account that has the AI Administrator, Security Administrator or Office Apps Administrator role.
- Open the Microsoft 365 admin center and go to Copilot > Settings.
- Select the View all tab.
- Type "Frontier" in the Search all Copilot settings bar.
- Select Copilot Frontier.
- Choose No access (the default), All users, or Specific users and groups.
What success looks like: Microsoft says eligible users get supported preview features as they're released, and features may take up to three hours to show up. Don't start troubleshooting after five minutes.
Common failure points:
- Feature missing for a user: check that the user has a license for the product being previewed.
- Setting missing for the admin: check the admin's role and the admin's own product licenses.
- Frontier agents missing: Microsoft Learn says the Frontier switch doesn't override agent settings. Allow agents and plugins built by Microsoft must be on under Agent > Settings > Agent and plugin access, and an agent an admin has turned off stays unavailable whether or not the user is enrolled. These agent controls apply to Frontier agents. Microsoft doesn't say they're required for Outlook, OneDrive, SharePoint or Teams previews.
- Feature depends on a third-party model: Microsoft says Frontier will never turn on AI providers such as Anthropic for you. If a feature needs one, an admin has to approve that model explicitly.
One more thing to plan for: Microsoft Learn says a new unified Release Preferences page, which brings Frontier, Standard and Deferred settings together, is expected in the admin center in November 2026. Once it arrives, the menu paths above may change. Watch Message center.
The Targeted release retirement
Many organizations have relied on Targeted release for early validation, and it is going away. According to Microsoft Learn's retirement guide:
- November 2026: admins can no longer add users to Targeted release, remove them or change enrollment.
- January 2027: Targeted release is retired. Users assigned to it then get features according to their modern release preferences.
Microsoft is explicit that Targeted release users are not moved into Frontier automatically. The two options also do different jobs. Microsoft Learn says Frontier is for pre-GA features and Targeted release gave early access within GA. Moving everyone from Targeted release into Frontier would put them on preview software, not early GA builds, which is a bigger change in risk.
For organizations that used Targeted release for selected users, Microsoft suggests choosing Deferred release for the tenant and adding validation, support or pilot users to Standard release. That keeps an early GA test group while giving everyone else more time. Frontier then becomes a separate, deliberate choice for the few people who should see preview features.
The retirement doesn't touch everything. Microsoft Learn says Microsoft 365 Apps update channels, Windows update channels and Microsoft 365 Insider programs aren't affected. Windows servicing and Office desktop update channels stay as they are.
Caveats before enrolling production users
Microsoft Learn says production tenants can safely enroll users in Frontier. The fine print still deserves a careful read, particularly in regulated industries:
- Government clouds: Frontier and Deferred release aren't currently available in GCC, GCC High or DoD. For those customers, Standard release is the supported option after Targeted release retires.
- Support: preview features may be changed, suspended or discontinued, and may not be covered by standard support commitments or service level agreements.
- Compliance: Microsoft says HIPAA Business Associate Agreement coverage doesn't extend to Frontier experiences, and that Frontier features don't comply with ISO 27001, ISO 27002 or ISO 27018 requirements.
- Cost: Microsoft notes some Frontier experiences may only be available on a paid basis.
Hospitals and other HIPAA-covered organizations should check their data handling before enrolling, not after.
Analysis: tidier, with real tradeoffs
Bringing previews under one setting is a reasonable fix. Admins have long had to track separate preview mechanisms across Microsoft 365 workloads, and one opt-in with user and group targeting is simpler to govern. Help desks can also prepare for features before they reach everyone.
There are tradeoffs. Frontier carries the Copilot brand, and it is managed from the Copilot section of the admin center even for previews with no AI in them. That may confuse people for a while. The Copilot license requirement for enrollment is gone, but the menus still say Copilot. The single switch also means less granular control: Microsoft describes enrollment as covering all eligible previews in the listed products, so admins who want only Teams previews have no per-product toggle documented. Finally, the compliance caveats are the main reason to keep Frontier groups small and deliberate.
What admins should do this week
- Find your current Targeted release users under Settings > Org settings > Organization profile > Release preferences.
- Choose Standard or Deferred release for GA features, using Microsoft's mapping guidance.
- Pick a small Frontier pilot group, ideally IT staff and willing power users, and check their product licenses.
- Check whether your compliance obligations allow Frontier at all, especially HIPAA and ISO requirements.
- Update internal documentation that mentions Targeted release, and brief support, security and change-management teams.
- Watch Message center for the November rollout and the unified Release Preferences page.
Will one preview program make Microsoft 365's steady stream of changes easier to manage? It should, as long as admins treat Frontier as preview access and not as a replacement for Targeted release.