Microsoft Edge Release Notes

Release notes

• Configuration update for MIP Enforcement. Starting in Microsoft Edge 142, new configuration step introduced to maintain MIP protections via Microsoft Edge management service. Existing settings remain active until admins choose to update. For more information, see Protect Office documents with Microsoft Purview Information Protection labeling.

• SmartScreen and Scareware blocker. In organizations where both Scareware blocker and SmartScreen are enabled, users will now have the option to send signals to SmartScreen. The new setting “Share detected scam sites with Microsoft Defender SmartScreen” is available under edge://settings/privacy/security. If enabled, Scareware blocker reports its verdict to Microsoft Defender SmartScreen to enhance protection. Admins can control availability to this feature using the ScarewareBlockerSendDetectedSitesToSmartScreenEnabled policy.

• New Scareware blocker policies. Introducing two new policies for admins to configure Scareware blocker. The first, ScarewareBlockerAllowListDomains, configures a list of trusted domains for Microsoft Edge Scareware blocker. When a website's source URL matches any domain in this list, Microsoft Edge Scareware blocker doesn't analyze that site. The second, ScarewareBlockerBlocksDetectedSitesEnabled, blocks sites that are detected as potential tech scams. For both of these new policies, they'll only take effect if the ScarewareBlockerProtectionEnabled policy is enabled.

• Drag to group tabs. Tab groupings can be made by dragging a tab over another. This feature can now be controlled by the "Drag to group tabs" toggle in Microsoft Edge Settings edge://settings/appearance/tabs.

• Open external links in another profile when recommended by external applications. When Microsoft Edge is set as the default browser to open external links from applications, Microsoft Edge must determine which profile to open the links. Users can control which profile to use through the “Default profile for external links” setting. Applications such as Microsoft Teams or Outlook can also recommend a profile for the links. Currently, the user setting is prioritized over application recommendations. With this feature, the application recommended profile is given priority, instead of the profile selected in the setting. Admins can control the availability of the feature using the EdgeOpenExternalLinksWithAppSpecifiedProfile policy.

• Improved Autofill experience in Microsoft Edge. When users fill in an Address on a form, they'll be prompted to choose whether to save it for future Autofill suggestions. This enhancement ensures Autofill data is saved intentionally by users and reduces unwanted entries as part of their Autofill suggestion. Note: This is a controlled feature rollout. If you don't see this feature, check back as we continue our rollout.

• Changes to IE mode in Microsoft Edge. The entry points to reload a site manually in IE mode have been removed from consumer devices by default. This includes the option to reload in IE mode in the hamburger/ellipsis menu (a.k.a. AppMenu). Also, users will no longer see the option to add the toolbar button, and the toolbar button for IE mode will be removed. This change has completed with the release of Microsoft Edge 142 Stable.

This change doesn't impact enterprise customers when their devices are configured via group policy InternetExplorerIntegrationLevel. For more information, see Securing the Future: Changes to Internet Explorer Mode in Microsoft Edge.

A Refreshed Profile Flyout Experience for Better Clarity and Actionability

The Microsoft Edge profile flyout is updated to deliver a cleaner, more intuitive experience. The refreshed design makes it easier to distinguish between work and personal profiles, manage credentials, and quickly access key settings—all within a polished interface that supports modern browsing needs. With streamlined sign-in, clearer profile types, and organization branding preserved, this update enables a more efficient and trustworthy experience for customers. Note: This is a controlled feature rollout. If you don't see this feature, check back as we continue our rollout.

• Discover, collect, and protect data shared to Generative AI apps in Microsoft Edge with Microsoft Purview. Microsoft Edge for Business now supports inline enforcement of Purview DLP policies for unmanaged Generative AI applications. When a policy is configured in Purview to monitor or block interactions with unmanaged GenAI apps, Edge automatically applies the required settings to enforce those protections in the browser. This capability helps prevent sensitive data from being shared in prompts to AI services. Learn more on how to get started here.

• With this update, automatic activation of Microsoft Purview DLP inline protections for unmanaged GenAI apps in Edge for Business takes only one click. Learn more here. Administrators can create Purview policies to collect and analyze text prompts submitted to unmanaged GenAI apps in Edge to surface sensitive data exposure risks. Administrators can also block prompt submissions for users with elevated insider risk, enforcing adaptive protection directly in the browser.

Auto-Open feature rollout rollback

• Important update regarding the rollout of the Auto-Open feature. We’ve identified an issue with the initial implementation of the Auto-Open feature—it didn’t fully respect user preferences, and some settings weren’t honored as intended.

• To address this, the changes are being rolled back in phases during the next month to ensure all user preferences are correctly honored. As a result, users may temporarily notice a return to previous behavior where the sidepane opens even if the sidebar visibility is set to Off.

• Here are a few ways to manage the auto-open experience:

  • Manually Turn Off Auto-Open Pane: Users can manually disable the Auto-Open experience by navigating to the settings page if they prefer not to see the sidepane open for Outlook and Teams links.

  • Automatic Engagement-Based Logic: If a user doesn't engage with the Auto-Open experience and quickly closes it three times in a row, the feature is automatically turned off.

  • Turn off Auto-Open Pane using admin policies: Admins can control the Auto-Open experience by using either of these policies.

    • HubsSidebarEnabled: Set as "False" to turn off
    • ExtensionSettings: Set the sidebar_auto_open_blocked flag as "True" to turn off

Announcements

• Important update regarding the rollout of the Auto-Open feature. We’ve identified an issue with the initial implementation of the Auto-Open feature—it didn’t fully respect user preferences, and some settings weren’t honored as intended.
  To address this, the changes are being rolled back in phases during the next month to ensure all user preferences are correctly honored. As a result, users may temporarily notice a return to previous behavior where the sidepane opens even if the sidebar visibility is set to Off.
  Here are a few ways to manage the auto-open experience:
  • Manually Turn Off Auto-Open Pane: Users can manually disable the Auto-Open experience by navigating to the settings page if they prefer not to see the sidepane open for Outlook and Teams links.
  • Automatic Engagement-Based Logic: If a user doesn't engage with the Auto-Open experience and quickly closes it three times in a row, the feature is automatically turned off.
  • Turn off Auto-Open Pane using admin policies: Admins can control the Auto-Open experience by using either of these policies.
    1. HubsSidebarEnabled: Set as "False" to turn off
    2. ExtensionSettings: Set the sidebar_auto_open_blocked flag as "True" to turn off

Fixes

• Fixed an issue in headless mode which caused features like Print to PDF and Screenshot to not work as expected.

Feature updates

• Configuration update for MIP Enforcement. Starting in Microsoft Edge 142, new configuration step introduced to maintain MIP protections via Microsoft Edge management service. Existing settings remain active until admins choose to update. For more information, see Protect Office documents with Microsoft Purview Information Protection labeling.
• SmartScreen and Scareware blocker. In organizations where both Scareware blocker and SmartScreen are enabled, users will now have the option to send signals to SmartScreen. The new setting “Share detected scam sites with Microsoft Defender SmartScreen” is available under edge://settings/privacy/security. If enabled, Scareware blocker will report its verdict to Microsoft Defender SmartScreen to enhance protection. Admins can control availability to this feature using the ScarewareBlockerSendDetectedSitesToSmartScreenEnabled policy.
• New Scareware blocker policies. Introducing two new policies for admins to configure Scareware blocker. The first, ScarewareBlockerAllowListDomains, configures a list of trusted domains for Microsoft Edge Scareware blocker. When a website's source URL matches any domain in this list, Microsoft Edge Scareware blocker doesn't analyze that site. The second, ScarewareBlockerBlocksDetectedSitesEnabled, blocks sites that are detected as potential tech scams. For both of these new policies, they will only take effect if the ScarewareBlockerProtectionEnabled policy is enabled.
• Drag to group tabs. Tab groupings can be made by dragging a tab over another. This feature can now be controlled by the "Drag to group tabs" toggle in Microsoft Edge Settings edge://settings/appearance/tabs.
• Open external links in another profile when recommended by external applications. When Microsoft Edge is set as the default browser to open external links from applications, Microsoft Edge must determine which profile to open the links. Users can control which profile to use through the “Default profile for external links” setting. Applications such as Microsoft Teams or Outlook can also recommend a profile for the links. Currently, the user setting is prioritized over application recommendations. With this feature, the application recommended profile is given priority, instead of the profile selected in the setting. Admins can control the availability of the feature using the EdgeOpenExternalLinksWithAppSpecifiedProfile policy.
• Improved Autofill experience in Microsoft Edge. When users fill in an Address on a form, they will be prompted to choose whether to save it for future Autofill suggestions. This enhancement ensures Autofill data is saved intentionally by users and reduces unwanted entries as part of their Autofill suggestion. Note: This is a controlled feature rollout. If you don't see this feature, check back as we continue our rollout.
• Changes to IE mode in Microsoft Edge. The entry points to reload a site manually in IE mode have been removed from consumer devices by default. This includes the option to reload in IE mode in the hamburger/ellipsis menu (a.k.a. AppMenu). Also, users will no longer see the option to add the toolbar button, and the toolbar button for IE mode will be removed. This change has completed with the release of Microsoft Edge 142 Stable.
  This change does not impact enterprise customers when their devices are configured via group policy InternetExplorerIntegrationLevel. For more information, see Securing the Future: Changes to Internet Explorer Mode in Microsoft Edge.

Fixed various bugs, feature update and performance issues.
Stable channel security updates are listed here.

Feature Updates

• A Refreshed Profile Flyout Experience for Better Clarity and Actionability. The Microsoft Edge profile flyout is updated to deliver a cleaner, more intuitive experience. The refreshed design makes it easier to distinguish between work and personal profiles, manage credentials, and quickly access key settings—all within a polished interface that supports modern browsing needs. With streamlined sign-in, clearer profile types, and organization branding preserved, this update enables a more efficient and trustworthy experience for customers. Note: This is a controlled feature rollout. If you don't see this feature, check back as we continue our rollout.

Improved reliability

• Fixed an issue which caused Microsoft Loop and Planner workflows to crash when accessibility APIs were enabled.
• Fixed a browser crash that occurred when the BrowsingDataLifetime policy was enabled.