Share via

InPrivate Browsing/Android - Cannot launch into link if Edge is not running beforehand

Anthony Willett 0 Reputation points
2026-03-10T15:53:47.2133333+00:00

I'm having issues with launching Edge with a link if Edge was not run beforehand. We have a series of devices in a Mobicontrol managed environment where we launch Edge from a lockdown screen. Edge is installed with an App Configuration that puts the application into an InPrivate view, as these devices are expected to pass between users accessing confidential information. The links in the lockdown are correctly configured, but only work if Edge is currently running; attempting to use a link when Edge isn't running causes Edge to launch with a new tab instead. Pressing the system back button immediately after closes Edge and creates a cycle where none of the links work as expected. If a user navigates forward one link or uses the system home button, Edge remains resident and all the lockdown links work as expected.

Our current workaround is to launch Edge, then immediately return to the lockdown via a script. We've embedded this into the 'logout' button we've created to close Edge (and clear out all data from the InPrivate session). I want to know if there's another way to have the links work correctly without this workaround, or maybe an intent I could send to launch Edge in the background as starting it directly does create a noticeable flicker.

Microsoft Edge | Open the browser | Android
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-10T15:54:01.8066667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    This behavior is by design for Microsoft Edge on Android when using InPrivate and Intune-style data‑protection configurations. When Edge is cold‑started by an external link, it first brings up its configured default/start experience (for example, a new tab in InPrivate) rather than directly navigating to the incoming URL. The context does not document any supported way to:

    • Force Edge for Android to open a deep link correctly on first launch when it is configured to always start in InPrivate, or
    • Launch Edge “in the background” via a special intent so that the next external link will reliably reuse that running instance.

    The documented mobile controls focus on:

    • Data‑protection transitions (for example, blocked corporate sites → personal profile or InPrivate) using:
      • com.microsoft.intune.mam.managedbrowser.AllowTransitionOnBlock
      • com.microsoft.intune.mam.managedbrowser.openInPrivateIfBlocked
      • com.microsoft.intune.mam.managedbrowser.AutoTransitionModeOnBlock
    • General restrictions such as disabling “New InPrivate tab” and locking the UI via EdgeLockedViewModeEnabled and related app‑config/MDM policies.

    None of these policies or configurations change the initial cold‑start navigation behavior or provide a supported “silent pre‑launch” mechanism. The current workaround of starting Edge once (even briefly) so that subsequent lockdown links work as expected is consistent with what is possible using the documented configuration surface.

    Based on the available documentation, there is no supported alternative intent or policy that would:

    • Start Edge invisibly in the background, or
    • Guarantee that the first launch from a lockdown link opens that URL directly in InPrivate without the initial new‑tab behavior.

    Any further change would require a product enhancement request through Microsoft support or the Edge/Intune feedback channels.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.