Managing WebView2 applications
WebView2 is a component that developers use to build their applications, and the developers may deploy a self-updating Evergreen WebView2 Runtime on user device to power their applications. This document discusses how IT admins may manage WebView2 applications and Runtime. Feedback from both IT admins and developers is welcome on WebView2 Feedback repo.
Group policies for WebView2
IT admins may use group policy objects (GPO) to configure policy settings for WebView2. The following set of policies are/are not applicable to WebView2,
- Microsoft Edge - Update policies are available for IT admins to manage the install and update aspects of the WebView2 Runtime. The Microsoft Edge browser and WebView2 Runtime are updated using the same update mechanism. Unless a policy, such as
Update, is channel-specific, it applies to both the browser and WebView2 Runtime. For example,
UpdateSuppressedallows IT admins to set time during each day to suppress auto-update for both the browser and WebView2 Runtime. This enables IT admins to configure preferences and proxies once for both the browser and WebView2 Runtime to control their network bandwidth/traffic or for other purposes. IT admins may follow Microsoft Edge's guide to configure Microsoft Edge - Update policies.
- (Coming soon) WebView2-specific policies – WebView2 will expose a small additional set of group policies in cases where managing WebView2 directly makes sense. We recommend app developers to implement their own group policies to manage their use of WebView2, as it is more straightforward for IT admins to manage the app rather than WebView2 directly.