Microsoft Edge 152.0.4191.53

Set whether websites can access and use sensors such as motion and light sensors. You can completely block or allow websites to get access to sensors. Setting the policy to 1 lets websites access and use sensors. Setting the policy to 2 denies access to sensors. Setting the policy to 3 [removed: prompts][added: is intended to prompt] the user when a site requests access to [removed: sensors if the tri-state feature flag is enabled; otherwise, it defaults to allowing][added: sensors, but this option isn't yet supported; if you select it, websites can still] access [removed: to][added: and use] sensors. You can override this policy for specific URL patterns by using the 'SensorsAllowedForUrls' (Allow access to sensors on specific sites) and 'SensorsBlockedForUrls' (Block access to sensors on specific sites) policies. If you don't configure this policy, websites can access and use sensors, and users can change this setting. This setting is the global default for 'SensorsAllowedForUrls' and 'SensorsBlockedForUrls'. Policy options mapping: * AllowSensors (1) = Allow sites to access sensors * BlockSensors (2) = Do not allow any site to access sensors * AskSensors (3) = Ask whenever a site wants to access sensors[added: (This policy is not yet supported)] Use the preceding information when configuring this policy.

This policy controls whether Copilot in the Microsoft Edge side pane can access page [removed: content][added: content, browsing history,] and [removed: browsing history.][added: video transcript.] This includes page [removed: summarization][added: summarization, video summarization,] and other contextual queries. This policy applies only to users who are signed in to Microsoft Edge with a Microsoft Entra account and are using Copilot in the side pane. It applies to Copilot experiences in the side pane, including Microsoft 365 Copilot Business Chat and Microsoft Copilot with enterprise data protection (EDP). If you enable this policy, Copilot can access page [removed: content][added: content, browsing history,] and [removed: browsing history][added: video transcript] when users initiate contextual queries in the side pane or from Edge. If you disable this policy, Copilot can't access page [removed: content][added: content, browsing history,] or [removed: browsing history.][added: video transcript.] This also disables the M365LinksAutoOpenCopilotEnabled feature, because Copilot requires page content access to provide contextual insights for Microsoft 365 links. If you don't configure this policy: - Access is enabled by default in non-EU regions. - Access is disabled by default in EU regions. - Users can turn this setting on or off in Microsoft Edge settings. Copilot can't access page content on pages protected by data loss prevention (DLP) policies, even if this policy is enabled. For more information about Copilot data usage and consent, see https://go.microsoft.com/fwlink/?linkid=2288056

This policy lets you specify the [removed: major][added: exact 4-part] version of the WebView2 Runtime that specific applications should use in enterprise downgrade scenarios. Configure the policy by setting the value name to the Application User Model ID or the executable file name (for example, teams.exe). Set the value to the target [removed: major][added: full] version [removed: number][added: string] using [removed: digits only][added: the 4-part numeric format] (for example, [removed: 145). Full version strings ][added: 151.0.2178.0). Major-only values ](for example, [removed: 145.0.1234.56),][added: 151),] wildcard values (for example, 1[removed: 45][added: 51].*), and values that [removed: contain non-digit characters or separators][added: are not exact 4-part numeric versions] are not supported. The WebView2 loader [removed: scans][added: resolves] the runtime installation directory [removed: for an already-installed][added: only when a] folder that [added: exactly ]matches the [removed: specified major][added: configured full] version [added: exists ](for example, [removed: 145 matches 145.0.1234.56).][added: 151.0.2178.0 must match 151.0.2178.0 exactly).] If no [added: exact ]matching folder is found, the policy has no effect and the runtime defaults to the BrowserExecutableFolder policy or the Evergreen runtime (the default auto-updating runtime). Example value: Name: teams.exe, Value: [removed: 145][added: 151.0.2178.0] Name: outlook.exe, Value: [removed: 146][added: 152.0.2164.0]