Microsoft Teams Release Processes - Why do I not see a feature but my colleague does?

Published Feb 02 2021 08:00 AM 45.1K Views
Microsoft

At Microsoft Teams, we frequently hear the question, “I am running the same version as my coworker, but they have a feature I don’t. Why don’t I have that feature now? And how can I get it now?” Before we answer that question, we want to shed some light on our overall release processes so that the answer makes sense.


As a productivity tool connecting hundreds of millions of people around the world and enabling remote work, remote learning, and connections with family and friends, we take a very orchestrated approach to how we roll out and enable new features. We have multiple updates that get rolled out: web, desktop (Windows, Mac, Linux), mobile (iOS, Android), packages for conference room devices, and our backend services. Each of these packages are backed by feature flag configurations that let us ship a new Teams version and enable features separately.


When we roll out features, it consists of two activities:

  1. Shipping the version (Teams application version with code for new features included)
  2. Enabling the feature through the feature flag

Both activities happen progressively, but at different times. We first ship the build with the feature flags turned off. We progressively roll out the build to users, wait for the build to be picked up and used by users, and reach certain penetration rates. We’ll run scorecards for key performance and usage metrics between the prior build and the new build to ensure we are not introducing any form of regression with our latest version.


Once we have scorecards and confidence in the version, we can then begin to progressively enable our feature flags – making the new features available for users. For our larger, external customer facing rings, this is a multiple step process that usually happens over a few days.


Below is a high-level view of our audience segmentation. Each ring represents an audience with specific gating criteria to allow us to exit the build and the feature flag, and to progress them to the next ring.

Jessie_Hwang_0-1612282675618.png

When we begin rolling out feature flags within a ring is where you will usually see differences in features within the same version. We roll features and versions out on in increasing % tranches at user level (considering the worldwide user pool and not at an organization/tenant level) as it gives us the best cross section of use cases, hardware configurations, software configurations, network topology, bandwidth availability, etc., to validate our changes and the user experience they provide – but this does mean that co-workers on the same build can see differences in their features. Rolling out feature flags by organization introduces the potential to bias our results with similar hardware, bandwidth, and usage patterns, so we focus on getting a cross section of users and usage patterns with our rollouts.


In December 2020 we announced the availability of Teams Public Preview. Public Preview is a great mechanism to expose a subset of your user base to features a little ahead of everyone else. This allows you to get familiar with new features before they are available to all users.


Launch of Microsoft Teams preview experience and alignment with Microsoft 365 deployment channels | ...


Public preview in Microsoft Teams - Microsoft Teams | Microsoft Docs


Teams-Updates - Microsoft Teams | Microsoft Docs

 

37 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-2110426%22%20slang%3D%22en-US%22%3EMicrosoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2110426%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20Microsoft%20Teams%2C%20we%20frequently%20hear%20the%20question%2C%20%E2%80%9CI%20am%20running%20the%20same%20version%20as%20my%20coworker%2C%20but%20they%20have%20a%20feature%20I%20don%E2%80%99t.%20Why%20don%E2%80%99t%20I%20have%20that%20feature%20now%3F%20And%20how%20can%20I%20get%20it%20now%3F%E2%80%9D%20Before%20we%20answer%20that%20question%2C%20we%20want%20to%20shed%20some%20light%20on%20our%20overall%20release%20processes%20so%20that%20the%20answer%20makes%20sense.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EAs%20a%20productivity%20tool%20connecting%20hundreds%20of%20millions%20of%20people%20around%20the%20world%20and%20enabling%20remote%20work%2C%20remote%20learning%2C%20and%20connections%20with%20family%20and%20friends%2C%20we%20take%20a%20very%20orchestrated%20approach%20to%20how%20we%20roll%20out%20and%20enable%20new%20features.%20We%20have%20multiple%20updates%20that%20get%20rolled%20out%3A%20web%2C%20desktop%20(Windows%2C%20Mac%2C%20Linux)%2C%20mobile%20(iOS%2C%20Android)%2C%20packages%20for%20conference%20room%20devices%2C%20and%20our%20backend%20services.%20Each%20of%20these%20packages%20are%20backed%20by%20feature%20flag%20configurations%20that%20let%20us%20ship%20a%20new%20Teams%20version%20and%20enable%20features%20separately.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EWhen%20we%20roll%20out%20features%2C%20it%20consists%20of%20two%20activities%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EShipping%20the%20version%20(Teams%20application%20version%20with%20code%20for%20new%20features%20included)%3C%2FLI%3E%0A%3CLI%3EEnabling%20the%20feature%20through%20the%20feature%20flag%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EBoth%20activities%20happen%20progressively%2C%20but%20at%20different%20times.%20We%20first%20ship%20the%20build%20with%20the%20feature%20flags%20turned%20off.%20We%20progressively%20roll%20out%20the%20build%20to%20users%2C%20wait%20for%20the%20build%20to%20be%20picked%20up%20and%20used%20by%20users%2C%20and%20reach%20certain%20penetration%20rates.%20We%E2%80%99ll%20run%20scorecards%20for%20key%20performance%20and%20usage%20metrics%20between%20the%20prior%20build%20and%20the%20new%20build%20to%20ensure%20we%20are%20not%20introducing%20any%20form%20of%20regression%20with%20our%20latest%20version.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EOnce%20we%20have%20scorecards%20and%20confidence%20in%20the%20version%2C%20we%20can%20then%20begin%20to%20progressively%20enable%20our%20feature%20flags%20%E2%80%93%20making%20the%20new%20features%20available%20for%20users.%20For%20our%20larger%2C%20external%20customer%20facing%20rings%2C%20this%20is%20a%20multiple%20step%20process%20that%20usually%20happens%20over%20a%20few%20days.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EBelow%20is%20a%20high-level%20view%20of%20our%20audience%20segmentation.%20Each%20ring%20represents%20an%20audience%20with%20specific%20gating%20criteria%20to%20allow%20us%20to%20exit%20the%20build%20and%20the%20feature%20flag%2C%20and%20to%20progress%20them%20to%20the%20next%20ring.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Jessie_Hwang_0-1612282675618.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F251423i761A8C39CE6A401C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Jessie_Hwang_0-1612282675618.png%22%20alt%3D%22Jessie_Hwang_0-1612282675618.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWhen%20we%20begin%20rolling%20out%20feature%20flags%20within%20a%20ring%20is%20where%20you%20will%20usually%20see%20differences%20in%20features%20within%20the%20same%20version.%20We%20roll%20features%20and%20versions%20out%20on%20in%20increasing%20%25%20tranches%20at%20user%20level%20(considering%20the%20worldwide%20user%20pool%20and%20not%20at%20an%20organization%2Ftenant%20level)%20as%20it%20gives%20us%20the%20best%20cross%20section%20of%20use%20cases%2C%20hardware%20configurations%2C%20software%20configurations%2C%20network%20topology%2C%20bandwidth%20availability%2C%20etc.%2C%20to%20validate%20our%20changes%20and%20the%20user%20experience%20they%20provide%20%E2%80%93%20but%20this%20does%20mean%20that%20co-workers%20on%20the%20same%20build%20can%20see%20differences%20in%20their%20features.%20Rolling%20out%20feature%20flags%20by%20organization%20introduces%20the%20potential%20to%20bias%20our%20results%20with%20similar%20hardware%2C%20bandwidth%2C%20and%20usage%20patterns%2C%20so%20we%20focus%20on%20getting%20a%20cross%20section%20of%20users%20and%20usage%20patterns%20with%20our%20rollouts.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EIn%20December%202020%20we%20announced%20the%20availability%20of%20Teams%20Public%20Preview.%20Public%20Preview%20is%20a%20great%20mechanism%20to%20expose%20a%20subset%20of%20your%20user%20base%20to%20features%20a%20little%20ahead%20of%20everyone%20else.%20This%20allows%20you%20to%20get%20familiar%20with%20new%20features%20before%20they%20are%20available%20to%20all%20users.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams-blog%2Flaunch-of-microsoft-teams-preview-experience-and-alignment-with%2Fba-p%2F1964899%22%20target%3D%22_blank%22%3ELaunch%20of%20Microsoft%20Teams%20preview%20experience%20and%20alignment%20with%20Microsoft%20365%20deployment%20channels%20%7C%20Microsoft%20Tech%20Community%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FMicrosoftTeams%2Fpublic-preview-doc-updates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPublic%20preview%20in%20Microsoft%20Teams%20-%20Microsoft%20Teams%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmicrosoftteams%2Fteams-client-update%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETeams-Updates%20-%20Microsoft%20Teams%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2110426%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20Microsoft%20Teams%2C%20we%20frequently%20hear%20the%20question%2C%20%E2%80%9CI%20am%20running%20the%20same%20version%20as%20my%20coworker%2C%20but%20they%20have%20a%20feature%20I%20don%E2%80%99t.%20Why%20don%E2%80%99t%20I%20have%20that%20feature%20now%3F%20And%20how%20can%20I%20get%20it%20now%3F%E2%80%9D%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2110426%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeployment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115928%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115928%22%20slang%3D%22en-US%22%3E%3CP%3EDon't%20get%20me%20started%20on%20appdata%20installation%20%3A)%3C%2Fimg%3E%20I%20am%20now%20in%20the%20process%20of%20remediation%20RCE%20vulnerability%20in%20Teams%20and%20having%20fun%20going%20through%20machines%20and%20deleting%20ancient%20Teams%20versions%20from%20users%20profiles.%20Sometimes%205%2C%20sometimes%2012%20(multi%20user%20desktops).%20At%20least%20don't%20make%20Teams%20automatically%20start%20and%20auto%20install%20when%20user%20just%20logs%20in%20into%20system%20and%20maybe%20has%20no%20interest%20in%20using%20Teams.%20Also%20fun%20in%20VDI%20when%20working%20on%20updating%20images%2C%20etc.%20and%20having%20to%20close%20that%20annoying%20login%20window%20jumping%20at%20you%20every%20time.%20MS%20is%20giving%20you%20tools%20fighting%20Shadow%20IT%20and%20yet%20on%20another%20hand%20gladly%20lending%20it%20to%20users.%20%22What%3F%20Administrative%20permissions%20to%20install%20apps.%20Please!%20You%20don't%20need%20that%20for%20Teams.%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115487%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115487%22%20slang%3D%22en-US%22%3E%3CP%3ERespectfully%2C%20while%20this%20information%20is%20helpful%20for%20those%20of%20us%20who%20are%20IT%20admins%2C%20our%20end%20users%20just%20don't%20care.%20They%20are%20only%20frustrated%20that%20their%20coworkers%20have%20access%20to%20features%20that%20they%20do%20not.%20This%20makes%20change%20management%20for%20larger%20organizations%20very%20difficult%20-%20especially%20since%20now%20many%20of%20us%20are%20completely%20wedded%20to%20Teams%20for%20UC.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115345%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115345%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F731911%22%20target%3D%22_blank%22%3E%40IanMurphy48%3C%2FA%3E%26nbsp%3B%20--%20on%20the%20part%20you%20mentioned%20about%26nbsp%3B%20--%3CEM%3Erefuse%20to%20update%3C%2FEM%3E---%2C%26nbsp%3B%20%26nbsp%3B%20perhaps%20you%20have%20seen%20this%20discussion%3A%3CBR%20%2F%3E--Force%20Teams%20desktop%20client%20update%20--%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams%2Fforce-teams-desktop-client-update%2Fm-p%2F2056566%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams%2Fforce-teams-desktop-client-update%2Fm-p%2F2056566%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E---%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115235%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115235%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20traditional%20Office%20products%20do%20a%20good%20job%20of%20notifying%20the%20users%20about%20new%20features%2C%20it%20would%20be%20helpful%20if%20Teams%20provided%20a%20What%E2%80%99s%20New%20panel%20like%20they%20do%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115180%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115180%22%20slang%3D%22en-US%22%3E%3CP%3EAgree%20with%20ron%20S.%20Why%20it%20can't%20be%20just%20build%20number%20that%20would%20explain%20what%20version%20of%20the%20program%20I%20people%20have%20(%3Dwhat%20features%20are%20available)%3F%20The%20updates%20are%20quire%20frequent%2C%20so%20it's%20quite%20impossible%20to%20know%20if%20everyone%20in%20my%20organization%20has%20the%20same%20features%20enable.%20In%20addition%2C%20on%20corporate%20level%20some%20features%20might%20be%20turned%20off%20so%20looking%20at%20Microsoft%20help%20pages%20won't%20help%20since%20the%20feature%20might%20not%20be%20turned%20on%20by%20my%20corporation.%20And%20one%20more%20annoyance%20is%20the%20really%20long%20period%20of%20rollouts..%20New%20features%20are%20announced%20big%2C%20but%20the%20roll%20out%20to%20all%20users%20might%20take%20months.%20That's%20why%20I%20don't%20even%20look%20at%20the%20news%20about%20new%20features%20since%20it%20might%20take%20looooong%20time%20before%20I'm%20able%20to%20use%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2114879%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2114879%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20does%20this%20map%20to%20the%20different%20types%20of%20Tenants%20(e.g.%20gcc%2C%20edu%2C%20etc...).%20Is%20this%20process%20repeated%20for%20each%20type%20of%20tenant%2C%20or%20are%20they%20brought%20in%20a%20different%20points%20as%20the%20feature%20is%20made%20public%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2113758%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2113758%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20you%20should%20have%20posted%20it%20on%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2F%3C%2FA%3E%20as%20this%20blog%20post%20is%20only%20about%20Teams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2113550%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2113550%22%20slang%3D%22en-US%22%3E%3CP%3EPS%3A%20I%20have%20submitted%20a%20%22feedback%22%20in%20Word%20UserVoice%20%22Display%20%22Feature%20Flags%22%20to%20users%22%20(I%20intend%20it%20as%20a%20global%20%22Office%22%20feedback%2C%20not%20just%20Word%20specific)%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fword.uservoice.com%2Fforums%2F304924-word-for-windows-desktop-application%2Fsuggestions%2F42618259-display-feature-flags-to-users%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fword.uservoice.com%2Fforums%2F304924-word-for-windows-desktop-application%2Fsuggestions%2F42618259-display-feature-flags-to-users%3C%2FA%3E%3C%2FP%3E%3CP%3EEveryone%20who%20has%20commented%2C%20please%20vote%20and%20comment%20on%20this%3C%2FP%3E%3CP%3E.%3C%2FP%3E%3CP%3EDon%20K%3A%3C%2FP%3E%3CP%3EI%20believe%20your%20understanding%20is%20not%20quite%20on.%26nbsp%3B%20As%20I%20understand%20it%2C%20the%20%22feature%20flags%22%20are%20implemented%20at%20the%20user%20level%2C%20not%20the%20corporate%20level.%20I%20suspect%20they%20are%20%22secret%22%20registry%20keys%20on%20the%20computer.%26nbsp%3B%20Maybe%20flags%20hidden%20in%20the%20%22MS%20Account%22%20information.%26nbsp%3B%20Either%20way%2C%20users%20have%20to%20see%20this%20information!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2113533%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2113533%22%20slang%3D%22en-US%22%3E%3CP%3EI%20do%20support%20on%20the%20MS%20Answers%20forum%2Fcommunity.%26nbsp%3B%20We%20constantly%20get%20this%20question.%3C%2FP%3E%3CP%3E.%3C%2FP%3E%3CP%3EYour%20excuse%20is%20WORTHLESS!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20we%20users%20can%20see%20is%3A%3C%2FP%3E%3CUL%3E%3CLI%3EVersion%20number%2C%3C%2FLI%3E%3CLI%3Ebuild%20number%20and%3C%2FLI%3E%3CLI%3EChannel%3C%2FLI%3E%3C%2FUL%3E%3CP%3EIn%20the%20rest%20of%20the%20development%20world%20that%20would%20be%20enough%20information%20to%20uniquely%20identify%20what%20features%20we%20should%20be%20able%20to%20see%20in%20our%20applications.%20Different%20features%2C%20different%20build%20number!%3C%2FP%3E%3CP%3E.%3C%2FP%3E%3CP%3EIf%20you%20want%20to%20play%20silly%20b**gers%20with%20%22feature%20flags%22%2C%20fine.%20But%20YOU%20MUST%20EXPOSE%2FDISPLAY%20those%20flags%20(with%20publicly%20available%20explanation%20documentation)%20TO%20USERS!%20At%20the%20very%20least%20give%20us%20documentation%20telling%20us%20what%20registry%20keys%20to%20look%20at!%3C%2FP%3E%3CP%3E.%3C%2FP%3E%3CP%3E%22You%22%20(generically%20MS%20(mis)management)%20are%20obviously%20oblivious%20to%20the%20waste%20of%20user%20and%20user%20corporate%20time%20(and%20money)%20and%20the%20angst%20you%20are%20inflicting%20on%20your%20users!%3C%2FP%3E%3CP%3E(have%20you%20gotten%20the%20idea%20that%20I%20feel%20strongly%20about%20this%20issue%3F)%3C%2FP%3E%3CP%3E.%3C%2FP%3E%3CP%3EFix%20this%20problem%20in%20ALL%20Office%2F%22%3CEM%3EMicrosoft%20365%3C%2FEM%3E%22%20(stupid%20name%20change%2C%20a%20rant%20for%20another%20time)%20applications!%26nbsp%3B%20Display%20this%2Fthese%20%22flag(s)%22%20in%20the%20File%20menu%20%26gt%3B%20Account%20command%20%26gt%3B%20About%20information.%26nbsp%3B%3C%2FP%3E%3CP%3EPLEASE!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2113245%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2113245%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20about%20giving%20visibility%20to%20enabled%2Fdormant%20flags%3F%20Maybe%20there%20can%20be%20a%20dashboard%20in%20Teams%20admin%20center%20showing%20which%20part%20of%20tenant%20users%20is%20on%20which%20version%20and%20which%20flags%20(features)%20are%20currently%20enabled%20and%20which%20are%20not%20yet%20for%20some%20users%20with%20an%20approximate%20ETA%20on%20enablement%20(which%20should%20change%20dynamically%20based%20on%20roll%20out%20progress%2C%20issues%20found%2C%20etc.).%20And%20maybe%20even%20in%20the%20client%20in%20some%20section%20about%20what's%20new%2C%20coming%20features%2C%20show%20a%20list%20of%20major%20features%20with%20a%20checkmark%2C%20if%20it%20is%20enabled%20on%20this%20client%20and%20some%20sort%20of%20%22coming%20in%20x%20weeks%22%20for%20the%20not%20enabled%20yet%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2113181%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2113181%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20was%20not%20all%20of%20the%20information%20I%20was%20looking%20for%2C%20but%20it%20is%20a%20start.%20While%20I%20understand%20that%20MS%20needs%20the%20time%20to%20roll%20out%20features%2C%20having%20some%20users%20have%20disparate%20experiences%20tends%20to%20degrade%20the%20user%20experience.%20For%20instance%2C%20the%20Teams%20Together%20Mode.%20One%20user%20can%20have%20it%2C%20and%20others%2C%20wanting%20to%20use%20it%20will%20not.%20That%20creates%20a%20disparate%20experience%20where%20if%20someone%20wants%20to%20kick%20off%20that%20new%20experience%20in%20their%20next%20meeting%2C%20because%20they're%20excited%20to%20share%20what%20they've%20learned%2C%20they%20don't%20have%20the%20feature.%20-%20Bad%20user%20experience%20and%20also%20creating%20issues%20with%20level%201%20support%20seeking%20further%20clarification%20as%20to%20why%20they%20don't%20have%20that%20feature.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20would%20suggest%20Microsoft%20do%20is%20create%20talking%20points%20that%20would%20be%20available%20through%20their%20Microsoft%20adoption%20guides.%20It's%20important%20to%20note%20this%20and%20not%20just%20stumble%20upon%20this%20information.%20We%20need%20to%20be%20able%20to%20speak%20to%20it%20and%20temper%20the%20expectations%20of%20our%20own%20user%20base.%20I'll%20be%20able%20to%20take%20this%20information%20and%20craft%20it%20into%20a%20watered-down%20version%20for%20my%20company.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2112892%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2112892%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20are%20right.%20I%20was%20downgrading%20my%20Teams%20client%20some%20time%20ago%20and%20was%20surprised%20to%20see%20Presence%20scheduling%20option%20working%20in%20a%20much%20older%20version%2C%20when%20this%20option%20just%20appeared%20as%20available%20a%20few%20days%20ago%20at%20that%20point..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20only%20guess%2C%20but%20maybe%20some%20users%20don't%20get%20Together%20Mode%20because%20of%20hardware%20restrictions.%20But%20i%20would%20rather%20guess%20features%20are%20not%20actually%20trickling%20down%20in%20a%20few%20days%20as%20MS%20brags.%20Not%20a%20first%20or%20second%20time%20i%20am%20waiting%20for%20months%20to%20get%20some%20new%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2112617%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2112617%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139606%22%20target%3D%22_blank%22%3E%40Don%20Kirkham%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20much%20I%20have%20learnt%2C%20the%20flags%20and%20versions%20are%20not%20going%20hand%20by%20hand.%20The%20features%20seems%20to%20be%20written%20into%20the%20earlier%20versions%20of%20the%20clients%20already%2C%20but%20are%20disabled%20until%20the%20flags%20on%20tenant%20enables%20it.%20Because%20of%20that%2C%20you%20could%20have%20older%20version%20from%20client%20(not%20too%20old)%20and%20still%20get%20the%20same%20features%20than%20newer%20clients.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2112593%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2112593%22%20slang%3D%22en-US%22%3E%3CP%3EBased%20on%20this%20blog%2C%20once%20the%20new%20version%20is%20deployed%20to%20the%20tenant%20and%20the%20feature%20flag%20is%20turned%20on%2C%20everyone%20in%20the%20tenant%20should%20see%20the%20new%20feature.%20That%20is%20not%20my%20experience.%20I%20have%20users%20that%20are%20on%20the%20latest%20version%2C%20but%20still%20can't%20see%20features%20(like%20Together%20Mode)%20that%20have%20been%20out%20for%20months.%20Other%20users%20in%20the%20same%20tenant%20have%20all%20of%20the%20latest%20features.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20something%20else%20we%20need%20to%20do%20on%20a%20device%20or%20user%20level%20to%20ensure%20new%20features%20are%20available%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2112563%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2112563%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%2C%20when%20we%20push%20Teams%20client%20via%20package%20using%20version%201.3%20vs%201.4%2C%20where%20we%20can%20check%20which%20features%20are%20added%20in%201.4%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2112533%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2112533%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Martin.%20This%20is%20something%20we%20deal%20with%20customers%20on%20frequent%20basis.%20having%20a%20public%20blog%20definitely%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2111991%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2111991%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20doesn't%20really%20answer%20the%20question%20of%20how%20to%20ensure%20all%20those%20in%20the%20same%20ring%20and%20in%20the%20same%20tenant%20get%20the%20updates%20as%20quickly%20as%20they%20can%20*%3CSTRONG%3Ewithin%3C%2FSTRONG%3E*%20that%20tenant.%26nbsp%3B%20That%20is%20the%20main%20question%20we%20(IT)%20face%20every%20time%20a%20new%20set%20of%20features%20is%20rolled%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20solve%20this%20by%20pushing%20to%20everyone%20in%20the%20same%20tenant%20for%20whichever%20release%20ring%20they%20are%20in.%26nbsp%3B%20This%20just%20creates%20more%20work%20for%20IT%20groups%20everywhere%20like%20it%20is%20now%20and%20always%20makes%20users%20question%20if%20something%20is%20working%20correctly%20or%20not%20when%20their%20colleague%20on%20the%20same%20team%20gets%20new%20features%20they%20do%20not%20yet%20have%20themselves%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2111850%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2111850%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20to%20you%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2251%22%20target%3D%22_blank%22%3E%40Martin%20Rinas%3C%2FA%3E%20to%20sharing%20this.%20But%20I%20believe%20the%20biggest%20problem%20on%20the%20organizational%20level%20is%20the%20transparency%20and%20predictability.%20I%20could%20use%20the%20client%20version%20report%20on%20CQD%20to%20see%20which%20version%20users%20are%20using%20and%20if%20new%20version%20is%20coming%2C%20I%20could%20see%20how%20widely%20it%20has%20been%20distributed.%20But%20as%20you%20told%20also%2C%20that%20is%20not%20the%20full%20picture.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20cannot%20see%20those%20feature%20flags%20from%20anywhere%20(%3F)%2C%20I%20cannot%20see%20on%20which%20rings%20we%20are%2C%20and%20I%20have%20no%20possibilities%20to%20see%20when%20certain%20feature%20rollout%20is%20starting%20to%20our%20end%20users.%20Are%20you%20planning%20to%20share%20any%20visibility%20to%20this%2C%20or%20is%20this%20just%20a%20cost%20we%20need%20to%20pay%20when%20using%20the%20cloud%20services%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20about%20the%20public%20preview%2C%20if%20we%20allow%20users%20to%20choose%20to%20use%20that%20option%2C%20how%20I%20could%20see%20who%20have%20accepted%20the%20preview%2C%20and%20of%20course%20in%20centralized%3F%20It%20could%20be%20a%20challenge%20for%20the%20support%20organization%20if%20people%20who%20have%20forgotten%20that%20they%20are%20part%20of%20the%20preview%20features%2C%20and%20start%20reporting%20odd%20user%20experiences.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2111761%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2111761%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20doesn't%20help%20in%20explaining%20users%20why%20they%20don't%20have%20a%20feature%20that%20another%20user%20has.%20This%20article%20will%20not%20help.%20They%20will%20still%20think%20they%20IT%20is%20dumb%20or%20doesn't%20care.%20Even%20personally%2C%20i%20just%20don't%20care%20about%20news%20about%20new%20features%2C%20because%20i%20know%20it%20can%20take%20months%20(not%20days)%20until%20you%20see%20it.%20Like%20with%20tasks%20in%20Teams%2C%20native%20notifications%20(where%3F)%20and%20so%20on.%20You%20are%20killing%20the%20excitement%20about%20new%20features%20with%20very%20long%20deployments%20and%20delays.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2111354%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2111354%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20receive%20this%20question%20on%20a%20regular%20basis.%20Thank%20you%20for%20helping%20clarify%20the%20process%20that%20your%20team%20takes.%20Keep%20up%20the%20good%20work!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2148776%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148776%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20I'm%20seeing%20is%20totally%20inconsistent%20with%20Teams%20mysteriously%20working%20perfectly%20and%20being%20up%20to%20date%20on%20some%20machines%20but%20on%20others%20I%20diligently%20push%20out%20the%20machine%20wide%20installer%20each%20few%20days%20but%20the%20user%20version%20just%20never%20updates.%20I%20have%20quite%20a%20few%20where%20the%20machine%20wide%20is%201.4.00.xxx%20and%20the%20user%20is%20still%20on%201.3.0.xxx%3C%2FP%3E%3CP%3EWorse%2C%20the%20msi%20installer%20will%20occasionally%20remove%20teams%20completely%20-%20with%20no%20errors%20logged%20as%20far%20as%20I%20can%20tell.%20It%20just%20disappears.%20I%20always%20run%20the%20msi%20with%20logging%20to%20a%20file%20and%20can't%20find%20any%20indication%20of%20why%20it%20would%20have%20just%20removed%20everything%20when%20it%20should%20have%20updated.%3C%2FP%3E%3CP%3EI%20have%20all%20of%20this%20automated%2C%20so%20whenever%20a%20new%20version%20comes%20out%20I%20push%20out%20the%20msi%20to%20hundreds%20of%20machines.%20I%20do%20this%20with%20many%20many%20applications%2C%20Teams%20is%20the%20worst%20to%20deal%20with.%20Acrobat%20comes%20a%20close%20second.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2149993%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2149993%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20come%20you%20are%20not%20just%20letting%20Teams%20update%20itself%3F%20It%20sounds%20like%20you%20may%20have%20created%20extra%20work%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2150206%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150206%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20IS%20updating%20itself%20once%20it%20gets%20to%20user%20AppData%20and%20user%20is%20using%20it.%20Ian%20is%20doing%20vain%20work%20by%20pushing%20msi%20over%20and%20over%20again.%20If%20use%20is%20not%20using%20it%2C%20it%20will%20stay%20the%20same%20version%20forever%20and%20eventually%20will%20be%20marked%20by%20security%20scanners%20for%20having%20some%20RCE.%20You%20can%20push%20msi%20to%20this%20machine%2C%20it%20will%20not%20update%20the%20version%20in%20AppData.%20Which%20is%20the%20same%20as%20if%20the%20user%20installed%20it%20on%20his%20own%20via%20exe%20from%20MS%20page.%20We%20are%20going%20to%20have%20Teams%20rollout%20soon%20using%20msi%20and%20i%20kind%20of%20dread%20this.%20As%20this%20will%20only%20create%20many%20more%20vulnerabilities.%20Especially%20on%20multi%20user%20machines.%20Because%20system%20wide%20installer%20%22conveniently%22%20activates%20when%20a%20new%20user%20logs%20in%20and%20copies%20its%20version%20at%20that%20point%20to%20user's%20profile%20and%20opens%20a%20sign%20in%20window.%20But%20if%20user%20ignores%20that%2C%20yeah%2C%20another%20obsolete%20vulnerable%20in%20future%20version%20sitting%20in%20user%20profile.%20MS%20it%20pushing%20Shadow%20IT%20with%20this%20design%20and%20then%20sells%20MCAS%20to%20control%20Shadow%20IT%20%3AD%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2132713%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2132713%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20an%20excellent%20blog%20post%20explaining%20how%20to%20ship%20features%20to%20users%20and%20separating%20deployments%20from%20releases.%20We%20run%20an%20agency%20and%20use%20feature%20flags%20extensively%20to%20enable%20features%20directly%20on%20our%20clients'%20websites%20and%20only%20for%20their%20internal%20team.%20This%20allow%20us%20to%20get%20the%20best%20possible%20feedback.%20We%20use%20a%20tool%20called%20%3CA%20href%3D%22https%3A%2F%2Funlaunch.io%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EUnlaunch%3C%2FA%3E%20due%20to%20its%20tiny%20size%20and%20overhead%20(had%20some%20concerns%20regarding%20other%20tools%20on%20page%20speed%20and%20performance.)%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20server%20teams%20uses%20the%20Java%20SDK%20to%20separate%20deployments%20from%20releases.%20We%20also%20use%20kill%20switches%20for%20Op%20toggles.%26nbsp%3B%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-2163328%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2163328%22%20slang%3D%22en-US%22%3E%3CP%3EBeing%20able%20to%20request%20that%20all%20users%20on%20smaller%20tenants%20(e.g.%20%26lt%3B%2010%2C000%20accounts)%20are%20synchronised%20on%20feature%20flags%20would%20be%20useful.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2206417%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2206417%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20other%20words%2C%20you're%20testing%20your%20code%20in%20production.%26nbsp%3B%20If%20it%20works%2C%20you%20continue%20rollout.%26nbsp%3B%20Got%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2408637%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2408637%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20like%20the%20way%20you%20roll%20these%20features%20out%20as%20it%20is%20very%20hard%20to%20support%20users%20when%20the%20IT%20staff%20doesn't%20have%20the%20features%20before%20a%20large%20portion%20of%20users%20and%20even%20with%20public%20preview%20enabled%20for%20IT%20staff%20not%20all%20of%20those%20features%20become%20available%20in%20advance.%20Microsoft%20PLEASE%20FIX%20your%20horrible%20roll%20out%20system!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115239%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115239%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20sort%20of%20makes%20sense%2C%20but%20then%20you%20find%20machines%20which%20are%20hopelessly%20out%20of%20date%20running%201.2%20releases%20which%20refuse%20to%20update.%20Surely%20downloading%20the%20msi%20from%20the%20web%20and%20running%20it%20on%20a%20machine%20should%20be%20all%20that%20is%20required%3F%20Maybe%20it%20won't%20get%20you%20onto%20the%20latest%20and%20greatest%20version%2C%20but%20at%20it%20should%20at%20least%20bring%20you%20up%20to%20a%20recent%20version%2C%20no%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20same%20goes%20for%20all%20these%20profile%20installed%20versions.%20I'd%20prefer%20to%20have%20only%20a%20machine-wide%20copy%20installed.%20Why%20is%20this%20not%20possible%3F%20Installing%20the%20machine%20wide%20installer%20should%20eliminate%20the%20copy%20installed%20in%20the%20users%20folder%2C%20but%20it%20never%20does.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThings%20are%20ok%20at%20the%20moment%2C%20but%20they%20day%20someone%20discovers%20a%20major%20security%20bug%20in%20the%20client%20and%20we%20all%20have%20to%20urgently%20update%20to%20version%201.x%20this%20is%20going%20to%20become%20a%20major%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2438154%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2438154%22%20slang%3D%22en-US%22%3E%3CP%3EI%20totally%20agree%20with%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F17756%22%20target%3D%22_blank%22%3E%40Jeffrey%20Allen%3C%2FA%3E%20comments%20above%20and%20I%20am%20having%20difficulty%20understanding%20Microsoft's%20roll%20out%20logic.%20How%20the%20hell%20are%20O365%20Admins%20supposed%20to%20stay%20ahead%20of%20the%20curve%20with%20regards%20to%20testing%2C%20updating%20documentation%2C%20training%20and%20pre-informing%20users%20of%20upcoming%20updates.%20You%20get%20to%20work%20and%20find%20out%20that%20half%20the%20tenant%20suddenly%20has%20new%20features%20and%20the%20other%20half%20don't.%20All%20users%20have%20the%20same%20client%20version%20and%20I'm%20tired%20of%20checking%20forums%20every%20single%20day%20for%20some%20sort%20of%20solution.%20I%20thought%20(with%20public%20preview%20enabled)%2C%20that%20our%20admins%20would%20have%20the%20latest%20features%20weeks%20before%20the%20rest%20of%20the%20tenant%20-%20not%20to%20be.%20Very%20embarrassing%20for%20us%20in%20trying%20to%20explain%20this%20to%20management%20and%20users%20alike.%20How%20can%20you%20not%20roll%20out%20features%20at%20the%20tenant%20level%3F%3F%3F%20And%20while%20I'm%20here%20complaining%20about%20the%20roll-out%2C%20thank%20you%20also%20for%20f**king%20with%20the%20speed%20dial%20groups%20as%20well.%20While%20half%20my%20tenant%20is%20p*ssed%20about%20not%20having%20the%20new%20features...%20the%20other%20half%20don't%20like%20'Call%20History%2C%20missing%20overview%20of%20groups'%20and%20want%20to%20roll%20back!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20give%20up%20-%20have%20a%20nice%20weekend%20and.....%20Microsoft%20PLEASE%20FIX%20your%20horrible%20roll%20out%20system!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2502197%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2502197%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2251%22%20target%3D%22_blank%22%3E%40Martin%20Rinas%3C%2FA%3E%2C%26nbsp%3Bwhat%20is%20the%20logic%20behind%20the%20release%20process%20if%20it%20isn't%20beneficial%20to%20businesses%20IT%20offices%20if%20we%20have%20public%20preview%20and%20can't%20get%20the%20features%20in%20advance%20to%20test%20and%20prepare%20for%20training%3F%20This%20is%20the%20end%20of%20June%20and%20I%20am%20under%20the%20impression%2C%20I'm%20the%20only%20member%20of%20my%20organization%20that%20doesn't%20have%20the%20new%20calls%20tab%20features%20and%20keep%20getting%20asked%20for%20assistance%20and%20I%20can't%20assist%20as%20I%20don't%20have%20the%20new%20call%20tabs%20feature%20and%20so%20I%20look%20like%20the%20idiot.%26nbsp%3B%20Fix%20your%20release%20cycle%20or%20drop%20it!%20Highly%20disappointed%20in%20the%20way%20it%20exists%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2667535%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2667535%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F17756%22%20target%3D%22_blank%22%3E%40Jeffrey%20Allen%3C%2FA%3E.%20I%20have%20been%20in%20public%20preview%20since%20the%20beginning.%20I%20have%20set%20myself%20as%20Targetted%20Release%20user.%20But%20till%20today%20I%20do%20not%20have%20some%20preview%20features%20even%20now%20they%20have%20been%20rolling%20out%20for%20quite%20some%20time%20like%20the%20Dynamic%20View%20and%20Presenter%20Mode.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20made%20service%20request%20from%20admin%20center%20but%20they%20cannot%20help%20also%2C%20as%20they%20said%20those%20are%20inside%26nbsp%3B%20Microsoft%20matter%20that%20they%20also%20do%20not%20have%20access%20to%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wonder%20if%20there%20are%20some%20config%20file%20in%20AppData%20that%20we%20can%20modify%20to%20enable%20those%20new%20features.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20Microsoft%20can%20provide%20a%20setting%20in%20Admin%20Center%20or%20user%20level%20(of%20Public%20Previewer)%20to%20enable%20those%20new%20feature%20flag%20as%20soon%20as%20they%20are%20released.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2669422%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2669422%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F812577%22%20target%3D%22_blank%22%3E%40RikkyCitra%3C%2FA%3E%2C%26nbsp%3BI%20finally%20got%20the%20new%20calling%20experience%20this%20morning%2C%20however%2C%20I%20still%20don't%20have%20the%20dynamic%20view%20yet.%20It%20would%20be%20nice%20to%20be%20able%20to%20make%20an%20adjustment%20in%20the%20Teams%20admin%20center.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2707374%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2707374%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Martin%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20is%20a%20nice%20article%2C%20it%20is%20clear%20how%20this%20work%20but%20honestly%20it%20might%20work%20for%20Microsoft%20but%20it%20does%20not%20work%20for%20corporate%20customers.%3C%2FP%3E%3CP%3EThere%20is%20not%20accepted%20answer%20%22You%20know%2C%20read%20this%20article%20and%20then%20you%20would%20understand%20why%20you%20have%20to%20wait%22.%20Even%20if%20the%20users%20are%20%22happy%22%20to%20wait%20then%20they%20will%20logically%20ask%20%22OK%2C%20and%20how%20long%20do%20I%20have%20to%20wait%3F%20Hours%3F%20Days%3F%20Weeks%3F%22%20Telling%20them%20that%20we%20cannot%20answer%20this%20question%20because%20we%20do%20not%20know%20the%20answer%2C%20this%20will%20not%20be%20accepted.%3C%2FP%3E%3CP%3EAbsolutely%20agree%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F90197%22%20target%3D%22_blank%22%3E%40Petri%20X%3C%2FA%3E%26nbsp%3Bthat%20transparency%20is%20gone.%20How%20we%20can%20trace%20it%3F%20We%20(Company%20Teams%2FO365%20admins)%20are%20responsible%20towards%20our%20users%20(customers).%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFurthermore%2C%20how%20will%20you%20distribute%20critical%20application%20patches%3F%20These%20have%20to%20be%20pushed%20as%20soon%20as%20possible.%26nbsp%3B%3C%2FP%3E%3CP%3E(Example%20VDI%20(limited)%20user%20experience%20on%20physical%20NBs)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20said%3A%26nbsp%3B%3CEM%3EWe%20first%20ship%20the%20build%20with%20the%20feature%20flags%20turned%20off.%20We%20progressively%20roll%20out%20the%20build%20to%20users%2C%20wait%20for%20the%20build%20to%20be%20picked%20up%20and%20used%20by%20users%2C%20and%20reach%20certain%20penetration%20rates.%3C%2FEM%3E%3C%2FP%3E%3CP%3EDoes%20it%20mean%20that%20users%20will%20get%20the%20new%20patched%20version%20(build)%20within%20hours%2Fdays%2Fweeks%3F%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20we%20somehow%20distribute%20it%20with%20internal%20tools%20(SCCM%20for%20instance)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3EMichal%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2731075%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2731075%22%20slang%3D%22en-US%22%3E%3CP%3EBtw%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F17756%22%20target%3D%22_blank%22%3E%40Jeffrey%20Allen%3C%2FA%3E%26nbsp%3B%2C%20have%20you%20ever%20check%20in%20AppData%5CRoaming%5CMicrosoft%5CTeams%20there%20is%20a%20file%20named%20setting.json%3F%3C%2FP%3E%3CP%3EWhen%20I%20am%20not%20in%20Public%20Preview%2C%20the%20first%20line%20shows%20that%20I%20am%20in%20ring%20%22general%22.%20If%20I%20switch%20to%20Public%20Preview%2C%20I%20am%20in%20%22ring3_6%22.%20May%20be%20you%20can%20check%20yours%20to%20see%20which%20ring%20you%20are%20in%20when%20in%20Public%20Preview.%20The%20setting.jason%20file%20can%20be%20opened%20with%20notepad.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETill%20today%20I%20still%20don't%20understand%20why%20Public%20Preview%20doesn't%20get%20some%20preview%20features%20activated%20when%20they%20are%20released.%20Yesterday%20I%20just%20got%20Dynamic%20View%20and%20Presenter%20Mode%20activated%20along%20with%20may%20be%20the%20whole%20users%20in%20my%20organisation%2C%20while%20those%20features%20supposed%20to%20be%20available%20for%20Public%20Preview%20months%20ago%20ahead%20form%20general%20users.%20My%20guess%20that%20these%20features%20are%20tenant%20level%20features%20that%20should%20be%20activated%20for%20the%20whole%20users%20at%20once%20to%20be%20working.%20If%20so%2C%20then%20what's%20the%20point%20that%20they%20released%20them%20for%20Public%20Preview.%20I%20really%20hope%20that%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2251%22%20target%3D%22_blank%22%3E%40Martin%20Rinas%3C%2FA%3E%26nbsp%3Bcan%20give%20clear%20explanation.%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2732659%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Release%20Processes%20-%20Why%20do%20I%20not%20see%20a%20feature%20but%20my%20colleague%20does%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2732659%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F812577%22%20target%3D%22_blank%22%3E%40RikkyCitra%3C%2FA%3E%2C%26nbsp%3Bthanks%20and%20it%20does%20show%20I'm%20in%20ring3_6%20and%20still%20don't%20get%20all%20of%20the%20features%20early.%20I%20have%20presenter%20mode%20but%20not%20dynamic%20view.%20I%20finally%20got%20the%20new%20calls%20tab%20recently%20after%20almost%20all%20of%20the%20staff%20did%20and%20most%20weren't%20on%20public%20preview.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Feb 02 2021 08:19 AM
Updated by: