Targeted release for particular users

%3CLINGO-SUB%20id%3D%22lingo-sub-309633%22%20slang%3D%22en-US%22%3ETargeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309633%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20question%20around%20how%20targeted%20release%20for%20specific%20users%20works%20for%20Office%20365%20(I%20am%20not%20talking%20about%20client%20applications).%20I%20can%20see%20for%20certain%20features%20which%20are%20user-centric%20that%26nbsp%3Bthis%20makes%20sense.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20base%20platform%20things%20though%20I%20can't%20see%20how%20that%20would%20work%20for%20everything.%20If%20you%20have%20a%20fundamental%20change%20to%20the%20underlying%20platform%20then%20surely%20that%20is%20an%20all%20or%20nothing%20change%20for%20all%20users%3F%20It%20could%20be%20targeted%20in%20that%20it%20is%20applied%20for%20all%20users%20or%20if%20you%20chose%20certain%20users%20only%20then%20that%20particular%20change%20is%20held%20back%20until%20standard%20release%3F%20Is%20there%20any%20documentation%20for%20this%20anywhere%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-309633%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309788%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309788%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20never%20been%20able%20to%20find%20a%20listing%20of%20which%20services%2Fapps%20actually%20use%20the%20Targeted%20Release%20process.%20I%20know%20for%20sure%20that%20Teams%2C%20Yammer%2C%20PowerApps%2C%20Flow%2C%20and%20PowerBI%20do%20NOT.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChanges%20to%20the%20Security%20and%20Compliance%20Center%20services%20do%20not%20seem%20to%20use%20it.%3C%2FP%3E%3CP%3EChanges%20to%20the%20O365%20and%20other%20Admin%20Centers%20do%20not%20use%20it%2C%20i.e%2C%20you%20have%20have%20some%20admins%20test%20some%20new%20admin%20features%20before%20other%20admins.%20However%2C%20each%20global%20admin%20can%20decide%20to%20use%20the%20new%20Preview%20version%20of%20the%20Admin%20center%20if%20they%20want%20to.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20stuff%20from%20SPO%20does%20go%20through%20it%20but%20a%20lot%20does%20not.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309787%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309787%22%20slang%3D%22en-US%22%3EIt%20sounds%20like%20the%20solution%2C%20from%20what%20you%20are%20saying%20Mark%20is%20to%20have%20all%20users%20on%20the%20standard%20release%20which%20will%20avoid%20the%20issues%20of%20having%20any%20users%20on%20targeted.%20I%20don't%20think%20anything%20from%20our%20personal%20experiences%20point%20towards%20targeted%20for%20either%20a%20subset%20of%20users%20or%20the%20whole%20organisation.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309769%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309769%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20a%20good%20point%20actually.%20I%20wasn't%20aware%20that%20a%20fair%20amount%20of%20stuff%20might%20bypass%20targeted%20release...it's%20all%20a%20bit%20wild%20west%20then.%20If%20you%20happen%20to%20build%20processes%2C%20both%20people%20and%20code%20based%20it%20can%20take%20a%20long%20time%20to%20get%20those%20changed%20in%20a%20large%20corp%20environment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309755%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309755%22%20slang%3D%22en-US%22%3EThe%20biggest%20issues%20I%20have%20with%20the%20Targeted%20Release%20process%2C%20is%20the%20fact%20that%20many%20services%2Fapps%20don't%20use%20this%20process%20and%20many%20feature%20updates%20just%20show%20up%20and%20the%20only%20way%20to%20know%20that%20you%20have%20it%20is%20trial%20and%20error.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20problem%20with%20having%20a%20separate%20tenant%2C%20is%20that%20there%20is%20no%20way%20to%20control%20which%20tenant%20gets%20an%20update.%20It%20is%20quite%20possible%20for%20a%20%22Prod%22%20tenant%20to%20get%20an%20update%20before%20a%20%22Test%22%20tenant.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309724%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309724%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20-%20I%20figured%20as%20much%20and%20I%20guess%20in%20those%20cases%20they%20just%20hold%20it%20back%20until%20ready%20for%20everyone.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20reason%20I%20am%20after%20clarification%20is%20in%20designing%20a%20path%20to%20live%20for%20a%20large%20corporate.%20There%20was%20a%20feeling%20internally%20that%20we%20could%20simply%20assign%20only%20some%20users%20to%20be%20on%20targeted%20release%20and%20that%20would%20give%20us%20enough%20of%20a%20heads%20up%20to%20some%20of%20the%20changes%20coming.%20I%20feel%20that%20really%20you%20need%20at%20least%20a%20whole%20environment%20before%20prod%20on%20Standard%20release%20which%20is%20where%20you%20test%20and%20then%20another%20one%20before%20that%20on%20targeted%20for%20everyone%20in%20order%20to%20see%20upcoming%20changes%20across%20the%20board.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309721%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309721%22%20slang%3D%22en-US%22%3EBeing%20on%20targeted%20release%2C%20you%20won't%20get%20all%20the%20changes%20that%20say%20a%20first%20release%20entire%20tenant%20would%20see%20due%20to%20some%20things%20requiring%20like%20you%20said%20entire%20back%20end%20changes.%20Sometimes%20from%20my%20experience%20as%20well%20you%20will%20get%20a%20feature%20but%20it%20won't%20work%20for%20those%20users%20because%20it's%20not%20all%20users.%20It%20may%20have%20changed%20recently%20where%20they%20do%20a%20better%20job%20of%20that%2C%20but%20tenants%20with%20select%20users%20won't%20get%20ALL%20the%20exact%20same%20features%20that%20a%20tenant%20set%20to%20that%20will%20all%20the%20time%2C%20but%20most%20of%20the%20time%20the%20Select%20Users%20will%20get%20them%20first.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309653%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309653%22%20slang%3D%22en-US%22%3E%3CP%3ESure%2C%20I%20get%20what%20you%20mean.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20always%20goes%20through%20the%20Targeted%20%26gt%3B%20Standard%20cycle%20as%20per%20that%20article.%20There%20is%20also%20the%20option%20of%20having%20users%20added%20to%20the%20insider%20programs%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOffice%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Finsider.office.com%2Fen-us%2F%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Finsider.office.com%2Fen-us%2F%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20365%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Finsider.windows.com%2Fen-us%2Fsignup%2Fmicrosoft-365-insider-please-sign-in%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Finsider.windows.com%2Fen-us%2Fsignup%2Fmicrosoft-365-insider-please-sign-in%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20insider%20programs%20are%20to%20test%20and%20feedback%20on%20the%20bleeding%20edge%20functionality%20prior%20to%20it%20entering%20targeted%20release.%20I%20would%20advise%20caution%20on%20enrolling%20users%20into%20insider%20programs%20because%20these%20can%20have%20a%20number%20of%20bugs%20and%20cause%20issues%20on%20machines.%20Some%20applications%20such%20as%20Teams%20have%20developer%20previews%20which%20are%20designed%20for%20developers%20to%20get%20early%20access%20to%20builds%20in%20order%20to%20develop%20and%20test%20applications.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhether%20to%20have%20a%20subset%20of%20users%20on%20Targeted%20is%20really%20a%20personal%20choice.%20Some%20organisations%20I%20work%20with%20would%20say%20it%20is%20essential%20in%20order%20to%20preview%20functionality%20so%20it%20helps%20IT%20be%20ahead%20of%20the%20curve%20when%20the%20rest%20of%20the%20organisation%20is%20on%20the%20standard%20release.%20This%20is%20more%20prevalent%20in%20larger%20organisations%20with%20dedicated%20IT%20Teams%20Other%20organisations%20just%20have%20the%20whole%20organisation%20on%20the%20standard%20release%20once%20the%20functionality%20has%20been%20tried%20and%20tested.%20This%20is%20more%20common%20amongst%20SMB's%20or%20organisations%20which%20want%20a%20flat%20standardised%20release%20across%20all%20users.%20It%20is%20much%20rarer%20to%20have%20organisations%20wholly%20on%20the%20targeted%20release%3A%20these%20tend%20to%20be%20IT%2FPro%20Service%20organisations.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20helps!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%20Chris%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309645%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309645%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20but%20I%20should%20have%20probably%20been%20clearer%20in%20my%20question%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20read%20that%20documentation%20but%20I%20wanted%20to%20know%20if%20there%20are%20changes%20which%20can%20occur%20which%20do%20not%20go%20through%20the%20targeted%20-%26gt%3B%20standard%20cycle%20for%20certain%20users%20as%20it%20doesn't%20make%20sense%20to%20only%20have%20that%20particular%20change%20for%20a%20sub-set%20of%20users%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309635%22%20slang%3D%22en-US%22%3ERe%3A%20Targeted%20release%20for%20particular%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309635%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mark%3CBR%20%2F%3E%3CBR%20%2F%3ECertainly%20is%20documentation%20for%20Targeted%20release%20-%20right%20here%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fadmin%2Fmanage%2Frelease-options-in-office-365%3Fview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fadmin%2Fmanage%2Frelease-options-in-office-365%3Fview%3Do365-worldwide%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20stated%20in%20the%20article%20'%3CSPAN%3EYou%20can%20choose%20to%20have%20individuals%20or%20the%20entire%20organization%20receive%20updates%20early'%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EHope%20that%20helps%20and%20answers%20your%20question!%20If%20so%2C%20please%20like%20and%20set%20as%20the%20solution!%20If%20not%2C%20let%20me%20know%20what%20more%20you%20need.%20Thanks%20for%20raising%20this%20to%20the%20Tech%20Community.Best%2C%20Chris%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

I have a question around how targeted release for specific users works for Office 365 (I am not talking about client applications). I can see for certain features which are user-centric that this makes sense.

 

For base platform things though I can't see how that would work for everything. If you have a fundamental change to the underlying platform then surely that is an all or nothing change for all users? It could be targeted in that it is applied for all users or if you chose certain users only then that particular change is held back until standard release? Is there any documentation for this anywhere?

9 Replies
Highlighted

Hi Mark

Certainly is documentation for Targeted release - right here

https://docs.microsoft.com/en-us/office365/admin/manage/release-options-in-office-365?view=o365-worl...

 

As stated in the article 'You can choose to have individuals or the entire organization receive updates early'


Hope that helps and answers your question! If so, please like and set as the solution! If not, let me know what more you need. Thanks for raising this to the Tech Community.

Best, Chris

Highlighted

Thanks but I should have probably been clearer in my question :) 

 

I have read that documentation but I wanted to know if there are changes which can occur which do not go through the targeted -> standard cycle for certain users as it doesn't make sense to only have that particular change for a sub-set of users?

 

 

Highlighted

Sure, I get what you mean.

 

It always goes through the Targeted > Standard cycle as per that article. There is also the option of having users added to the insider programs

 

Office: https://insider.office.com/en-us/ 

Microsoft 365: https://insider.windows.com/en-us/signup/microsoft-365-insider-please-sign-in/

 

 

The insider programs are to test and feedback on the bleeding edge functionality prior to it entering targeted release. I would advise caution on enrolling users into insider programs because these can have a number of bugs and cause issues on machines. Some applications such as Teams have developer previews which are designed for developers to get early access to builds in order to develop and test applications.

 

Whether to have a subset of users on Targeted is really a personal choice. Some organisations I work with would say it is essential in order to preview functionality so it helps IT be ahead of the curve when the rest of the organisation is on the standard release. This is more prevalent in larger organisations with dedicated IT Teams Other organisations just have the whole organisation on the standard release once the functionality has been tried and tested. This is more common amongst SMB's or organisations which want a flat standardised release across all users. It is much rarer to have organisations wholly on the targeted release: these tend to be IT/Pro Service organisations.

 

Hope that helps!

 

Best, Chris

Highlighted
Being on targeted release, you won't get all the changes that say a first release entire tenant would see due to some things requiring like you said entire back end changes. Sometimes from my experience as well you will get a feature but it won't work for those users because it's not all users. It may have changed recently where they do a better job of that, but tenants with select users won't get ALL the exact same features that a tenant set to that will all the time, but most of the time the Select Users will get them first.
Highlighted

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. 

Highlighted
The biggest issues I have with the Targeted Release process, is the fact that many services/apps don't use this process and many feature updates just show up and the only way to know that you have it is trial and error.

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.
Highlighted

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.

Highlighted
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
Highlighted

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.