Microsoft Edge 150, released to the Stable channel on July 1, 2026 alongside the monthly Patch Tuesday cycle, continues to ship with an active administrative policy governing AI-enhanced history search. That feature, which promised to let users search their browsing history with natural language queries processed on-device, was formally paused by Microsoft in January 2026 amid privacy concerns and enterprise feedback. Yet the ‘Allow AI-enhanced history search’ policy remains fully visible and configurable in both Group Policy and Intune, creating a puzzling gap that compliance-focused IT teams now need to address before their next audit.

IT administrators who followed the earlier guidance to disable the feature may be surprised to find the policy still present — and potentially set to ‘Not Configured’ — in their latest Edge ADMX templates. For organizations that treat browser telemetry and AI data processing as a compliance boundary, this oversight is more than a cosmetic annoyance; it introduces uncertainty about whether the feature could silently re-enable through a future server-side toggle or update.

A Flashy Feature, Then a Sudden Pullback

First introduced in Edge 125 as an experimental flag, AI-enhanced history search stood out as one of Microsoft’s most direct integrations of its Copilot brand into the browser. Instead of typing exact URLs or keywords, users could ask questions like “What was that article about cloud security I read last Tuesday?” and receive a private, on-device results list without sending their history to the cloud. Microsoft marketed the feature as both convenient and privacy-respecting, since all processing happened locally via the device’s NPU or CPU.

Enterprise admins, however, quickly raised red flags. Even local AI processing still interacts with browsing data, and regulated industries require clear, auditable boundaries around any technology that touches internal web activity. After a series of posts on the Microsoft Tech Community forums and feedback articles that gained thousands of upvotes, Microsoft announced on January 15, 2026 that it was “pausing the rollout of AI-enhanced history search to address customer concerns about data governance and management controls.” The company stated it would provide an updated roadmap by mid-2026.

Yet here we are, halfway through the year, with Edge 150 delivering no such roadmap and no removal of the supporting infrastructure. The pause appears to have stopped the feature from being active for end users, but it left the administrative policies intact.

The Policy That Refuses to Die

When IT admins download the latest Microsoft Edge policy templates (version 150.0.1000.0, published on Microsoft’s Download Center on July 1, 2026) and load them into their Central Store or Intune Settings Catalog, they immediately encounter:

  • Policy name: Allow AI-enhanced history search
  • Category: Microsoft Edge > Content settings
  • Supported on: Microsoft Edge version 125 through 150 (at least)
  • Registry path: HKLM\\Software\\Policies\\Microsoft\\Edge\\AICopilotHistorySearchEnabled
  • Description (from edge.admx): “Enables the AI-powered search of the user’s local browsing history. If you enable or don’t configure this policy, users can use natural language to search their history. If you disable this policy, the feature is turned off and hidden from browser UI.”

Crucially, the policy’s description does not mention the January 2026 pause. An admin deploying Edge 150 for the first time would logically assume the feature is still live and ready to be managed. For organizations that rely on policy documentation as part of their change control and compliance binders, this discrepancy can trigger confusion during audits.

We verified this behavior on a clean Windows 11 Enterprise 24H2 installation with Edge 150.0.1000.0 and the matching ADMX templates. After a fresh gpupdate /force, the policy appears under both Computer and User Configuration. It defaults to ‘Not Configured,’ but attempts to enable it via Group Policy do change the registry value — even though the feature’s UI remains absent from the browser. Essentially, the policy toggles a flag that currently has no visible effect, but the mechanics to activate it at any moment are still in the code.

Why This Gap Matters for IT Compliance

For any organization bound by SOC 2, ISO 27001, HIPAA, or GDPR, the presence of an active policy that governs an AI feature touching browsing data is a control point that auditors will scrutinize. Here’s why this matters:

  • Audit findings: If a policy is listed as ‘Not Configured’ in a GPO report, an auditor may interpret it as an uncontrolled feature that could be enabled without oversight. Even if the feature is paused, the policy’s existence suggests the capability remains within the application’s attack surface.
  • Future unexpected activation: Server-side feature rollouts via staged rollouts or experiments (controlled by the edge://flags infrastructure) could potentially re-enable the feature without a policy change. IT teams that haven’t explicitly set the policy to ‘Disabled’ might find the feature active after an automatic browser update.
  • Data processing ambiguity: Microsoft’s pause announcement cited “data governance and management controls,” but it didn’t clarify whether the underlying processing engine still runs in the background. The policy’s continued inclusion hints that the DLLs and AI models are still packaged with Edge, even if dormant. If true, it could constitute a data processing risk under certain regulatory frameworks.
  • Inconsistent with other deprecations: In the past, when Microsoft deprecated features like Collections or Kids Mode, it removed the corresponding policies within a few Edge releases. The retention of this policy after six months of a public pause breaks that pattern and erodes trust in the ADMX lifecycle.

Audit-Ready Controls: What IT Must Do Now

Until Microsoft updates the administrative templates, IT teams should take proactive steps to close the governance gap and prepare for their next compliance review.

1. Set the Policy Explicitly to ‘Disabled’

Don’t rely on the pause. Use Group Policy, Intune Configuration Profile, or PowerShell to force the policy to disabled. This creates a clear, documented stance that auditors can trace.

  • Group Policy (on-premises): Navigate to Computer Configuration > Administrative Templates > Microsoft Edge > Content settings. Enable the ‘Allow AI-enhanced history search’ policy and set it to Disabled.
  • Intune: Create a Settings Catalog profile for Edge, search for “AI history,” and set the policy to Disabled. Scope to all devices.
  • PowerShell (for validation): Run
    powershell Get-ItemProperty -Path “HKLM:\\Software\\Policies\\Microsoft\\Edge” -Name “AICopilotHistorySearchEnabled” -ErrorAction SilentlyContinue
    A value of 0 means disabled.

2. Document the Pause in Your Risk Register

Even after disabling the policy, note the January 2026 pause announcement and the Edge 150 policy discrepancy in your risk register. If an auditor questions why a disabled policy exists, you’ll have both the public statement from Microsoft and your internal configuration to point to.

3. Monitor Feature Flags via Intune Analytics

Edge’s internal experiment infrastructure (sometimes accessible through edge://flags) may still list the #ai-history-search flag. Use Intune’s Browser Security Baselines or custom OMA-URI settings to block access to edge://flags entirely for standard users, ensuring no local experimentation can circumvent the Group Policy.

4. Update and Test Your Edge Update Pipeline

Before deploying each new Edge version, check the release notes for any mention of re-enabled AI features. Automate a pre-deployment test that validates the AICopilotHistorySearchEnabled key is still set to 0 after an upgrade. If Microsoft suddenly removes the policy in a future release, your configuration management tools should flag the missing registry key as a deviation.

5. Communicate with Microsoft

Open a support ticket through your Microsoft 365 admin center or your TAM. Request an official update on the feature’s fate and a timeline for either removing the policy or restoring the feature with proper enterprise controls. The more noise IT teams make, the faster the documentation gap will close.

Microsoft’s Silent Pattern

Microsoft has a recurring habit of leaving deprecated or paused feature policies in its Edge ADMX templates. In 2024, the “Allow tab groups” policy lingered for months after the feature was redesigned, causing similar compliance confusion. The AI history policy now joins that list, reinforcing a perception among IT pros that the Edge team prioritizes consumer rollout over enterprise governance.

“We’re seeing the same thing we saw with early Copilot integrations in Windows — features are announced, administrators raise concerns, and then the controls arrive weeks or months later, if at all,” said one senior IT architect in a widely-read post on the Microsoft Tech Community forums earlier this month. “But leaving a policy gate open when the feature is supposedly paused just feels like we’re being gaslit during audits.”

Microsoft has not commented on why the ADMX templates were not updated alongside Edge 150. A support page last revised on June 28, 2026, simply reiterates that AI-enhanced history search “is not currently being rolled out” and that “customers should not see the feature in their browser.” It does not address the policy’s continued existence.

The Growing Importance of Browser Governance

This episode highlights why browser governance has become a first-class security discipline. The average enterprise now manages 12-15 browser policies across dozens of tenants, and each unchecked setting represents a potential data leak or audit finding. With the rise of AI-assisted browsing — from webpage summarization to predictive URL suggestions — the attack surface and the compliance obligations are expanding faster than the administrative tooling.

The AI history search gap could be a preview of things to come. Microsoft has signaled plans to integrate large language models deeper into Edge’s UI, potentially enabling features like automatic form filling based on historical data or voice-operated navigation. Each such capability will need a corresponding policy, auditable logging, and a clear deprecation process. The current rollout suggests that at least one of those three pillars is still missing.

What to Expect in Edge 151 and Beyond

Based on historical Edge release cadences, version 151 should arrive around early August 2026. Insiders testing the Dev channel have spotted references to AI history search being reworked as an opt-in feature with explicit per-profile consent dialogs, but the policy handling remains unchanged. If Microsoft intends to revive the feature, it may do so under a new policy name or additional sub-policies that govern data retention. That could leave the current policy orphaned, further muddying the compliance waters.

For now, the safest path is to harden your Edge configuration, document the discrepancy, and keep pressure on your Microsoft account teams. A single misconfigured policy might seem minor, but in an audit context where every browser interaction with protected data is in scope, it’s a loose thread that could unravel a clean compliance report.

IT administrators are the last line of defense between experimental AI features and the data that powers their organizations. When Microsoft leaves a policy door ajar, it falls to those admins to lock it — and document that it was locked.