A quiet roadmap update confirms that Microsoft plans to unify tracking prevention settings across all Edge browsing sessions, stripping away a long-standing option that let private windows enforce stricter anti-tracking rules than normal tabs. The change, scheduled for general availability in August 2026, means InPrivate will no longer operate as a de facto hardened zone for users who wanted Strict protection only when they weren’t being tracked by their own browser history.

The Setting That’s Going Away

Edge’s tracking prevention engine has shipped with three tiers since its debut: Basic, Balanced, and Strict. The middle ground—Balanced—blocks trackers from sites you haven’t visited while still allowing enough cross-site functionality to keep most websites from breaking. Strict blocks more trackers and storage accesses but occasionally breaks sites. For years, Edge has also included a checkbox buried in its privacy settings: “Always use Strict tracking prevention when browsing InPrivate.” Flip it on, and every time you opened an InPrivate window, the browser would silently upgrade to Strict, even if your regular windows stayed on Balanced.

Roadmap item 530578, published to the Microsoft 365 Roadmap on July 31, 2026, declares that setting obsolete. After the update, InPrivate windows will mirror whatever tracking prevention level the user has chosen globally. If you’re on Balanced, InPrivate gets Balanced. If you’re on Strict, both modes get Strict. No separation. No silent upgrade.

The description Microsoft provides is spare, labeling it a “unified experience.” It’s not a new privacy layer or a downgrade in protection, but a removal of a distinct, if obscure, control.

What This Actually Looks Like for You

For Home Users Who Rarely Touch Settings

If you’ve never dug into Edge’s privacy menus, you’re almost certainly running Balanced tracking prevention—the default. InPrivate windows on your machine already behave identically to regular windows because you likely never turned on the separate Strict toggle. For you, nothing changes. InPrivate will continue to discard your browsing history, cookies, and site data when you close all private windows. What it won’t do is apply a hidden layer of tracker blocking that your regular tabs don’t have. But again, you never had that unless you manually switched it on.

For Power Users Who Relied on the InPrivate Strict Exception

If you deliberately enabled “Always use Strict tracking prevention when browsing InPrivate,” this is where the road forks. You’ll need to make a conscious choice: either bump your whole browser to Strict, knowing that some sites might break, or accept that InPrivate will no longer be the place where you get stricter tracker blocking while regular windows stay on Balanced for compatibility.

This matters because the real-world difference between Balanced and Strict is tangible. Strict prevention can block more third-party cookies, storage access, and resource loads that are used for fingerprinting or cross-site tracking. But that same aggressiveness can break single sign-on flows, embedded comments widgets, or payment forms. Many users adopted the split approach specifically to avoid those frustrations in everyday browsing while tightening the screws when they opened an InPrivate window to research something sensitive, check a flight price without being profiled, or log into a secondary account.

For IT Administrators and Managed Environments

There’s no Group Policy or MDM setting specifically for “force strict tracking prevention in InPrivate only.” Administrators who want to control tracking prevention across their fleet already use the broader policies that set Balanced or Strict for all sessions. This change doesn’t alter those policies, but it does remove a variable: employees who might have toggled the checkbox locally will now find its effect gone. For organizations that forbid Strict across the board due to compatibility concerns, this is a net positive—it eliminates a stealthier state where some private windows could break in unexpected ways.

IT should note that tracking prevention is not a security control. Microsoft’s own documentation clearly states that InPrivate mode does not hide your activity from employers, schools, ISPs, or the sites you visit. The retirement of this setting doesn’t weaken protection against malware, phishing, or network monitoring. It’s a privacy feature, not a security one.

How We Got Here

Edge’s tracking prevention system launched in late 2019, built into the Chromium-based browser from the start. The Balanced mode was modeled on Mozilla’s Enhanced Tracking Protection, attempting to block known trackers while maintaining site functionality. Strict mode was added as an option for users willing to trade compatibility for more thorough blocking.

The InPrivate-specific toggle arrived later, documented on Microsoft Learn as a way to “use Strict tracking prevention when you browse InPrivate, which might provide stronger protection against websites tracking your browsing activity.” It was never on by default; the default behavior for InPrivate was always to inherit the global setting. But for those who found the checkbox, it became a clever workaround: browse normally with fewer interruptions, switch to private mode when you needed the extra shield.

The 2026 roadmap entry is part of a larger trend within Edge to simplify its settings surface. Over the past two years, Microsoft has consolidated several privacy toggles, streamlined cookie controls, and aligned Edge more closely with Chromium defaults. Removing an exceptional path that only a fraction of users leveraged fits that pattern.

If you peek at the number on the roadmap (530578) and the August 2026 timeframe, you’ll also notice that Microsoft announced it late in the game—just a few days before the feature entered development. That’s not unusual for minor behavioral changes, but it underscores that this isn’t a headline-grabbing release. It’s a quiet cleanup.

What to Do Now

You have roughly a year before the update rolls out worldwide. No immediate action is required, but if you’ve been depending on the InPrivate Strict exception, you’ll want to settle on a permanent posture sooner rather than later.

Step 1: Check your current settings.
Open Edge, visit edge://settings/privacy, and look at the Tracking prevention section. Note whether you’re on Basic, Balanced, or Strict. Then scroll down and see if “Always use Strict tracking prevention when browsing InPrivate” is checked. If the checkbox isn’t there, you’re on the default path and can stop reading.

Step 2: Decide on a consistent tracking prevention level.
If that checkbox is checked, ask yourself: do you value compatibility or tracker blocking more? Test Strict in your standard browsing for a few days. Pay attention to sites that break—things like login buttons that don’t respond, comments that don’t load, or videos that won’t play. If the breakage is too much, stick with Balanced. You can always disable tracking prevention entirely by switching to Basic, but that removes almost all protections.

Step 3: Stack alternative protections for private sessions.
Even after the change, you can still harden InPrivate windows using other means. Edge allows you to block all third-party cookies (a separate switch in edge://settings/content/cookies). You can restrict which extensions run in InPrivate—by default, extensions are disabled unless you explicitly allow them. Review those permissions at edge://extensions and click “Details” on each extension to toggle “Allow in InPrivate.” If you want strong isolation, disable everything and enable only an ad/tracker blocker you trust. Extensions like uBlock Origin can apply their own filtering rules that are entirely independent of Edge’s built-in tracking prevention.

Step 4: Watch for the rollout.
When August 2026 arrives, the change will likely appear as part of a routine Edge update. Microsoft hasn’t specified a toggle-off option, so once installed, the legacy checkbox will vanish and the unified behavior will take effect. If you’re using Edge in an enterprise environment, you may get advance notice via Microsoft 365 Message Center or release notes.

Step 5: Re-evaluate your privacy workflow.
Remember that tracking prevention is only one piece of the puzzle. InPrivate mode still deletes local traces, but it doesn’t anonymize your traffic. Consider pairing it with a VPN or DNS-level filtering if you need stronger network privacy. For managing logins across multiple accounts, Edge’s multiple profile feature is often more practical than InPrivate windows, because profiles can isolate cookies and site data permanently without requiring a fresh private session each time.

What Comes Next

This cleanup likely previews a broader effort to make Edge’s privacy controls more approachable. Microsoft has been gradually aligning its browser’s defaults with Chromium’s, and the Chromium project itself continues to iterate on tracking protection (think of the Privacy Sandbox and Topics API). Edge’s tracking prevention may eventually fold more directly into Chromium’s native mechanisms, reducing the need for a separate menu entirely.

For now, the takeaway is straightforward: InPrivate will be a little less special, but the underlying privacy protections remain. The decision simply moves from a hidden checkbox to your conscious choice of a browser-wide setting. If that choice feels more honest—an explicit tradeoff rather than a silent split—then August 2026 might leave your browsing a fraction simpler and no less private.