Microsoft Is Ending the Setting That Gave Some Staff New Features Early. Did Anyone Use It?

"Targeted release" sounds like the careful option, as if Microsoft were aiming new features at the right people. It is the opposite. It meant early access: the people you enrolled saw changes to Teams, SharePoint, Outlook on the web and the admin center ahead of everyone else. Microsoft is now ending that setting and replacing it with three simpler choices.

Most small companies never touched it, and for them this is a non-event. The ones that did are the ones where an IT person or an outside provider set up a test group years ago and nobody wrote it down. Our Microsoft 365 managed services include a check of exactly this kind of forgotten setting.

Quick answers

What is being retired, and when? Targeted release for Microsoft 365 services. Microsoft's own planning page says administrators can no longer add or remove users, or change enrollment, in November 2026. The retirement itself follows in January 2027, with no exact day published.

Do we have to do anything? Only if Targeted release was ever switched on. Microsoft states that organizations that do not use it need no immediate action. Check under Settings, Org settings, Organization profile, Release preferences.

What happens if we do nothing? Users who were on Targeted release move to your current general-availability preference. Unless someone changed it, that is Standard release, meaning new features arrive the day they become generally available.

Is there a deadline? Microsoft's Message Center notice carries an act-by date of October 31, 2026. After that the enrollment screen is locked, so decisions made in November have to be made in the new settings page.

What did Targeted release do, and what takes its place?

Microsoft rolls out new features to its own staff first, then to customers in waves. Targeted release let a company put a few people, or everyone, near the front of the customer queue. The early features were still finished and supported, just a little ahead of the general rollout.

Microsoft's retirement guidance replaces it with three options. They answer different questions than the old setting did, so they are not a one-to-one swap.

The key point is the first row. Microsoft says Frontier is not a renamed Targeted release. Frontier gives you features that are still in preview. Targeted release gave you finished features a bit sooner. Switching a Targeted group to Frontier would hand your testers unfinished software.

Which setting should a 20-person company pick?

Microsoft's table of recommendations is short. If Targeted release was on for everyone, choose Standard, or Deferred if you want extra preparation time. If it was on for a few selected people, choose Deferred for the company and add those people to the Standard group, so they keep seeing changes first. If you used Standard for everyone, there is nothing to update.

That second case is the one worth understanding, because it is also what we would suggest for most offices that care about stability. The logic is simple: your two or three most tech-comfortable people see changes on day one, tell you what looks different, and everyone else gets the same change a month later with a warning in hand.

Two limits apply. Deferred only delays features that Microsoft tags as both a "Major update" and a "Deferred feature". Smaller changes arrive on the normal schedule, at the same time as Standard. And the exception list, whether single users or members of a security group, is capped at 100 people in total, which is not a limit a small company will meet.

What does a major update look like in practice?

Microsoft defines major updates in its release options documentation. The list reads like the things that make your phone ring: changes to a user's inbox, meetings, delegations, sharing and access; a new application switched on with default settings; changes to where data is stored; rebranding that confuses staff; changes to visible capacity such as storage.

We have covered several of these in recent weeks. A Copilot trial turned on by default and a Teams agent that can reset passwords are exactly the kind of change where a 30-day head start decides whether you announce it or your staff discover it.

Be realistic about the limits, though. Deferred is not an approval queue where you vet each feature. The 30-day clock starts when Microsoft begins the Standard rollout, so it buys you notice, not control. Switches inside individual features, like the ones described in our article on Baseline Security Mode, still have to be managed on their own.

Should anyone in your company join Frontier?

Probably not everyone, and for many small firms nobody. Frontier is Microsoft's program for previews of new features, mostly AI ones, before general availability. Microsoft's comparison table is plain about it: Frontier features are preview, subject to change, and not governed by the general-availability service levels.

That matters most if the person trying a preview feature handles client files, payroll or contracts. A preview AI feature that reads documents is a data-handling question before it is a productivity question. Our piece on the Microsoft 365 E7 Frontier suite shows how Microsoft is positioning this at the high end.

If you want to try it, keep it to a named person who is not touching sensitive data, write down the date you enrolled them, and agree who switches it off. Microsoft's Frontier setup page describes the opt-in.

How do you check and change it in ten minutes?

You need an administrator who holds the Office Apps Admin, Security Admin or AI Admin role. Work through the steps in this order.

Step 1: find out if you are affected. In the Microsoft 365 admin center, open Settings, Org settings, Organization profile, Release preferences. If it says Standard for everyone, you are finished.

Step 2: write down who is on Targeted release. Take a screenshot of the list before you change anything. You will want it if someone asks in March why a feature appeared early.

Step 3: set the general-availability preference. Open Copilot, Settings, View all, then "Copilot Release Preferences: General Availability". Choose Standard or Deferred and add your exception users or group, then save. Microsoft notes that changes can take up to 24 hours.

Step 4: decide on Frontier. The matching Frontier setting sits in the same Copilot settings area.

Step 5: tell people. Whoever answers staff questions should know which group is on which setting.

One caveat from Microsoft: if you move someone from Standard to Deferred, they might lose features they already have that have not yet reached Deferred. Do it for the right people, not as an experiment. And in November, Microsoft replaces the current screens with a single Release Preferences page, so the menu names above may change within weeks.

Is another admin tool leaving this month?

Yes, a smaller one. Microsoft's Message Center notice MC1462922 says the Admin app, built for very small businesses inside Teams, Outlook and Microsoft365.com, stops being supported or available from October 2026. Microsoft names the Microsoft Admin Center, the Teams Admin Center and the Microsoft 365 Admin Agent as the places to go instead.

If your owner or office manager has been using the Admin app for simple tasks, show them the admin center version this week, while the old one still opens. The notice makes no action mandatory, but a tool people used yesterday that quietly disappears is how a "simple" task turns into a call to the provider.

What is the real cost of ignoring it?

For most companies, nothing visible. Microsoft's guidance says users left on Targeted release will follow your existing general-availability preference when the retirement arrives. The cost is a loss of intent. A group you built on purpose to get early warning silently turns into an ordinary Standard group, and the early warning is gone with it.

The bigger risk is the opposite case: a company that never configured anything, and assumes "Microsoft handles updates". Microsoft does handle them. What it does not do is decide which of your staff should hear about a change first, or what your help desk should say. That remains a company decision, and it takes one short conversation.

If you are not sure who in your tenant is on which setting, the review is cheap. A Microsoft 365 security assessment lists release preferences along with other settings that drift over the years, and our IT governance service turns the answer into a written rule: who tests, who waits, who decides.

A simple rule you can write on one page

When we set this up for a customer, the whole policy fits in five lines. Standard is the default for the company. One named tester per ten staff, with a deputy, is on Standard while everyone else is on Deferred. Nobody is on Frontier unless the owner approves it in writing. The person who reads the Message Center each week is named. And the screenshot from step 2 is saved with the date.

That is not a heavy process, and it is the part Microsoft cannot do for you. The new settings page arrives in November. The decision about who goes first is still yours.