Forum Discussion

Modechristo_13's avatar
Modechristo_13
Copper Contributor
Oct 08, 2026

Microsoft Edge plans to retire its legacy direct-WAM - version 157

Hello,

 

I’m not sure if you are already aware of the above.

 

Do you know of any way I could create a detection mechanism in Intune for the recommendation below?

 

Thank you

 

Action recommended for administrators:

 

Check edge://signin-internals under Edge Auth Library Information → Library to see if any managed profiles still show WAM.

 

Organizations wishing to validate early or test profiles that previously disabled the transition can test with --enable-features=msForceOneAuthWAM.

 

Report any sign-in issues to Microsoft Support prior to the Microsoft Edge 157 release.

intune

2 Replies

  • WinEndpointOps's avatar
    WinEndpointOps
    Copper Contributor
    Oct 11, 2026

    That check lives in a browser page, so I don't know of a built-in Intune signal for it. Two ways to get close:

    • Policy-based: WAM behaviour is driven by Edge policy and feature flags, so detect the settings that opt a device out of the transition (Edge policies under HKLM\SOFTWARE\Policies\Microsoft\Edge, plus any --disable-features entries in launch shortcuts) with a Remediation detection script and report the result per device.
    • Pilot first: put a small ring on the Edge Beta channel with --enable-features=msForceOneAuthWAM and watch for sign-in failures before 157 reaches everyone.

    I haven't found an officially documented registry value that reports the WAM state itself, so I'd confirm the exact policy names against the Edge policy documentation for 157 before building the script.