![]() ![]() Security and quality updates ship as needed. If you find an issue, it can be remediated before the release is published to the Stable Channel. This channel provides a great opportunity to validate that things work as expected in your environment. It's a supported release, and each release from Beta is serviced until the next release is available. The Beta Channel is intended for production deployment to a representative sample set of users. A release from the Stable Channel is serviced until the next release from the channel is available. It's the most stable of the channels and is the result of the stabilization of the feature set available in the prior Beta Channel release. The Stable Channel is intended for broad deployment in your organization, and it's the channel that most users should be on. To help you make this decision, review the following information about the four update channels that are available for Microsoft Edge. For example, the number of line-of-business applications in use will affect your testing requirements every time there's a Microsoft Edge update. The update channel you decide to deploy depends on several factors. Representative validation in the organization ![]() Channel overview ChannelĪn enterprise release option for Stable aligned to a longer release cycle This article applies to Microsoft Edge version 77 or later. Here's an overview of the four options.įor more information on support for each channel, read: Microsoft Edge Lifecycle Microsoft provides four options, called channels, to control how often Microsoft Edge is updated with new features. However, as the admin who deploys Microsoft Edge to users in your organization, you might want more control over how often your users get these new features. One of the benefits of the next version of Microsoft Edge is that Microsoft can provide new features regularly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |