Controlled Feature Roll-outs in Microsoft Edge

Feature Rollout
Hello Edge Insiders! We have so many cool new features in the works for you, and we’d like to share with you the process behind how these new features will become available.
To honor our commitment to building a great browser, we test our feature changes for any regressions by gradually rolling out the feature to a small randomly selected subset of Canary & Dev channel, and then increase this subset as we are more confident about the feature. These controlled feature rollouts begin after completing standard quality, reliability, and compliance tests and determining that the feature is at ship quality. As we progressively ramp up the percentage of users, we are validating that each new feature aligns with our promise to be a safe, fast, and delightful browser in a scientific manner.
But I’m an Insider, so I must be getting these updates first?
Every time we run a controlled feature rollout, we will randomly select a percentage of the Canary and Dev channels to get the treatment, and an equally sized group to remain in the control group. A set of guardrail metrics, including performance, reliability, browser usage, and feedback reports, are measured for each group. Statistical tests to compare the metrics between treatment and control allow us to estimate the impact of each individual change. This also requires that we not tamper with the audience selection to the degree that it would influence behaviors or participation. As a result, we will generally announce new features available in dev at the conclusion of the controlled feature rollout.
What if I really can’t wait?
If a feature has not yet been enabled by default for you, and you’d like to try it out, you can enable it on edge://flags and the new feature will be applied the next time you launch your browser.

edge://flags

Thanks for being an Insider!
Exposing some of you to new features as the final stage of validation not only ensures the feature works better when you all get it; but safeguards later channels as well. Your input (both explicit and aggregated from browser telemetry) is helping us build a better browser.
Continue calling out what’s working, what’s not, what you like, and what could be better. In some cases, you might be ‘one of the few’ seeing a new experience. In those cases, your usage and feedback become even more critical. It helps us decide whether a feature should be enabled or not.