The Microsoft account login server has detected too many repeated authentication attempts. Please wait a moment and try again. HOW LONG IS THAT MOMENT?

THIS IS THE PROBLEM!
I reported that I had turned off allow all cookies, since I had so many website in the list that had cookies set who I had not even gone to. Thinking of security which MS should understand and NOT have this as the recommended setting, I turned it OFF and used the white list. I have added all the microsoft sites to the white list BUT that was when I then could NOT log onto MS rewards. BUT I can on opera GX browser. Thats how I knew it was what I had done with the Edge browser cookie settings. WHY when I have turned off the crappy default setting that allows any website to add cookies but added all ms sites to the white list does this happen? MS sites should be able to recognize that they are in the white list.

Blondi SL wrote:

As a Microsoft Certified technician (happily retired now, I might add) I'm not one to go and just do mass cookie deletion. I work around that by trying to find "related" cookies.

However, in this case, even that wasn't necessary.

All I had to do was get to a point where I could do a forced log off from this Microsoft Account, and once I did that, re-logged on and satisfied authentication, all is fine again. Deleting cookies is way too often the suggestion by people when in fact, while that often works, isn't always necessary.

I've been a certified tech (Microsoft, HP, IBM, Lenovo) for decades and I've learned some tricks here and there.

I was caught off guard with THIS particular situation, because with that flash error, it didn't even suggest to people to log off and re-log on. People who don't expect this might not be sure why it's happening and in fact, that message is rather misleading.

If this is due, as I think you suggest, to a "new cookie", the message is poorly composed and doesn't give any indication as to the fix.

If anything, with that message, perhaps Microsoft should send people an email, right then, giving them a link to log off and letting them log in again, fully, with the authentication token being required.

Oh well. it is what it is and I got it working without cookie deletion.

And the posts to which I send people

* * Edit on 4/23/2024. Brought to this thread by a search?

Please see the Post by Ray Lazarus on Page 6 and the post by TheRealMystic on Page 4.

don't recommend clearing all Cookies. I agree that "clear all Cookies" is recommended too often and I might not have ever cleared all Cookies.

Don

Suji Lakshminarayanan wrote:

Same issue - started this A.M (12/19/2024) - seems like MSFT has not addressed this!

Please see my post, 2nd post above yours on this page.

Don

Same issue - started this A.M (12/19/2024) - seems like MSFT has not addressed this!

Hi Don:

As a Microsoft Certified technician (happily retired now, I might add) I'm not one to go and just do mass cookie deletion. I work around that by trying to find "related" cookies.

However, in this case, even that wasn't necessary.

All I had to do was get to a point where I could do a forced log off from this Microsoft Account, and once I did that, re-logged on and satisfied authentication, all is fine again. Deleting cookies is way too often the suggestion by people when in fact, while that often works, isn't always necessary.

I've been a certified tech (Microsoft, HP, IBM, Lenovo) for decades and I've learned some tricks here and there.

I was caught off guard with THIS particular situation, because with that flash error, it didn't even suggest to people to log off and re-log on. People who don't expect this might not be sure why it's happening and in fact, that message is rather misleading.

If this is due, as I think you suggest, to a "new cookie", the message is poorly composed and doesn't give any indication as to the fix.

If anything, with that message, perhaps Microsoft should send people an email, right then, giving them a link to log off and letting them log in again, fully, with the authentication token being required.

Oh well. it is what it is and I got it working without cookie deletion.