Microsoft Copilot: October changes admins should plan for

Key insights

• Targeted Release is scheduled to retire in January 2027; users will not move automatically to Frontier.
• Microsoft recommends moving the existing Targeted Release group to Standard and other users to Deferred.
• The setting “Users can create agent blueprints” can control whether ordinary users create agent identity templates.
• Usage-based billing models in Copilot Chat, Word, Excel, and PowerPoint require UBB to be enabled and credits allocated.
• The App Builder agent and vibe.powerapps.com are scheduled to retire November 30; plan to migrate affected apps.

Microsoft Copilot’s October changes put release-ring planning, usage-based billing, and agent controls on the admin agenda. Microsoft 365 administrators and Copilot decision-makers should review who receives previews, who can create agent blueprints, and whether users should access credit-based models. Nick DeCourcy (Bright Ideas Agency) summarizes these changes and related user-facing updates in a YouTube video.

What's new

The most consequential admin change is the planned retirement of Targeted Release in January 2027. Microsoft’s release options will become Frontier, Standard, and Deferred. Frontier provides access to preview features that may not reach general availability; Standard receives features as they become generally available, while Deferred receives eligible major updates about 30 days later.

That distinction matters because Frontier is not a replacement for Targeted Release. Targeted Release has been used to give selected users early access to features expected to arrive more broadly. Frontier is a preview channel, and its features are not a reliable list of what will later reach general availability. The Microsoft 365 admin center documentation describes the transition and recommended preparation steps.

Other changes in the roundup include more Copilot features that use usage-based billing (UBB), and a planned option to buy Microsoft Copilot or Copilot Business without an underlying Microsoft 365 base license. UBB models are expected in Copilot Chat and Copilot in Word, Excel, and PowerPoint. The transcript says users need UBB enabled and credits allocated to see those models; choosing them can incur additional credit use.

There are also controls and deadlines for agent and app creation. From November 4, users are expected to be able to create agent blueprints in Microsoft Entra unless administrators restrict that capability. The App Builder agent and vibe.powerapps.com are scheduled to retire on November 30, so organizations using them should identify affected apps and plan their next step.

Who it is for and what you need

These changes are most relevant to Microsoft 365 administrators who manage release preferences, Copilot licensing, billing policies, and agent creation. They also matter to users who rely on preview features, build apps with the App Builder agent, or need access to newer models through UBB.

The material does not specify a particular Microsoft 365 license requirement for changing release preferences or managing agent blueprint creation. It says Copilot without a base license is planned from December 1, but does not explain which services or functionality that purchase would include. Copilot features continue to depend on the apps and services a user is licensed to use, so the standalone offer should not be read as including every Microsoft 365 service.

Rollout and purchase timing can vary. The transcript notes that the first UBB default changes affect new Copilot Business purchases in tenants with Microsoft 365 Business Premium, with other tenants and CSP purchases following later. It also reports that 11 markets are initially excluded. Check your tenant’s Message Center notices and spending policies before assuming that a stated date or default applies to your organization.

How it works

1. In the Microsoft 365 admin center, review your release preferences and identify users currently enrolled in Targeted Release. Enrollment changes are due to lock in November, according to the transcript.
2. Choose a future release pattern. Microsoft’s recommended approach is to move the current Targeted Release group to Standard and move other users to Deferred. This keeps a sequence in which one group receives eligible changes later, rather than using Frontier as a substitute for early access.
3. Review who should receive Frontier previews. From November, Frontier is also set to include non-Copilot preview features in Teams, new Outlook for Windows, OneDrive, and SharePoint. For desktop app previews, the transcript points to Beta Channel or Current Channel Preview as alternatives; it notes a gap for web apps.
4. For credit-based models, decide whether users should have UBB enabled and allocate credits to those who need access. Review the spending policy associated with new Copilot Business purchases, particularly if your tenant could receive UBB by default.
5. In Microsoft Entra, review the “Users can create agent blueprints” setting before the rollout begins. The transcript says administrators can turn it off in advance; confirm the current setting and its effect in your own tenant.
6. Inventory apps built with the App Builder agent or vibe.powerapps.com and plan migration before the stated November 30 retirement. The transcript does not provide a migration procedure.

The release-ring recommendation is not simply “put testers in Frontier.” If the goal is to prepare users for features that are nearing general availability, Microsoft’s stated approach is Standard for the former Targeted Release group and Deferred for the rest. Frontier has a different purpose: previewing features that may change or disappear.

Limitations and open questions

Several details remain uncertain in the material. It does not fully explain what a Copilot purchase without a base Microsoft 365 license includes, or how users without licensed mail, files, and other services will experience Copilot. Treat the license change as a purchasing option to investigate, not proof that all Copilot functions work without the underlying services.

The timing and scope of UBB defaults are not uniform across purchase routes and markets. The transcript describes changes that may trigger additional costs and identifies a default monthly credit limit for the affected scenario, but administrators should verify the current policy and Message Center notice for their tenant. The article also does not establish that every tenant or user has access to every preview or model.

Finally, Frontier features can be withdrawn rather than becoming generally available. The transcript cites Researcher’s Critique and Council previews as examples due to leave, while other scheduled features have shifted dates or been canceled. Administrators should communicate that preview access is experimental and avoid building critical processes around it.

Sources

• Microsoft Learn: Plan for the retirement of Targeted Release
• Microsoft Tech Community: Frontier expands to more Microsoft 365 public previews
• Nick DeCourcy (Bright Ideas Agency): October 2026 Copilot catch-up

Frequently asked questions

When does Targeted Release retire?

The transcript says Targeted Release is scheduled to retire in January 2027, with enrollment changes locking in November. Check Microsoft’s retirement guidance and your tenant notices for current details.

Does Frontier replace Targeted Release?

No. Frontier is for preview features that may not reach general availability. The transcript says Microsoft recommends moving the former Targeted Release group to Standard and other users to Deferred.

Can users create agent blueprints in Microsoft Entra?

The transcript says ordinary users are expected to be able to create agent blueprints from November 4. Administrators can turn off “Users can create agent blueprints”; confirm the setting in your tenant.

What do users need to access Copilot models billed by usage?

The transcript says UBB must be enabled for the user and credits allocated. The models add an option alongside included subscription functionality, but may consume additional credits.