SOLVED

At what stage a feature is announced in Office 365 message centre

%3CLINGO-SUB%20id%3D%22lingo-sub-774694%22%20slang%3D%22en-US%22%3ERe%3A%20At%20what%20stage%20a%20feature%20is%20announced%20in%20Office%20365%20message%20centre%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-774694%22%20slang%3D%22en-US%22%3EIts%20when%20the%20feature%20is%20ready%20for%20general%20rollout%20and%20theres%20an%20ETA%20for%20it%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-774700%22%20slang%3D%22en-US%22%3ERe%3A%20At%20what%20stage%20a%20feature%20is%20announced%20in%20Office%20365%20message%20centre%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-774700%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F378311%22%20target%3D%22_blank%22%3E%40Justin_J945%3C%2FA%3E%26nbsp%3Bthis%20is%20a%20great%20question%20that%2C%20unfortunately%2C%20does%20not%20have%20a%20good%20answer.%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20how%20it%20supposed%20to%20work%26nbsp%3B%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%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%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20It%20is%20very%20inconsistent%2C%20each%20app%2Fservice%20team%20handles%20this%20differently%20and%20many%20of%20them%20do%20not%20even%20use%20the%20Targeted%20Release%20process.%20This%20issue%20has%20existed%20for%20many%20years%20and%20continues%20to%20be%20a%20source%20of%20frustration%20for%20many%20of%20us.%26nbsp%3B%3C%2FP%3E%3CP%3EWhile%20some%20features%20are%20deployed%20to%20individual%20users%20that%20have%20been%20identified%20as%20Targeted%20Release%20participants%2C%20others%20are%20sent%20to%20Tenants%20that%20are%20flagged%20as%20Targeted%20while%20others%20are%20not%20deployed%20to%20either%20of%20these%20and%20they%20just%20show%20up.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-774651%22%20slang%3D%22en-US%22%3EAt%20what%20stage%20a%20feature%20is%20announced%20in%20Office%20365%20message%20centre%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-774651%22%20slang%3D%22en-US%22%3E%3CP%3EI%20understand%20that%20there%20are%20various%20stages%20(pre-release%2C%20private%20preview%2C%20public%20preview%20and%20so%20on)%20that%20each%20Office%20365%20feature%20has%20to%20go%20through%20before%20it%20appears%20in%20our%20Office%20365%20message%20centre.%20At%20what%20stage%20Microsoft%20decides%20that%20a%20specific%20feature%20is%20announced%2Fpublished%20in%20our%20Office%20365%20Message%20centre%20tenant%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJ%20Justin%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-774651%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

I understand that there are various stages (pre-release, private preview, public preview and so on) that each Office 365 feature has to go through before it appears in our Office 365 message centre. At what stage Microsoft decides that a specific feature is announced/published in our Office 365 Message centre tenant?

 

Regards

 

J Justin

 

2 Replies
Highlighted
Its when the feature is ready for general rollout and theres an ETA for it
Highlighted
Best Response confirmed by Justin_J945 (Occasional Contributor)
Solution

@Justin_J945 this is a great question that, unfortunately, does not have a good answer. 

This is how it supposed to work https://docs.microsoft.com/en-us/office365/admin/manage/release-options-in-office-365?view=o365-worl... 

 

However, It is very inconsistent, each app/service team handles this differently and many of them do not even use the Targeted Release process. This issue has existed for many years and continues to be a source of frustration for many of us. 

While some features are deployed to individual users that have been identified as Targeted Release participants, others are sent to Tenants that are flagged as Targeted while others are not deployed to either of these and they just show up.