This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 97%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJV%3C/text%3E%3C/svg%3E)
Strangest thing is happening. We assign Edge (Stabile version) to our dedicated android devices with Azure AD. Yesterday version 124.0.2478.50 (247805005) of Edge AI Browser was starting to install on our devices and we ran in to a problem instantly. The app shows a screen saying "Sign in to sync" and Add account. Normally edge should just automatically sign in to the signed in users account (SSO). Pressing the "Add account" button results in that the app is just "thinking" spinning blue circle and nothing more happens. The most strange thing is that the official version according to Google Play and Microsofts release notes is 123.0.2420.102 (242010205). And if you Google "124.0.2478.50 (247805005)" you get information about Edge BETA, which we dont have assigned to our devices. How can ver 124.0.2478.50 (247805005) be installed on our devices in the first place? Testing the exact same thing in our QA tenant, we just see ver 123.0.2420.102 (242010205)
Chapter 2
A day later we realized that Edge was updated again, and the version was back to 123.0.2420.102 and SSO was working. We quickly uninstalled Edge on all our devices and reinstalled it again, problem solved... temporary.
Chapter 3. Tonight Edge was updated again (on Google Play) to version 124.0.2478.62 and now the SSO issue is back!!!
THIS IS A VERY SERIOUS ISSUE CAUSING SEVERE ISSUES!
Clearing app cache does not help by the way Anyone experiencing this? Any ideas why?
Is anyone from Microsoft reading this?
Do you understand the severity of this matter?
Are any actions taken?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 1%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEV%3C/text%3E%3C/svg%3E)
Version 124.0.2478.87 installed on our compay devices: SSO still not working.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 25%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIG%3C/text%3E%3C/svg%3E)
Same here. 124.0.2478.87 installed but issue still not fixed.
LATEST NEWS FROM MICROSOFT:
"We have a known issue “yes”. But this is not a change on Edge that caused the issue. The change was brought in OneAuth SDK by the Authentication team and we only integrated the change into out browser which being MSEdge"
I´ll keep you updated about what the Authentication-team has to say about it
//N
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 9%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EML%3C/text%3E%3C/svg%3E)
Does anyone know if a fix is incoming? I have a fleet of 400 Android MHS kiosk phones in a health care setting and lack of SSO with Edge is a massive problem. It also causes issues with Teams, where the phones are "being prepared" and access to chat and calls seems random at best.
Edge version 124.0.2478.87, Teams version 1416/1.0.0.2024083602
V. 124.0.2478.104 Edge is available on APK Mirror, not yet in the Play Store. I don't know if it fixes anything.
Just updated to 124.0.2478.104 and SSO issue is not fixed
Updated to 124.0.2478.104 but SSO issue is still not fixed
This morning version 125.0.2535.51 installed and SSO works.
I will run more tests and share results.
Installed V.125.0.2535.51 on one of our AAD shared devices: SSO in Edge is working again. But now I have an issue with Teams: when I log off the session and login with a differend user, Teams is stil trying to login the previous user. I don't know if this is a new issue, or it's related to the SSO-problem.
I just tried doing the same (log-out session and log-in with different user) and both Edge and Teams are fine - current, active user is logged in for both.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
May I ask where you get version 125 and how you forced the installation? We have devices with MHS setup and version on the managed play store is still 124 :(
The version in the Play Store online is indeed V.124; but when I manually open the Play Store on the device and search for updates, I can see V. 125, but not on all our devices. I cannot explain why.
It was available in Google Play Store as a normal update.
If it helps, our phones are in Norway and Sweden.
Thanks, Ill try to check later today... only 124 was available this morning (Czechia). Dear Microsoft, this is really big problem and failure from your side. Premier Support team doesnt know anything about it and I spend many hours and days trying to find out, why our policies are not working. Currently only Teams is working in device shared mode with MHS... Outlook and Edge are not working, asking for account.
The update has sloooowly started to happen to my fleet of Android phones, I can confirm it fixed the SSO issue with Edge, though Teams still seems slow to connect on startup. No way to force the update from Intune, has to happen from the PlayStore side from what I can see. I rebuilt a phone after the update 1st started to appear yesterday but that phone still ended up with 124.0.2478.104 being installed instead of 125.0.2535.51 and is still on it after spending the whole night charging while idle.
v125 still not available here (Czechia) and service is still not working, did anyone get any updates from MS?
This morning, Edge was updated to 125.0.2535.72. I can confirm SSO is working fine.
Google Play shows V.124.0.2478.104 updated on May,27, but V.125 still not available on our devices (Belgium)
I do not see any 125.xx version here yet (Sweden)
We had it working in version 124.0.2478.87
But in 124.0.2478.104 it broke again!
Not really impressed about how MS is handling this :(