 Dunia says, hi guys. Is anyone working on Azure AD to Azure AD synchronization? Is it possible in any way, Tenant 01, Microsoft 365, hosted Azure AD, Tenant 2 apps, services, and virtual machines? Is there any way we are able to sync both Azure AD to avoid unnecessary user creation? Intention is to provide seamless access to Tenant 02 resources. Yeah. So basically what they're trying to do is they're trying to sync to Azure Active Vectories. That would be the question, yes. Yeah. That's plain and simple. But the only way to really do that is you have to go back to an on-premise AD to do that. So currently with Azure AD Connect, that's the only way you can do that. So Azure AD Connect can sync to multiple online tenants. So you can have a single AD presence on-prem that can sync to one, two, three, four, 10 different online tenants. So you would make all of your users standard inside of that AD on-prem and sync it to both Tenant 01 and Tenant 02, which would basically sync those together. Now, that's not to say that you could not actually script a function to duplicate those users between a Tenant 01 and a Tenant 02, which is entirely possible. The only thing I'd be cautious of if you did that using Azure CLI would be that you, for any reason, it falls out of sync. We all know when Active Directory falls out of sync, bad things can happen. So I would rather rely on a tool that's actually, its primary reason for living is to sync Active Directory to do that job for you. Yeah, because there are a number of replication, third-party replication tools that do that, that have different aspects. I mean, I know that there's backup, so you can do like AD backup and again, but then you have the synchronization issues, even if it's a small amount of time. So having that replication, recognize changes and whatever trigger can do it automatically or that it runs every hour or several times a day however it is, but there are a lot of options for that. I agree, I don't understand why Microsoft natively hasn't come up with a way to sync from one tenant to another, without even touching on-prem. To me, that makes sense, but maybe there's a technical reason for that. Maybe there's a reason why that synchronization can't happen, I don't know. Maybe you just like to take food out of the mouths of ISVs, Mike. Yeah. This could be, that could be. It's an opportunity for a product to use. It is, it is. It's subject matter in this question that I'm not very familiar with and as Mike is answering the question, I'm wondering what would an expected use case be for synchronizing that single on-premise AD to multiple tenants? If a good example of that would be test dev. So there's a reason you want it as a separate tenant or to isolate your test dev, completely isolate, say your developers wanted a completely different environment. Because number one, maybe they want to replicate the exact same virtual networks, which you can't do inside of a single tenant, things like that. That's a good example. Interesting. Thank you.