How to Enable or Disable “Share Microsoft Edge Browsing Data with Other Windows Features” in Windows 11

This guide will teach you how to enable or disable Share Microsoft Edge browsing data with other Windows features setting in Windows 11. Microsoft Edge includes a feature that lets your browsing data be shared with other Windows components, such as Windows Search and the Start menu search box. When this integration is enabled, Windows can index your Edge history, favorites, top sites, and recent tabs so they appear as results alongside apps, files, and settings.

This can make it much easier for users to jump back into recent work or frequently visited sites directly from the taskbar or Start menu. At the same time, organizations may choose to disable this sharing to reduce where sensitive browsing activity can surface, enforce privacy and compliance rules, or keep browser data strictly inside Edge.

How the setting works

Under the hood, this behavior is controlled by the LocalBrowserDataShareEnabled policy, which controls whether Edge publishes local browsing data to the Windows indexer. When the feature is on, Edge connects your profile’s local browsing data with Windows so that Windows Search and other features can find and launch previously visited sites. If you turn the feature off, Edge removes the data already shared with Windows on that device and stops sharing any new browsing data from that profile.

This integration is local to the user’s device and is separate from cloud-based features (such as Edge sync). Disabling sharing does not disable syncing to your Microsoft account, and turning off sync does not automatically stop Windows from indexing local history if sharing remains enabled. That distinction matters for admins who want to tightly control how and where browsing data appears without necessarily changing how it is backed up or roams between devices.

Prerequisites

To manage “Share Microsoft Edge browsing data with other Windows features,” you will need a Windows 11 device with Microsoft Edge installed and kept current. If you plan to configure the feature via registry or Group Policy, your account must have local administrator rights on the machine. In enterprise environments, make sure you have imported the latest Microsoft Edge ADMX and ADML templates so the LocalBrowserDataShareEnabled policy and related options are available in the Group Policy Editor. Having those pieces in place ensures that policy changes are recognized correctly and that your configurations will be consistent across devices.

Use Edge settings

For single-user systems or quick adjustments, the easiest way to control this feature is directly from the Edge UI. This lets users decide whether they want their browsing activity integrated into Windows experiences, as long as no higher-level policy has locked it down.

To enable or disable sharing through Edge settings:

1. Open Microsoft Edge.
2. Select Settings and more (three dots), then choose Settings.
3. Go to Profiles, and look for Share browsing data with other Windows features.
4. Toggle this setting on to let Edge connect local browsing data from your profile with Windows.
5. Toggle it off to stop sharing and remove previously shared data from Windows on that device.

After changing the toggle, close all Edge windows and reopen the browser so the integration state fully refreshes. If your device is managed by an organization and a policy is enforcing this setting, you may find that the toggle is greyed out with messaging that your browser is managed; in that case, you will need an admin to change the policy rather than the in-browser setting.

Manage data sharing via Registry Editor

When you need stronger, system-wide control and want to bypass the per-profile UI, Registry Editor gives you a direct way to configure the LocalBrowserDataShareEnabled policy. This approach is useful for standalone systems, lab machines, or when you want to test policy behavior before rolling it out via Group Policy or MDM.

To manage the setting using Registry Editor:

1. Press Win + R, type regedit, and press Enter.
2. Navigate to:
3. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge
4. If the Edge key does not exist, create it under Microsoft.
5. Create or modify a DWORD (32-bit) value named LocalBrowserDataShareEnabled.
6. Set the value to 1 to enable sharing and allow Windows to index local Edge browsing data.
7. Set the value to 0 to disable sharing, remove data already shared, and prevent new data from being sent.
8. Close Registry Editor and restart Microsoft Edge.

Values under HKLM\SOFTWARE\Policies behave as mandatory policies for Edge, so they override user choice and typically lock the corresponding toggles in the UI. By writing LocalBrowserDataShareEnabled here, you ensure that every profile on the device follows the same integration policy, which is important in environments where different users or profiles might otherwise configure inconsistent settings.

Enable or disable data sharing with Group Policy

For most enterprises, Group Policy is the preferred way to manage whether Windows can access Edge browsing data across many machines. The LocalBrowserDataShareEnabled policy can be set as either a mandatory or recommended setting, giving you flexibility in how strictly you enforce it.

To configure this via Group Policy:

1. Ensure the latest Microsoft Edge ADMX/ADML files are installed in your Group Policy central store or local PolicyDefinitions folder.
2. Open the Local Group Policy Editor on a workstation (gpedit.msc) or the Group Policy Management Console on a domain controller.
3. Navigate to:
4. Computer Configuration > Administrative Templates > Microsoft Edge.
5. Find the policy named Enable Windows to search local Microsoft Edge browsing data, which maps to LocalBrowserDataShareEnabled.
6. Set the policy to Enabled if you want Windows to index local Edge browsing data.
7. Set the policy to Disabled if you want to stop sharing and remove data already shared from that device.
8. Leave the policy Not Configured to allow Edge’s default behavior or user choice via the UI.
9. Run gpupdate /force on a client device to accelerate policy application.
10. In Edge, browse to edge://policy to confirm that LocalBrowserDataShareEnabled appears with the intended value.

Group Policy lets you scope settings to specific organizational units, security groups, or device types, so you can, for example, allow sharing on personal productivity devices while disabling it on high-security workstations. When configured as a mandatory policy under Computer Configuration, it ensures that all users and profiles on the affected machines adhere to the same integration rules.

Automate configuration with PowerShell

PowerShell is well suited to automating this configuration across large fleets or integrating it into provisioning scripts and RMM workflows. Because it writes the same registry values used by Group Policy, it works smoothly alongside other management approaches and keeps your configuration consistent.

In a PowerShell session running as administrator, you can:

1. Set LocalBrowserDataShareEnabled to 1 under HKLM:\SOFTWARE\Policies\Microsoft\Edge to enable sharing.
2. Set the same value to 0 to disable sharing and remove data from Windows on that device.
3. Run Stop-Process -Name msedge -Force to close Edge so it reads updated policies on the next launch.

These commands can be wrapped in reusable scripts that your RMM or MDM platform deploys to managed devices, either during onboarding or as part of periodic remediation. That way, if a machine falls out of the desired state — because a policy was removed or the registry changed — your automation restores the correct value without manual effort.

Verify Windows integration behavior

Once you have configured the setting, you should verify that Windows behaves consistently with your chosen policy. The most practical test is to use Windows Search or the Start menu to look for sites you recently visited in Edge.

A simple validation flow:

1. With sharing enabled, browse to several distinct sites in Edge, then close the tabs.
2. Open the Start menu or Windows Search and type keywords from those sites’ URLs or page titles.
3. If integration is working, you should see results that reference your recent Edge activity, such as website shortcuts or history entries.
4. Disable sharing via Edge settings or policy, restart Edge, and wait a short period for indexing to update.
5. Repeat the search and confirm that new browsing activity is no longer appearing as results sourced from Edge.

On managed machines, use edge://policy to confirm the effective LocalBrowserDataShareEnabled value and verify whether it is coming from a mandatory or recommended policy path.

If search behavior lags behind your changes, you may need to clear Edge browsing data, sign out and back in, or rebuild the Windows Search index to flush stale entries.

Additional considerations

Before you standardize on enabling or disabling this feature across your environment, there are a few additional factors to weigh. Some Windows experiences that use browsing data may require you to be signed in with a Microsoft account or work account to unlock their full capabilities, even though the indexing itself is local. If you turn off sharing, Edge removes previously shared data from Windows on that device, but your browsing history remains in the browser unless you separately manage or clear it.

It is also crucial to treat sync and local sharing as separate levers: sync controls whether data leaves the device for cloud storage and cross-device use, while LocalBrowserDataShareEnabled controls how the local copy of that data is exposed inside Windows. Depending on your risk model, you may want to disable one, the other, or both. Additionally, some security baselines, MDM profiles, or application control products can further restrict what Windows can index or surface, which may result in more restrictive behavior than this single policy would produce by itself.

In environments with multiple Edge profiles — such as users juggling separate work and personal profiles — remember that the policy can be applied per profile or per device. When you configure LocalBrowserDataShareEnabled as a mandatory policy in HKLM or via Computer Configuration GPO, you effectively impose the same decision across all profiles on that device, which is often desirable for compliance.

Troubleshooting

If you run into issues where the feature does not behave as expected, there are several likely causes to examine.

A common complaint is that the Edge toggle for sharing browsing data is greyed out; this almost always indicates that LocalBrowserDataShareEnabled is being enforced via HKLM\SOFTWARE\Policies or Group Policy, so start by checking the registry and edge://policy for an active policy.

Another scenario is that Windows Search continues to show browsing-based results even after you disable sharing. In that case, clear Edge browsing data, close the browser, and allow some time for the Windows Search indexer to drop previously cached entries; rebuilding the search index under Settings > Search > Searching Windows can also help if stale data persists. If a registry value fails to apply, double-check that you are using the correct path, name, and REG_DWORD type, and confirm that no higher-priority Group Policy is setting a conflicting value.

Inconsistent behavior between profiles is often a sign that some profiles are governed by policy while others are left to user choice, or that some profiles are signed in with accounts that have different sync or policy scopes. Standardizing on a device-level mandatory configuration usually resolves those discrepancies. If search results are unreliable regardless of your Edge configuration, rebuilding the Windows Search index and ensuring that the search service itself is healthy should be part of your troubleshooting checklist.

NinjaOne integration

For organizations using NinjaOne, this setting is a natural fit for automated browser and OS hardening. NinjaOne can deploy registry changes that set LocalBrowserDataShareEnabled to 0 or 1 across all managed Windows 11 devices, ensuring a consistent approach to how Edge browsing data is exposed to Windows features.

By wrapping the PowerShell and registry methods into reusable components, you can apply them during onboarding, standardize them across policy groups, and remediate any drift discovered by scheduled audits.

Because NinjaOne also provides reporting and inventory capabilities, you can track which devices currently allow Windows to index Edge browsing data and which do not, then compare that state against your compliance or security baselines. Over time, embedding this configuration into your standard templates means new systems are deployed with the correct integration setting from day one, rather than relying on individual admins or users to remember to toggle it.

Conclusion

Controlling whether Microsoft Edge shares browsing data with other Windows features is a small switch with significant implications for privacy and user experience. When sharing is enabled, Windows becomes a unified place to rediscover sites you have visited in Edge, which can streamline workflows for many users. When it is disabled, your history and related data stay inside the browser, reducing how widely that information is exposed on the device and helping organizations meet stricter privacy and compliance obligations.

In summary

You are not limited to a single configuration method: Edge settings work for local, user-driven decisions; the registry and Group Policy provide strong enforcement; and PowerShell plus RMM tools let you automate the entire process. Whatever path you choose, always verify the effective policy using edge://policy and real-world search tests so you know exactly how Windows and Edge are interacting on each device you manage.