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

Hello Martin

It is a nice article, it is clear how this work but honestly it might work for Microsoft but it does not work for corporate customers.

There is not accepted answer "You know, read this article and then you would understand why you have to wait". Even if the users are "happy" to wait then they will logically ask "OK, and how long do I have to wait? Hours? Days? Weeks?" Telling them that we cannot answer this question because we do not know the answer, this will not be accepted.

Absolutely agree with Petri-X that transparency is gone. How we can trace it? We (Company Teams/O365 admins) are responsible towards our users (customers).  

Furthermore, how will you distribute critical application patches? These have to be pushed as soon as possible. 

(Example VDI (limited) user experience on physical NBs)

You said: 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.

Does it mean that users will get the new patched version (build) within hours/days/weeks? 

Could we somehow distribute it with internal tools (SCCM for instance)?

Thank you  
Michal