Microsoft Edge: 154.0.4258.48 to 156.0.4314.42

[added: DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. This policy is deprecated. Use the 'AutofillSettings' (Block AutoFill data types for specific sites) policy instead. To keep the current behavior of disabling AutoFill for addresses, configure 'AutofillSettings' with "url_pattern" set to "*" and "blocked_types" set to ["contact_info", "identity_docs", "travel"]. ]Enables the AutoFill feature and allows users to autocomplete address information in web forms through previously stored information. If you have enabled or not configured this policy, users manage AutoFill for addresses in Microsoft Edge settings. AutoFill allows users to complete address fields in web forms using previously saved information. If you have disabled this policy, Microsoft Edge doesn't suggest, fill in, or save address information. AutoFill is also disabled for all web forms except payment and password fields, and previously saved addresses aren't available. If you disable this policy, then 'EdgeAutofillMlEnabled' (Machine learning powered autofill suggestions) is turned off. If you disable this policy, all activities for all web forms are stopped, except payment and password forms. No further entries are saved, and Microsoft Edge doesn't suggest or AutoFill any previous entries.

[added: DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. This policy is deprecated. Use the 'AutofillSettings' (Block AutoFill data types for specific sites) policy instead. To keep the current behavior of disabling AutoFill for addresses, configure 'AutofillSettings' with "url_pattern" set to "*" and "blocked_types" set to ["contact_info", "identity_docs", "travel"]. ]Enables the AutoFill feature and allows users to autocomplete address information in web forms through previously stored information. If you have enabled or not configured this policy, users manage AutoFill for addresses in Microsoft Edge settings. AutoFill allows users to complete address fields in web forms using previously saved information. If you have disabled this policy, Microsoft Edge doesn't suggest, fill in, or save address information. AutoFill is also disabled for all web forms except payment and password fields, and previously saved addresses aren't available. If you disable this policy, then 'EdgeAutofillMlEnabled' (Machine learning powered autofill suggestions) is turned off. If you disable this policy, all activities for all web forms are stopped, except payment and password forms. No further entries are saved, and Microsoft Edge doesn't suggest or AutoFill any previous entries.

[added: DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. This policy is deprecated. Use the 'AutofillSettings' (Block AutoFill data types for specific sites) policy instead. To keep the current behavior of disabling AutoFill for payment instruments, configure 'AutofillSettings' with "url_pattern" set to "*" and "blocked_types" set to ["payments"]. ]Enables Microsoft Edge's AutoFill feature and lets users auto complete payment instruments like credit or debit cards in web forms using previously stored information. Includes suggesting new payment instruments like Buy Now Pay Later (BNPL) in web forms and Express Checkout. If you enable this policy or don't configure it, users can control AutoFill for payment instruments. If you disable this policy, AutoFill never suggests, fills, or recommends new payment Instruments. Additionally, it won't save any payment instrument information that users submit while browsing the web.

[added: DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. Microsoft Edge will use OneAuth for sign-in on Windows without requiring this policy. The policy is deprecated starting in version 155 and is planned to become obsolete in version 161. No configuration change or replacement policy is needed to continue using OneAuth. ]This policy allows users to decide whether to use the OneAuth library for sign-in and token fetch in Microsoft Edge on Windows 10 RS3 and later. If you disable or don't configure this policy, sign-in process uses Windows Account Manager. Microsoft Edge would be able to use accounts you signed in to Windows, Microsoft Office, or other Microsoft applications for sign in, without the need for a password. Or, you can provide valid account and password to sign in, which are stored in Windows Account Manager for future usage. You can investigate all accounts stored in Windows Account Manager through Windows Settings -> Accounts -> Email and accounts page. If you enable this policy, OneAuth authentication flow is used for account sign in. The OneAuth authentication flow has fewer dependencies and works without Windows shell. The account you use isn't stored in the Email and accounts page. This policy only takes effect on Windows 10 RS3 and later. On Windows 10 earlier to RS3, OneAuth is used for authentication in Microsoft Edge by default.

[added: DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. This policy is deprecated. Use the 'AutofillSettings' (Block AutoFill data types for specific sites) policy instead. To keep the current behavior of disabling AutoFill for payment instruments, configure 'AutofillSettings' with "url_pattern" set to "*" and "blocked_types" set to ["payments"]. ]Enables Microsoft Edge's AutoFill feature and lets users auto complete payment instruments like credit or debit cards in web forms using previously stored information. Includes suggesting new payment instruments like Buy Now Pay Later (BNPL) in web forms and Express Checkout. If you enable this policy or don't configure it, users can control AutoFill for payment instruments. If you disable this policy, AutoFill never suggests, fills, or recommends new payment Instruments. Additionally, it won't save any payment instrument information that users submit while browsing the web.

Controls whether users can access developer tools in Microsoft Edge. [added: This policy also applies to direct Chrome DevTools Protocol (CDP) connections (for example, connections that use --remote-debugging-port or --remote-debugging-pipe) and CDP connections through the chrome.debugger extension API. The 'RemoteDebuggingAllowed' (Allow remote debugging) policy controls whether users can use remote debugging. When remote debugging is allowed, this policy still controls which targets can be inspected. ]If you set this policy to 'DeveloperToolsDisallowedForForceInstalledExtensions' (default), users can access developer tools and the JavaScript console, except in the context of extensions installed by enterprise policy. If you set this policy to 'DeveloperToolsAllowed', users can access developer tools and the JavaScript console in all contexts, including extensions installed by enterprise policy. If you set this policy to 'DeveloperToolsDisallowed', users cannot access developer tools or inspect website elements. Keyboard shortcuts, menu options, and context menu entries that open developer tools or the JavaScript console are disabled. As of version 99, this policy also controls access to the 'View page source' feature. If you set this policy to 'DeveloperToolsDisallowed', users cannot view page source through keyboard shortcuts or the context menu. To fully block source viewing, add 'view-source:*' to the 'URLBlocklist' (Block access to a list of URLs) policy. As of version 119, this policy also controls whether developer mode for Isolated Web Apps can be enabled. As of version 128, this policy does not control developer mode on the extensions page if the 'ExtensionDeveloperModeSettings' (Control the availability of developer mode on extensions page) policy is configured. [removed: Developer tools availability is determined in the following order ][added: The 'DeveloperToolsAvailabilityAllowlist' (List ]of [removed: precedence: 1. If a URL matches a pattern in 'DeveloperToolsAvailabilityAllowlist'][added: URL patterns where developer tools are allowed) and 'DeveloperToolsAvailabilityBlocklist'] (List of URL patterns for which developer tools are [removed: allowed to be opened),][added: blocked) policies take precedence over this policy. Developer tools availability is determined by the first applicable rule below: 1. If a URL matches a pattern in 'DeveloperToolsAvailabilityAllowlist',] developer tools are allowed. 2. If the allowlist is configured and the blocklist is not, URLs not on the allowlist are blocked. 3. If a URL matches a pattern in [removed: 'DeveloperToolsAvailabilityBlocklist' (List of URL patterns for which developer tools are blocked), developer tools are blocked. 4. If ][added: 'DeveloperToolsAvailabilityBlocklist', developer tools are blocked. 4. Otherwise, if neither URL-list policy is configured, or if ]a URL [removed: is not covered by either ][added: matches neither ]list, this policy ('DeveloperToolsAvailability' (Control where developer tools can be used)) [removed: applies.][added: applies as the fallback. On Android, this policy controls inspection of targets through remote debugging. It does not enable on-device developer tools.] Policy options mapping: * DeveloperToolsDisallowedForForceInstalledExtensions (0) = Block [removed: the developer tools ][added: Edge DevTools ]on extensions installed by enterprise policy, allow in other contexts * DeveloperToolsAllowed (1) = Allow using [removed: the developer tools][added: Edge DevTools] * DeveloperToolsDisallowed (2) = Don't allow using [removed: the developer tools][added: Edge DevTools] Use the preceding information when configuring this policy.

This policy controls where developer tools can be used in Microsoft Edge by specifying an allowlist of URL patterns. [added: Developer tools availability is evaluated for each target being inspected. ]URL patterns are matched against the [removed: URL of every frame on the page being inspected.][added: target's URL, such as a page, a subframe represented by a separate target, an extension, or a web application. Frames that share a target follow that target's policy result.] If you configure this policy and do[removed: no][added: n']t configure the 'DeveloperToolsAvailabilityBlocklist' (List of URL patterns for which developer tools are blocked) policy, developer tools are available only [removed: when every frame on the page matches ][added: for targets whose URLs match ]a pattern in this allowlist. If [removed: any frame does not][added: a target's URL doesn't] match, developer tools are blocked for [added: that target. For example, a subframe represented by a separate target can't be inspected if its URL isn't on ]the [removed: entire page.][added: allowlist, but an allowlisted main-page target remains inspectable.] For information [removed: on][added: about] the URL format, see https://go.microsoft.com/fwlink/?linkid=2095322[removed: ]. If you configure both this policy and the 'DeveloperToolsAvailabilityBlocklist' policy, this allowlist takes precedence. [removed: URLs that match][added: A target whose URL matches] this allowlist [removed: are][added: is] allowed even if [removed: they][added: it] also match[added: es] the blocklist. [removed: URLs that match][added: A target whose URL matches] the blocklist but not this allowlist [removed: are][added: is] blocked. [removed: URLs that match][added: A target whose URL matches] neither [removed: are][added: list is] governed by the 'DeveloperToolsAvailability' (Control where developer tools can be used) policy. If you disable or do[removed: no][added: n']t configure this policy, developer tools availability is determined by the 'DeveloperToolsAvailabilityBlocklist' and 'DeveloperToolsAvailability' policies. This policy applies to developer [removed: tools opened for websites, extensions,][added: tools, direct Chrome DevTools Protocol (CDP) connections (for example, using --remote-debugging-port or --remote-debugging-pipe),] and [removed: web applications.][added: CDP connections through the chrome.debugger extension API. The 'RemoteDebuggingAllowed' (Allow remote debugging) policy controls whether remote debugging can start. When remote debugging is allowed, this policy still restricts which targets can be inspected.] Blanket host wildcards (that is, "*" or "[*]") aren't allowed. To enable developer tools globally, use the 'DeveloperToolsAvailability' policy. This policy supports up to 1,000 entries.[added: On Android, this policy controls inspection of targets through remote debugging. It does not enable on-device developer tools.] Example value: contoso.com https://ssl.server.com contoso.com/good_path https://server.contoso.com:8080/path .exact.hostname.com file://*

If you enable this policy, users [removed: will][added: may] see a prompt to import their browsing data from [removed: other browsers on each ][added: Chrome to ]Microsoft [removed: Edge launch. ][added: Edge. ]If [removed: you disable this policy, users will never see ]a [removed: prompt to import their][added: user gives consent, supported] browsing data [added: is imported ]from [removed: other browsers ][added: Chrome ]on each Microsoft Edge launch. [removed: If the policy is left unconfigured, users can activate this feature from][added: This policy applies to profiles that aren't signed in and profiles signed in with] a Microsoft [removed: Edge prompt or from the Settings page. Note: A similar policy named 'AutoImportAtFirstRun' (Automatically][added: account (MSA). It doesn't apply to profiles signed in with a Microsoft Entra ID account. If you disable this policy, users won't be prompted to] import [removed: another browser's][added: their browsing] data [removed: and settings at first run) exists. This policy should be used if you want to import supported data ][added: from Chrome on each Microsoft Edge launch. If you don't configure this policy, users can enable this feature ]from [removed: other browsers only once while setting up your device.][added: a Microsoft Edge prompt or from Settings.]

[added: DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. Starting in Microsoft Edge version 156, this policy is deprecated as the built-in PDF reader experience has transitioned to the newer version. The policy will remain supported for a minimum of 6 major releases and is planned to become obsolete starting in Microsoft Edge version 162. Once obsolete, organizations will no longer be able to use this policy to opt out of the new PDF reader. Your organization should remove this policy before it becomes obsolete. ]The policy lets Microsoft Edge launch the new version of the built-in PDF reader that's powered by Adobe Acrobat's PDF rendering engine. The new PDF reader ensures that there's no loss of functionality and delivers an enhanced PDF experience. This experience includes richer rendering, improved performance, strong security for PDF handling, and greater accessibility. If you enable this policy, Microsoft Edge will use the new Adobe Acrobat powered built-in PDF reader to open all PDF files. If you disable or don't configure this policy, Microsoft Edge will use the existing PDF reader to open all PDF files.

[added: DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. Starting in Microsoft Edge version 156, this policy is deprecated as the built-in PDF reader experience has transitioned to the newer version. The policy will remain supported for a minimum of 6 major releases and is planned to become obsolete starting in Microsoft Edge version 162. Once obsolete, organizations will no longer be able to use this policy to opt out of the new PDF reader. Your organization should remove this policy before it becomes obsolete. ]The policy lets Microsoft Edge launch the new version of the built-in PDF reader that's powered by Adobe Acrobat's PDF rendering engine. The new PDF reader ensures that there's no loss of functionality and delivers an enhanced PDF experience. This experience includes richer rendering, improved performance, strong security for PDF handling, and greater accessibility. If you enable this policy, Microsoft Edge will use the new Adobe Acrobat powered built-in PDF reader to open all PDF files. If you disable or don't configure this policy, Microsoft Edge will use the existing PDF reader to open all PDF files.

[added: DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. Starting in Microsoft Edge WebView2 version 156, this policy is deprecated as the built-in PDF reader experience has transitioned to the newer version. The policy will remain supported for a minimum of 6 major releases and is planned to become obsolete starting in Microsoft Edge WebView2 version 162. Once obsolete, organizations will no longer be able to use this policy to opt WebView2 applications out of the new PDF reader. Your organization should remove this policy before it becomes obsolete. ]This policy configures WebView2 applications to launch the new version of the PDF reader that's powered by Adobe Acrobat's PDF reader. The new PDF reader ensures that there's no loss of functionality and delivers an enhanced PDF experience. This experience includes richer rendering, improved performance, strong security for PDF file handling, and greater accessibility. If this policy is specified for an application, it is possible that it may impact other related applications as well. The policy is applied to all WebView2s sharing the same WebView2 user data folder. These WebView2s could potentially belong to multiple applications if those applications, which are likely from the same product family, are designed to share the same user data folder. Use a name-value pair to enable the new PDF reader for the application. Set the name to the Application User Model ID or the executable file name. You can use the "*" wildcard as value name to apply to all applications. Set the Value to true to enable the new reader or set it to false to use the existing one. If you enable this policy for the specified WebView2 applications, they will use the new Adobe Acrobat powered PDF reader to open all PDF files. If you disable the policy for the specified WebView2 applications or don't configure it, they will use the existing PDF reader to open all PDF files. Example value: {"name": "app1.exe", "value": true} {"name": "app_id_for_app2", "value": true} {"name": "*", "value": false}