On 8 October we published here that the new Microsoft 365 release model allowed 100 exceptions, and we copied the documentation sentence in full so nobody had to take our word for it. Today that same page says 10,000. Microsoft announced it on 3 November in the Message center, which is exactly where you're supposed to be reading everything else about this. Our post has been three weeks out of date on the one number that constrained the design: here's the correction, and what that factor of a hundred changes.
We administer customer Microsoft 365 tenants and our own, and we sell nobody's licences, so we read these documentation pages when a decision is due. October's post has the structural part and we won't repeat it: Targeted release retires in January 2027, Frontier isn't its replacement because they don't play in the same place, and the new design makes you hold back the majority instead of advancing the pilot. That still stands. What's changed since are two numbers, three pages revised on 16 November, and a lock that's already down.
The lock is already down
In October, November was a future date. Not any more. "Administrators can no longer add users to, remove users from, or modify Targeted release enrollment": in commercial clouds, your tenant's Targeted release list is read-only as of today. In January 2027 it disappears and those people move to "your current modern release preference for general availability (Standard release or Deferred release)", which defaults to Standard unless you've already moved the tenant to Deferred. Microsoft, the same documentation says, "won't automatically modify your release preference settings". The FAQ adds an exception that wasn't worded this way in October: government clouds "can continue to add, remove, or modify Targeted release assignments until its retirement". The lock is for commercial clouds only.
From 100 to 10,000
This is the sentence we quoted on 8 October, exactly as we copied it then:
You can add up to 100 exceptions to Standard release or Deferred release. Each user in a security group and each user added individually count toward the 100-user limit.
And this is the same sentence today, on the same page, revised 16 November 2026:
You can add up to 10,000 exceptions to Standard release or Deferred release. Each user in a security group and each user added individually count toward the 10,000-user limit.
The change has its own notice: MC1536057, "Increasing user exception limit to 10,000 for Standard-Deferred release preferences", published on 3 November 2026, rolling out from late October and due to complete by mid-November. So it wasn't silent. It was announced in the Message center, which is the only channel that tells you whether a feature will be delayed by thirty days or not. If your ring procedure was written before that date — ours included — the number that constrained it isn't the one you think.
That number decided the design. With a cap of a hundred, the exception had to be the small group: in a three-hundred-person company you couldn't put the majority in the exception list, so the only possible configuration was the one Microsoft recommends, everyone on Deferred release and the handful of validation and support people on Standard. With ten thousand, almost any mid-sized company fits whole, and designs you couldn't build in October are back on the table: leaving the tenant default on Standard and sending entire departments to Deferred, billing or customer service, which is exactly where a surprise costs money.
The trap is where it was, it just bites further out now. Each member of a security group counts one by one against the cap, and the error fires at two moments: when you try to configure too many at once, and also "if you later add users to a security group that's already included as an exception and the exception limit then exceeds 10,000". The notice itself says as much in other words and asks you to "review group membership regularly". The consequence we'd add is one of ownership: your exception is an Entra ID group somebody else maintains, probably with a dynamic rule or an HR onboarding process, and the day that group crosses the line the error shows up in your console, not in the process that caused it.
Three pages, three ways of dating the 30 days
Deferred release delays major changes by "approximately 30 days". The operational question is thirty days counted from what, and Microsoft answers it three different ways across three pages from the same month:
The third one governs, because it's the only one that defines the anchor unambiguously, and it's also the one least like what people understand when they read the first. "Having been generally available for thirty days" sounds like thirty days at your place. The clock actually runs from global day zero. Your Standard users get the change when the wave reaches your tenant, which may be day 3, day 12 or day 25, because "Microsoft rolls out Microsoft 365 features in stages to help ensure quality". What your organisation gains is at most thirty days minus however long the wave took to reach you. At most, because delivery to the Deferred audience isn't a switch thrown on day thirty either: the documentation doesn't promise instant delivery to that audience. Microsoft guarantees the order — Standard before Deferred — but not the distance, and the distance is what you plan around when you say "we have a month to prepare the training".
What Deferred does buy you
Almost nobody uses their validation window to validate. Most pilot groups we've seen are a list of names configured years ago that nobody reviews. If that's your case, the value of Deferred isn't in the testing you won't do, and the same FAQ page explains where it is. When Microsoft finds a quality issue mid-rollout it pauses the rollout, users who haven't received it don't get it, and "if needed, Microsoft might remove the feature from users who already received it". Then it closes: "Deferred release users won't receive a feature that Microsoft rolls back before it reaches them." The thirty days — however many they end up being — mostly buy immunity to somebody else's reversals, and that works without you doing anything. If we had to defend Deferred to a finance director, we'd defend it on those grounds before a validation plan nobody will execute.
What the ring does not stop
Two reminders from the FAQ before anyone rests the weight of their change governance on this wall. First: Deferred only holds back what's tagged as both Major update and Deferred feature in the Message center, and "features not eligible for Deferred release are released to all users, including those in Deferred release, according to the Standard release schedule once they become generally available". You can't defer individual features. Second: "some features are deployed at the tenant level. Tenant-wide changes might apply to all users at once, regardless of release audience assignment." The ring splits users; it doesn't build a wall.
And a third one we've had to clarify many times in a meeting: none of this touches the desktop apps' update channels. "Microsoft 365 Apps update channels, Windows update channels, and Microsoft 365 Insider programs aren't affected." They're two separate systems and only one is changing. A change arriving earlier than you expect isn't hypothetical either: we already wrote about a Windows protection the baseline switched on 35 days before the announcement.
Two live paths in the admin center
November's third notice is MC1556082, dated the 16th: "Microsoft 365 admin center: Unified release preferences for Standard, Deferred, and Frontier". It pulls into a single panel the three preferences you used to set separately, rolling out from mid-November and due to complete by the end of the month. That's why two paths coexist right now: the documentation warns that the unified experience "is rolling out gradually in mid-November 2026, so it might not be available in your organization yet". If you already have it, the setting is under Settings > Org settings > Organization profile > Release preferences. If it hasn't reached you, what governs when Teams, SharePoint and Outlook receive changes still lives under Copilot > Settings > View all > Copilot Release Preferences: General Availability. Yes, under Copilot. If someone on your team went looking for that setting and couldn't find it, that's probably why. Changes take "up to 24 hours" to take effect.
A warning for anyone working from the Spanish documentation: the retirement page declares itself machine-translated, and it shows. In the same box, two consecutive sentences call Targeted release "versión dirigida" and "versión de destino", and in the line about Message center tags the translation turns Deferred into "Debit". If you search the console for the exact term you just read, you may not find it. For this we read the English original, and it isn't fussiness: the term is what ends up written into an internal procedure.
The twenty-minute check
- Look at who was left inside. You can't change it any more, but you can see it. That list is the people who today see changes before the rest of your company, and in plenty of tenants it turns out to be people who no longer work there.
- Redo the design with the new cap. If you ruled out a configuration in October because it didn't fit in a hundred exceptions, look at it again with ten thousand in front of you.
- Use a dedicated security group and write down who maintains it. That's where the cap sits, and the day they cross it the error lands in your console.
- Tell the people who need to know. Microsoft's recommended-actions list includes notifying change management, support, security and compliance teams, and updating internal documentation that references Targeted release. That find-and-replace across your procedures takes half an hour.
When NOT to put the whole company on Deferred
Now that ten thousand fit, the temptation is to defer everyone. Microsoft's default recommendation is still Standard for most organisations and we agree, because Deferred has a cost. The first one the documentation states plainly: "If you move users from Standard release to Deferred release, they might lose access to features that aren't available yet in Deferred release." Moving people to the slow ring can take away something they already use. The second is organisational: the thirty days are only worth it if somebody does something with them. If nobody reads the Message center, all you achieve is that your company runs a month behind the screenshots in its own manuals.
If what tempts you is the other extreme — putting your validation people into Frontier to recover the pre-general-availability access Targeted release used to give — that decision isn't the administrator's. The programme terms say those experiences "may be modified, suspended, or discontinued, may not be covered by standard support commitments or service level agreements", that HIPAA Business Associate Agreement coverage isn't included and, verbatim, that "Frontier features do not comply with ISO 27001, ISO 27002, or ISO 27018 requirements". If your company is ISO 27001 certified, that's a conversation with whoever signs the scope. We handle it inside compliance and continuity for the same reason we inventory any other supplier: what falls outside the scope turns up in the audit.
What we are not claiming
We haven't timed how long a rollout wave takes to reach a specific tenant: Microsoft doesn't publish that per organisation and we don't have the series to claim it. What we stand behind is the arithmetic of a few official sentences, not a measurement of our own. We also don't know whether your tenant already has the unified experience, because that's a gradual rollout in progress on the day we write this. And we didn't discover when the timer starts: it's in Microsoft's FAQ and others have written about it since the spring; what we add is putting it next to the other two wordings and doing the subtraction. There's no vulnerability and no urgency here: nobody should move a maintenance window over this. It's change governance, the same pattern as another notice with a November deadline we looked at a few weeks ago.
What we will stand behind isn't about Microsoft. A number on a documentation page was multiplied by a hundred, notice and all, and it still got past us — and we'd written a whole post about that page. Almost nobody re-reads the documentation they decided on: the decision is made once, written into a procedure, and sits there while the source moves underneath it. If your Microsoft 365 ring plan was written in October, today it's out of date on exactly the number that constrained it.
Sources (verified at origin on 21 November 2026): the 10,000-exception cap, the second case of the error when a security group grows, the "approximately 30 days after rollout to the Standard release audience begins" wording, both admin center paths, the 24 hours, the gradual rollout of the unified experience and the warning about losing features when moving to Deferred — Configure new Standard and Deferred release options for Microsoft 365 (revised 16/11/2026). The 100-exception quote is the one we ourselves published on 08/10/2026 in the previous post, taken that day from that same page. When the 30-day timer starts, staged rollouts, rollback behaviour, tenant-level features, the double tag, Microsoft not changing your preferences, government clouds being able to keep modifying their assignments, and Office, Windows and Insider channels being unaffected — FAQ about modern release options. November's lock, January's retirement, the "have been generally available for approximately 30 days" wording, which preference users fall back to in January, and the recommended actions — Plan for the retirement of Targeted release in Microsoft 365; the Spanish version declares itself machine-translated and is where "versión dirigida", "versión de destino" and "Debit" come from. Frontier's terms (support, service level agreements, HIPAA and ISO 27001, 27002 and 27018) — Get started with the Microsoft Frontier Program. The three Message center posts: MC1490899 (07/10/2026, Targeted release retirement), MC1536057 (03/11/2026, raising the cap to 10,000) and MC1556082 (16/11/2026, unified release preferences), consulted on a public mirror because the Message center is only reachable from the tenant itself. Translations of the English quotes are ours. Ours too: the comparison of two readings of the same page, the table of three wordings, the subtraction of thirty days minus the wave's delay, and the criterion for when not to defer. Photograph by Asa Wilson, CC BY-SA 2.0 via Wikimedia Commons.
Who decides when a Microsoft 365 change reaches your company?
Writing down which ring each group is on, who maintains that group and who reads the Message center is a morning's work, and it stops you finding out in January that the plan was written against a page that no longer says the same thing. We do it as part of compliance and continuity and the modern workplace, with the inventory in front of us and without selling anybody's licences. If you want us to look at your tenant before January, write to us.
Talk to everyWAN