Microsoft is modernising how it delivers updates across Microsoft 365. The long-standing Targeted Release and Standard Release options are being replaced by a three-tier model: Frontier, Standard, and Deferred. The change applies first to Microsoft 365 Copilot features, with a phased expansion to other workloads including SharePoint Online planned for later in 2026.
Read the overview on Microsoft Learn
The three release channels
| Channel | When features arrive | Use case | Supported for production? |
|---|---|---|---|
| Frontier | Before general availability | Evaluate new AI and Copilot capabilities before GA. Features may change or be withdrawn without notice. | No. Evaluation and readiness testing only. |
| Standard | At general availability | Default for most organisations. Receives fully supported GA features at release. | Yes. Recommended for most tenants. |
| Deferred | Up to 30 days after GA | Organisations with compliance requirements or complex validation and testing needs. | Yes. Supported; features arrive after a short delay. |
What is changing from the old model
The previous model had two main options: Standard Release (the default) and Targeted Release (early access for selected users or the whole tenant). The new model replaces and extends that structure:
- Targeted Release is superseded by Frontier for pre-GA AI features. Unlike old Targeted Release, Frontier is explicitly unsupported and not intended for production environments.
- Standard Release retains the same meaning: features arrive at GA. It remains the default for all tenants.
- Deferred is new: it gives admins up to 30 days of additional lead time after a feature reaches GA before it is applied to the assigned users.
- Per-user mixing is supported. Admins can assign most users to Standard and a subset of sensitive users to Deferred, or give the IT team Standard access while keeping end users on Deferred. This level of granularity was not easily achievable with the old Targeted Release model.
Rollout timeline
| Milestone | Date |
|---|---|
| MC1282306 published | 16 April 2026 |
| General Availability of modern release channels | Mid-April 2026 |
| Microsoft 365 Copilot features start using the new model | Late May 2026 |
| Expansion to other workloads (SharePoint, Exchange, Teams, etc.) | Phased; to be announced during 2026 |
How to configure the new release channels
Release preferences are managed in the Microsoft 365 admin center:
- Go to Settings > Org settings > Organization profile > Release preferences.
- Select the default release channel for your tenant: Standard or Deferred.
- To assign specific users to a different channel, select Selected users and add accounts or groups. This enables a mixed-channel configuration across your tenant.
- To evaluate Frontier features, enrol through the Frontier program entry point separately in the admin center. Frontier enrolment is distinct from the Standard/Deferred choice.
Updated Message Center post format
Alongside the new release channels, Microsoft has updated the structure of Message Center posts. Each post now follows a consistent layout:
- A brief launch-day summary with links to supporting documentation.
- Change description, rollout timeline, affected users and platforms, recommended admin actions, and compliance considerations in a consistent order.
- Clear indication of whether a feature is "deferred-capable", meaning it supports the Deferred channel delay.
The updated format makes it faster to triage Message Center posts and identify which changes require admin action before they reach users.
AI-assisted change planning tools
Microsoft has also introduced two optional MCP (Model Context Protocol) servers for organisations using AI assistants internally:
- Microsoft Release Communications MCP Server: connects AI tools to Microsoft 365 and Azure roadmap data, enabling admins to query upcoming changes through conversational prompts.
- Microsoft MCP Server for Enterprise: gives AI agents read-only access to your tenant's Message Center and Service Health Dashboard data via Microsoft Graph, with existing Entra security controls in place.
Both tools are optional. Standard change management via the admin center and weekly Message Center email digests continues to work as before.
Impact on ShareMaster
ShareMaster connects to SharePoint Online via the REST and CSOM APIs, not through the browser interface. The modernised change management model does not affect the API surface used by Recycle Master, Clone Master, Space Master, or any other ShareMaster tool.
When the Deferred channel expands to SharePoint workloads, admins will gain up to 30 days of lead time before new SharePoint features reach end users. This is useful for organisations that need to test custom solutions, update training materials, or validate permission changes introduced by new SharePoint platform updates.
Actions for SharePoint administrators
- Check your current release setting. Log in to the Microsoft 365 admin center and verify which channel your tenant is on. Most tenants default to Standard. No action is required unless you want Deferred.
- Consider Deferred for compliance-sensitive user groups. If you support users working with regulated content, assigning them to Deferred gives you a 30-day window to validate new Copilot features before they appear in those environments.
- Keep production users off Frontier. Frontier features are unsupported and subject to change. Limit Frontier enrolment to IT evaluation accounts.
- Watch Message Center for workload expansion. When Microsoft adds SharePoint Online to the modern release model, revisit your Deferred/Standard split to align with your change management schedule.