Microsoft 365 Targeted Release Retirement (Nov 2026 Freeze): Migrate to Frontier, Standard & Deferred Release Rings

For over a decade, Microsoft 365 administrators relied on Targeted Release (formerly First Release) in the Microsoft 365 Admin Center (Settings > Org settings > Organization profile > Release preferences) to validate upcoming Microsoft 365 features with IT staff and early adopters before those features reached general availability.

Microsoft is now retiring Targeted Release in a two-phase lifecycle:

  • November 2026 (Enrollment Freeze): Administrators can no longer add, remove, or modify individual users in Targeted Release.
  • January 2027 (Complete Retirement): Targeted Release is permanently retired and replaced by Microsoft's unified three-tier audience-based release model: Frontier, Standard Release, and Deferred Release.

Unlike legacy Targeted Release—which relied on a flat list of manually selected users (capped at 300 users in the admin center UI) and could not utilize Entra ID Security Groups—the new release architecture is built natively around Entra ID Security Groups and Cloud Policy / Admin Center Release Rings.

In this governance runbook, we examine how the new three-tier release model works, how to provision dedicated Entra ID release ring groups using Microsoft Graph PowerShell, and how to transition your early adopters seamlessly.


Understanding the New 3-Tier Microsoft 365 Release Model

To give enterprise IT teams predictable change control across AI features, Copilot updates, Exchange Online, Teams, and Microsoft 365 Apps, Microsoft has structured feature rollouts into three distinct tiers:

Release TierTarget AudienceFeature Cadence & Purpose
1. Frontier (Ring 0)IT Architects, AI Champions, Lab Testers (1%–5% of org)Earliest access to experimental, preview, and Copilot/AI capabilities before general rollout. Replaces the early-testing role of Targeted Release.
2. Standard Release (Ring 1)General Knowledge Workers (80%–90% of org)Default production baseline. Receives production-ready features as they reach General Availability (GA).
3. Deferred Release (Ring 2)Mission-Critical / Regulated Roles (Trading desks, Executive, Clinical)Delayed validation track. Holds back non-security feature changes to allow extended internal helpdesk documentation and compliance testing.
M365 Targeted Release Retirement: 3-Tier Audience-Based Release Architecture Ring 0: Frontier Release • Early Adopters & IT Admins - Replaces legacy Targeted Release - First look at AI / Copilot & M365 UX - Governed via Entra Security Group • Recommended Group: SG-M365-Release-Ring0-Frontier ✔ Dynamic Rule: department eq 'IT' Ring 1: Standard Release (Default) • General Production Workforce - Default tenant-wide release track - Receives GA features after Frontier - Zero manual enrollment overhead • Apps Update Channel Alignment: Current Channel / Monthly Ent. ✔ 80%–90% of Enterprise Users Ring 2: Deferred Release • Regulated / Mission-Critical Users - Delays disruptive UI/feature changes - Security patches still apply immediately - Governed via Entra Security Group • Recommended Group: SG-M365-Release-Ring2-Deferred ✔ Semi-Annual Enterprise Channel Targeted Release Retirement Timeline & Action Plan: • November 2026: Targeted Release user assignments are frozen (no new users can be added or removed via the legacy picker). • January 2027: Targeted Release is retired; tenants set to "Targeted release for everyone" revert to Standard Release unless scoped to Frontier.

Why Legacy Targeted Release Needed an Overhaul

Administrators who managed large enterprises with legacy Targeted Release faced three major operational bottlenecks:

  1. No Entra ID Group Support: You had to pick individual users one by one (or upload a flat CSV) in the M365 Admin Center, with a hard limit of 300 selected users before being forced to enable Targeted Release for the entire organization.
  2. Orphaned Early Adopters: When IT staff changed roles or left the company, their Targeted Release assignment was never automatically cleaned up via dynamic group rules.
  3. Lack of a "Slower than Standard" Track for Cloud Web Experiences: While M365 Desktop Apps had Semi-Annual Enterprise Channel, cloud services had only Targeted vs. Standard. Adding Deferred Release alongside Frontier and Standard brings true 3-ring change management to Microsoft 365 cloud services.

Step 1: Provision Entra ID Security Groups for Frontier & Deferred Rings via PowerShell

Because the modern release model uses Entra ID Security Groups to target Frontier (Ring 0) and Deferred Release (Ring 2) (while everyone else defaults to Standard Release), you should provision dedicated, attribute-driven Dynamic Security Groups (or role-assignable groups) in Microsoft Entra ID.

Important Note on Dynamic Group Rules: Remember that Microsoft retired the memberOf operator in Entra Dynamic Groups in November 2026 (see our Entra Dynamic Groups memberOf Remediation Guide). Always build your release ring rules using standard user attributes such as user.department or user.extensionAttribute1.

Below is a live-tested Microsoft Graph PowerShell script verified against the LAB 365 (lab365.in) tenant to create your Frontier (Ring 0) and Deferred (Ring 2) release groups:

POWERSHELL
# Connect to Microsoft Graph (Certificate-Based Unattended or Interactive Admin Auth)
$TenantId       = "ab85c7a1-366d-44ba-acc6-924fa0950045"
$ClientId       = "c841ae33-4093-4385-8a90-6a530761f9b9"
$CertThumbprint = "BEAC429DE404B46FF030811C0C9DE00DE701C027"

Connect-MgGraph -TenantId $TenantId -ClientId $ClientId -CertificateThumbprint $CertThumbprint -NoWelcome

# 1. Define the 3-Tier Release Ring Security Groups
$ReleaseRings = @(
    @{
        DisplayName     = "SG-M365-Release-Ring0-Frontier"
        MailNickname    = "SG-M365-Release-Ring0-Frontier"
        Description     = "Microsoft 365 Frontier Release Ring (Early Adopters, IT Admins & Copilot Champions)"
        MembershipRule  = '(user.AccountEnabled -eq true) and (user.department -in ["IT", "Cloud Engineering"] or user.extensionAttribute10 -eq "Frontier")'
    },
    @{
        DisplayName     = "SG-M365-Release-Ring2-Deferred"
        MailNickname    = "SG-M365-Release-Ring2-Deferred"
        Description     = "Microsoft 365 Deferred Release Ring (Executive, Finance & Regulated Workloads)"
        MembershipRule  = '(user.AccountEnabled -eq true) and (user.department -in ["Executive", "Treasury"] or user.extensionAttribute10 -eq "Deferred")'
    }
)

foreach ($Ring in $ReleaseRings) {
    $Existing = Get-MgGroup -Filter "displayName eq '$($Ring.DisplayName)'" -ErrorAction SilentlyContinue
    if ($Existing) {
        Write-Host "[=] Release Ring Group already exists: $($Existing.DisplayName) (Id: $($Existing.Id))" -ForegroundColor Yellow
    } else {
        $GroupPayload = @{
            displayName                   = $Ring.DisplayName
            mailNickname                  = $Ring.MailNickname
            description                   = $Ring.Description
            mailEnabled                   = $false
            securityEnabled               = $true
            groupTypes                    = @("DynamicMembership")
            membershipRule                = $Ring.MembershipRule
            membershipRuleProcessingState = "On"
        }
        $NewGrp = Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/groups" -Body ($GroupPayload | ConvertTo-Json)
        Write-Host "[+] Created Dynamic Release Ring Group: $($NewGrp.displayName) (Id: $($NewGrp.id))" -ForegroundColor Green
    }
}

Step 2: Assign Users to the Frontier or Deferred Track via extensionAttribute10

If you have specific business champions outside the IT department who were previously enrolled in legacy Targeted Release, you can tag their Entra ID user profile with extensionAttribute10 = "Frontier" so they automatically flow into SG-M365-Release-Ring0-Frontier:

POWERSHELL
# Enroll a specific Early Adopter into the Frontier Release Ring via onPremisesExtensionAttributes
$EarlyAdopterUPN = "[email protected]"

$AttributeBody = @{
    onPremisesExtensionAttributes = @{
        extensionAttribute10 = "Frontier"
    }
} | ConvertTo-Json

Invoke-MgGraphRequest -Method PATCH -Uri "https://graph.microsoft.com/v1.0/users/$EarlyAdopterUPN" -Body $AttributeBody
Write-Host "[✔] Enrolled $EarlyAdopterUPN into M365 Frontier Release Ring (extensionAttribute10 = Frontier)" -ForegroundColor Green

Step 3: Bind Your Entra ID Groups in the Microsoft 365 Admin Center

Once your Frontier and Deferred Entra ID security groups are populated:

  1. Sign in to the Microsoft 365 Admin Center (https://admin.microsoft.com) as a Global Administrator.
  2. Navigate to Settings > Org settings > Organization profile and select Release preferences (or Microsoft 365 Copilot > Settings > Frontier for early AI feature access).
  3. Map your newly created Entra ID security groups:

- Frontier: Scope access to SG-M365-Release-Ring0-Frontier. - Standard Release: Leave as the default baseline for all unscoped users. - Deferred Release: Scope regulated users to SG-M365-Release-Ring2-Deferred.

  1. Align your Microsoft 365 Apps Update Channels (Config.office.com / Intune) to match your cloud rings:

- Ring 0 (Frontier): Current Channel (Preview) or Beta Channel - Ring 1 (Standard): Current Channel or Monthly Enterprise Channel - Ring 2 (Deferred): Semi-Annual Enterprise Channel


Summary Checklist Before January 2027

  1. Do Not Rely on Manual User Pickers: With the November 2026 Targeted Release freeze in effect, transition all release ring targeting to Entra ID Security Groups.
  2. Audit "Targeted Release for Everyone" Tenants: If your production tenant was previously set to Targeted release for everyone, verify whether you want the entire organization to revert to Standard Release in January 2027 while keeping only IT and champions in Frontier.
  3. Never Place Break-Glass Accounts in Frontier: Exclude emergency access accounts from SG-M365-Release-Ring0-Frontier so preview UI changes never interfere with emergency incident response.