 So Douglas says, we have about 150 users that are currently in our tenant using AD sync. We have another 50 users that are Azure AD native. We want to migrate the 150 users off of local AD sync to Azure AD native without losing their user names. Users are heavy users of one drive, and so this needs to be migrated alongside. What is the best method? What is the best method? Well, I mean, it's really, it's a native process, right? It's really something that's built in to the product itself, the sync product. So it's just something that you do as part of that, and I think I provided a link there. Let me check here. Yes, you did. Okay. It seems to have gone away for me, but it's even worse there. I can see it, and that's all that's important. Yeah. That's all that's important. It's definitely there. Exactly. Okay. Yeah, it really is. It's all part of a native process to do that. So it's not something that they have to take a lot, spend a lot of time in or go to a third party. Although I think there are some third parties that could actually help you out there. And Christian, you might know more about that. But there is native functionality built in. Yeah. I mean, that's the migration has been, it's a commoditized area. This is kind of an easy process if you have that third party tool. I'm not sure on the native as far as migrating over the changes of those user IDs, natively, what happens with the OneDrive? Yeah. So that's just it. It's a delta cleanup, right? So it's getting those final changes after you are migrating. 150 users isn't that big of a deal. To be honest with you, it's not. I mean, in the whole scheme of things, I mean doing 150,000 or even 15,000, that's way different. That's way different. Yeah, that's the territory where I'd say if you definitely want to look at a third party tool when you're looking at, so if somebody has a similar scenario, but with 1,500 instead of 150 users, then I agree that heavier lifting and there are likely going to be other assets besides just the AD changes and OneDrive. It's probably be messier. Who would have thought that we get to this point in the game and we're still doing migrations, huh? Yeah, there was a lot of conversation about that like six to eight years ago that even further back than that, that migrations were going away. Has everybody been in the cloud and then there's just an update? It's like, no, and that's why there were a small group of us that were, they said, let's stop calling it migration and just call it moving because moving content will happen. Like, I don't know if you reorg if you're absolutely required acquisitions, right? Consolidate organizations, yeah. Consolidate cloud applications. There's data all over the place. People will go continually go and create new instances and then want to merge things over. I mean, all that shadow IT is not going away. You can minimize it, but there'll always be reasons to consolidate and move profiles and data. When you go back to those six years like you talked about, Christian, actually a lot of folks just wanted to get to the cloud and what they did was they synced their AD. Okay, so that was the first thing they did and they were like, hey, let's try moving some mailboxes and either it worked or it didn't work. And if it didn't work, they're like, ah, we'll come back to this later. And that later became two years, three years, four years. Now some companies that I've talked to are just like, hey, yeah, we've already been syncing our AD for like four years, but we've never really done anything. And now we want to move mailboxes, you know? And I'm like, wow, you've been paying for all that for four years just to sync user accounts that you're really not using. Ha, ha, ha, ha. Redundancy never hurts. Yeah, yeah, until it does.