 The teal says, hi, I need help cleared cash and cookies on my PC. Then I was logged out of my Microsoft Teams and Outlook. Tried logging back in. However, when I add my account, Authenticator won't generate the number that I can tap. Lots of questions on this one. Yeah, indeed. First of all, your Authenticator, unless it's on your PC, should have had not been affected whatsoever by your clearing the cash and the cookies that you have on your PC. So that's number one. Second, then I was logged out by my MS Teams and Outlook, my home and for what reason? How? Was it just a conscious thing that you decided to do? Did somebody update something somewhere and tell you to log out so that they could do something or whatever? I mean, that's less important, that's how we're written. Tried logging back in. However, when I add my account, Authenticator won't generate the number that I can tap. Well, is that the way it's working in this particular case? Because there are four different ways Authenticator will get back with you. First of all, it just says, hey, I need authentication, tap this, which you can. Second way, it'll give you a series of four or five or six different numbers. Please tap to allow the account or number or this particular authentication request with these five or six digits past tap okay to accept that. A third way, it will provide you with three different numbers up with a number on your screen and say, select this number and then the Authenticator app on your phone will provide you three or four different numbers and you pick the correct one. The latest iteration of that is that they say, on the request from your PC, please enter the following number and when you open Authenticator, you've just got a type in field and you can add whatever number happens to be there. So how did we get to this authenticator ever work in the first place? When I hear the question, I can't help but think of the times when I've got a new phone or I had to reset my phone or it was damaged and anyway, the original Authenticator account installation and the accounts associated with my installation, excuse me, on the phone are gone. So I come in with a new phone, I install the Authenticator app, I go to Teams or any other privileged access site in Microsoft 365, and it's saying I'm prompting you but I'm not seeing it on my device and I think we've all had that right and there's a linkage between those original setups of the Authenticator accounts, maybe on the original device prior to a reset or a replacement that need to be maintained. So it's good that you cleared the cache and the cookies that never hurts and that usually helps. But in this case, it sounds like the issue is not Teams or your web, but your Authenticator app assuming it's on your phone device. So question to ask yourself, did you get a new phone? If so, did you restore the accounts and when you restore the accounts, how it's not just like restore from back up, there's a bunch of other business that you have to do right back on the Authenticator screens. It depends on the Authenticator style on the site that the Authenticator is working against. For example, Facebook, GitHub, places like that, it just if you have backed it up and you restore it following directions, those just automatically come up and work for any Office account, 365 account of that sort of thing, it will come back with an error that says you need to reconnect Authenticator to this account. That's where it kind of becomes sticky because if you've got an old phone and you were very nice and you backed up your stuff firsthand, and then on your new phone, you downloaded all it's still going to need you to use the old phone or some other second factor that you may have entered in order to be able to get back into your account to reconnect that particular the Authenticator with the account that you're trying to open it with. That's where a lot of people wind up in trouble. They'll, I got me a new phone, I got rid of the old phone and you'll find that not only is the Authenticator on that phone that they've either didn't back up or did back up and are running against this error that I've mentioned or another one of their second factors happens to be the phone number of the phone that they just got rid of and they've got a new phone so it won't prompt them that way. An instance of my big thing in life is give it as many different second factors as you can. I think in this case, all he really needs to do is to get back into his account and tell it this for this Authenticator is connected to these accounts. The question of whether he has a methodology of getting back in there without his old phone, without some other second factor, an e-mail address or two or three or four, as it will take a lot of them on phone number or two, or whatever. That's on my Office 365 account, it's the N365 family account. But in that particular one, I've got like three different e-mail addresses and two phone numbers. Plus the Authenticator plus an old Authenticator, that was the thing that I did when I had to replace my phone. I had, first of all, the phone that I use is no longer being manufactured, it's an LG. So anything that I'm dealing with is old. When I bought the phone because they weren't terribly expensive, I bought a second phone thinking if I have a problem, I've got an instant backup and that has pretty well worked. I had a case with the old phone, the first of the two of these that were the battery decided to expand. While I was getting the battery replaced, I needed the second phone. Well, I had them both set up. Authenticator actually works because of the way, I'm guessing the way that they set it up. If you go back in and you could have more than one Authenticator defined on a program. Now, I've not been on occasion yet where one phone was dead, and I needed to fire up the other phone to get back in. So I don't know specifically if that works, but I can very much attest to the fact that on a 365 account, I have got two different Authenticators. I know at least in part that works because for some of the other the ones that I don't have to go back in and reset, I forget whether it was Facebook or Github or whatever. If you look at the two of them with the both phones turned on and running, they're producing the same number. Again, I've got more questions than answers on this particular question. I've never been able to re-link my Office 365 account to my Authenticator without either having the recovery information put in ahead of time or working with my IT support team to re-initialize the prompt. My advice for Teal is it sounds like not able to do it, maybe didn't have those backup authentication methods. Your only option is talk with IT and get that reset. Pray that it's not an outlook.com because you'll never get there. If it's a 2FA set up account and you lose the second FAs and can't get back in, you are dead. That account is gone. It is history. We've talked about that in past questions as well. Not to scare you Teal, but that's why I think we've made it clear is to have multiple backups, emails, other methods, other multiple factors. Henceforth, I shall be called Fuchsia.