 Simon says, I just wanted to say that Simon says, I have a Microsoft account where an old admin has synced the local AD. How can I delete old on-premises accounts that are not synced anymore because the install of Azure AD Connect changed? So I'll start Neil. This is really a confusing question. The reason why I say that is because the on-premises accounts, the Azure Connect reads the on-premises accounts. It's not like it just randomly cannot sync. It's going to sync everything that's in the on-premises. That's its job. Now, there are configuration changes that you can do inside of AD Connect that will only sync certain objects and certain containers inside of Active Directory on-premises Active Directory. It is possible that if there's a specialized configuration going on there that's not allowing some of those to sync, but it's somewhat a confusion because all it's doing is it being like a gateway. It's just saying what's here replicated here. If you tell me only pull it from this container, this container, or this object, this object, and this container and replicate it to here, then that's all I'm going to do. AD Connect is really dumb that way. So that's what I would say is we need to take a look at how AD Connect is configured, if any configuration changes were made there, and if there was a skip or a hiccup, if you will, with the synchronization, AD is going to pick that up. It's just something that's going to be synchronized across. I mean, that's what AD does. Unless they've got bigger problems with their AD, I don't know that. Neil, if you have anything to add? Yeah, I read it the same way, and I've one of the things that I'm kind of distilled the whole thing down to a simple scenario of, it looks like this is what I'm reading. An old admin basically installed AD Connect and just when synchronize everything, the whole Active Directory from on-prem into Azure AD. They've since modified it using the filters process, the scripting PowerShell piece to filter down on maybe like you say, specific or use or various properties of the accounts. But all of those user accounts and groups that were synchronized to AD, Azure AD originally are still there, but now they're refining them down. So I think the question might be, how do I clean up my Azure AD? I think there might be an element of that to the question as well. I can't remember if it's on my head whether AD Connect will automatically clean up. I don't think it does. I think those accounts are just going to be. It's a switch. It's a switch. Yeah, it's a switch and AD Connect, they have that cleanup happen. So that's one thing they should look at as well. But I understand where you're coming from, reading into that question like that. But at the same time, I questioned how the old admins sync everything, and then you have all these other objects that are sitting there. I'm seeing what I'm reading from is that is there something actually wrong with the sync itself? Because the sync should pick that up. I mean, that's just and you should start seeing those accounts getting deleted. If they were moved over here, you should start seeing getting removed over there. That's my opinion. Yeah, if they've been removed, or are they just old accounts that are still sat there but no longer used or just by the definition of old on-premises accounts, is it? I'm trying to read the context. Is it old as in we no longer need them to be synced but they still exist in Azure AD? But like you say, it's kind of confusing. There's a number of ways just to kind of skin that cat, I guess in terms of which way is it? Well, all options are possible, but yeah, investigate the configuration of AD Connect. Is there a problem? AD Connect does log, so you can determine that. And then the two scenarios of, is it a conflict change and it's not picking up the deletions or is it the fact that you want to remove old accounts? Kind of falls into the same bucket really.