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(259.20000000000005, 69%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
Hi all!
We're having problems with our SSO into Edge only. The accounts login without issue to the other applications, but when trying to login to Edge for the first time, we're greeted with:
This error will only pop up on the first sign in, but after an hour, the account is shown as logged in and doesn't come up with the error again. We only have one account that has come up with that error on the same browser that has been previously signed into that continuously comes up with that error. Only Edge is affected. Even waiting overnight to ensure the account was left alone resulted in no resolution
The error at first login affects all accounts under our domain but only for edge, which makes me think it's an SSO setting somewhere that I've missed but I'm not certain.
If anyone has any insight or experience with this error I'd love to hear back!
May I know which sovereign cloud are you using? Additionally, you may provide a screenshot of edge://signin-internals/ for further troubleshooting. Please blur your private information as well.
We're not part of any sovereign cloud which is the bit that strikes me as odd. We've never configured that (to my knowledge). This is what the sign-in brought up:
Hope that's helpful!
Thanks for the screenshot, but everything's OK for Edge in the screenshot, except from the first-time login attempt failure, which we all know about. Let's go deeper into the details:
Hey @ShiJieLi-MSFT
I've grabbed a screenshot from a browser that has this issue at the moment:
When I'm talking about first sign in, I specifically mean for that pc profile. So if I create a new profile on this PC, or someone logs in for the first time into a PC, this error occurs. After an hour, the account seemingly signs itself in which is really weird.
I hope that helps a bit more? If there's more information I can provide just let me know!
To my knowledge we haven't made any changes within AAD before this started
All browsers experiencing this issue are up to date:
As for the other channels, I apologise but I'm not sure what you mean by them. I'm still learning a lot about this eco system beyond the surface level that I usually troubleshoot. Going off the names and a quick google, do you mean like different releases? I will have to organise for more testing to be done on that side if this is what you mean?
Yes, I meant Edge Insider channels, just like different releases but with higher versions. If there's a test machine available, it's worth testing.
But unfortunately, even though now I know the definition of "first sign in", the edge://signin-internals still does not give clear error messages. May I have a check on your Edge Group Policies? You can attach a screenshot of edge://policy.
Hey @
Here's what comes up:
Interestingly after doing some further testing with the test machine, we found the issue doesn't occur after login into a machine with an account that isn't sitting within our OU. So we're now thinking that the error is coming up because of something OU related on our side, but I've passed that onto the network team here locally to investigate because that goes well outside of my understanding.
All accounts that experience this issue are signed into business owned machines that are added to our OU. The error appears when connected to, and not connected to our network. I created a test account on the machine that we were using for testing the builds. This account was added locally and kept isolated from the OU. While signing into regular edge for the first time, no error occurred.
So it would appear we have somewhat of a smoking gun, we just need to find out exactly what it is that's causing the error and why it's making our accounts on first login pick up as a Sovereign Cloud linked account.
Hey @ShiJieLi-MSFT
Here's what comes up:
Interestingly after doing some further testing with the test machine, we found the issue doesn't occur after login into a machine with an account that isn't sitting within our OU. So we're now thinking that the error is coming up because of something OU related on our side, but I've passed that onto the network team here locally to investigate because that goes well outside of my understanding.
All accounts that experience this issue are signed into business owned machines that are added to our OU. The error appears when connected to, and not connected to our network. I created a test account on the machine that we were using for testing the builds. This account was added locally and kept isolated from the OU. While signing into regular edge for the first time, no error occurred.
So it would appear we have somewhat of a smoking gun, we just need to find out exactly what it is that's causing the error and why it's making our accounts on first login pick up as a Sovereign Cloud linked account.
So, when you use a test account (not added to your OU) to sign into a machine (added to your OU), the issue does not occur, right? As far as I'm concerned, at least these group policies will not cause this issue, so we can really focus on some account settings within your OU.
It looks like the account within your OU fails to carry the "token" to prove whether it belongs to a sovereign cloud or not, but after an hour for some reasons, the token is delivered to Microsoft Edge. For example, Roaming User Profiles will download a copy of local profile to the computer on creation, so there could be a one-hour delay. Since this issue occurs on every new profile creation, it is a good idea to consider that.
Anyway, this is just my assumption and I may not provide more information beyond Microsoft Edge. If you need more troubleshooting suggestions or log analysis for your OU settings, you may reach out to Support for Business. If there's more that I can help with, please let me know.
![](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(102.4, 44%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESJ%3C/text%3E%3C/svg%3E)
Since the release of Edge 124, we're having the same issue with SSO logins. Login and sync are not working. In addition, non-on-prem websites resolve but will not open (ERR_TIMED_OUT). Another browser will work. We can downgrade to Edge 122 or 123 and no longer have the issue. Any help appreciated.
![](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(35.2, 50%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
Same problem here, on our VDI environment. New windows 10 installation with all updates and still the same problem.
Hi all!
Apologies it has been a hot minute and we've still got the same problem, it more or less died down to the point where it got made into a background problem, but with an intake of new staff and refresh of machines we're back where we started. I've attached the screenshot as requested.
The error itself used to clear after an hour of no attempted logins when it would sign the user in automatically but it's no longer doing that. Further to this, we've found with our InTune PCs that we're rolling out, the issue is not at all present and the user is always signed into edge through the login process.
Hopefully won't have to let this go dormant again.
Thanks!
![](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(211.20000000000002, 74%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGS%3C/text%3E%3C/svg%3E)
Hi @Daniel McTackett , I've just had this happen and the problem was fixed by restarting the computer after repairing and resetting the Edge.
This issue could be related to a change in Edge 124 and later. Perform the following fix in Edge:
If this restores Edge, you can set it using Intune or GPO by enabling "Enable post-quantum key agreement for TLS" policy. Give it a try.
More discussion here: https://learn.microsoft.com/en-us/answers/questions/1659085/edge-124-will-not-open-external-sites-and-will-not