Forum Discussion
Targeted release for particular users
Thanks - I figured as much and I guess in those cases they just hold it back until ready for everyone.
The reason I am after clarification is in designing a path to live for a large corporate. There was a feeling internally that we could simply assign only some users to be on targeted release and that would give us enough of a heads up to some of the changes coming. I feel that really you need at least a whole environment before prod on Standard release which is where you test and then another one before that on targeted for everyone in order to see upcoming changes across the board.
The problem with having a separate tenant, is that there is no way to control which tenant gets an update. It is quite possible for a "Prod" tenant to get an update before a "Test" tenant.
That's a good point actually. I wasn't aware that a fair amount of stuff might bypass targeted release...it's all a bit wild west then. If you happen to build processes, both people and code based it can take a long time to get those changed in a large corp environment.
I have never been able to find a listing of which services/apps actually use the Targeted Release process. I know for sure that Teams, Yammer, PowerApps, Flow, and PowerBI do NOT.
Changes to the Security and Compliance Center services do not seem to use it.
Changes to the O365 and other Admin Centers do not use it, i.e, you have have some admins test some new admin features before other admins. However, each global admin can decide to use the new Preview version of the Admin center if they want to.
Some stuff from SPO does go through it but a lot does not.
- It sounds like the solution, from what you are saying Mark is to have all users on the standard release which will avoid the issues of having any users on targeted. I don't think anything from our personal experiences point towards targeted for either a subset of users or the whole organisation.
Best, Chris
