Edge Auto Sign in Broken / Cloud Filter

[DWilson1997]

Hi all,

 

We've recently noticed an issue during our filtering checks where Microsoft Edge is no longer automatically signing users in on first launch. As a result, our Smoothwall Cloud Filter is unable to identify the user and records their activity as "unknown-user."

 

All relevant Edge policies are configured via Intune and appear to be applying correctly on the client.

 

"BrowserSignin": 1,
"ImplicitSignInEnabled": true,
"ForceSync": true,
"NonRemovableProfileEnabled": true,
"ProactiveAuthWorkflowEnabled": true,
"HideFirstRunExperience": true

 

What we're seeing is that when a user signs into a device for the first time and opens Edge, the browser launches with "Profile 1" and displays their account ready to be signed in, but it doesn't complete the sign-in automatically. If the user closes Edge and reopens it, the browser immediately signs them in without any issues.

 

Has anyone else experienced this recently, or found a cause or fix for it?

[itskdog]

I recently tried switching BrowserSignIn to 2 (Force) rather than 1 (Enabled) to see if that would help.

[Joeloman]

Try installing Filter Backstop:
https://kb.smoothwall.com/hc/en-us/articles/25469690012956-Filter-Backstop-overview#h_01KH8H4P28M2VBFYZBSGQ8RPCV

 

It detects the logged-in user and reports this information to the Smoothwall extension in the browser.

[PeterH]

We have the same issue with Edge not signing in automatically on first launch. This happens with first login to a computer, i.e. new profile. We have our BrowserSignIn set to 2 (Force) which means users are having to manually sign in when they open the browser for the first time.

 

I spent hours chasing this trying to figure out what had broken it. It seems that the problem was introduced in Edge v153.0.4234.32. However I have tested with 4234.46 and it seems to be fixed. So perhaps try updating to the new version. 

 

[DWilson1997]

Glad it is not just us - thanks for the heads up. We are on 153.0.4234.32 so that makes sense, I'll do some testing on 153.0.4234.46

 

I'll also get filter backstop deployed if it can talk to cloud filter.

 

D

[Jake_Curran]

Can confirm updating to v153.0.4234.46 fixed this issue for us. Had to manually run the update in Edge settings though.