Client has On-Prem AD server x2 and are running 2 azure AD servers connect and syncing with Azure AD connect one way from on Prem to Azure.

Goal is to get rid of on prem ad put them in the cloud fully.

They have 28 vmware vms on vCenter 8.03 with ESXI 8.03 Dell R660 servers
Mix of Server OS from 2012 to 2025.

I ran the Azure migration assessment tool and it states that all servers are in readiness state to be migrated to Azure cloud.

I did more deep dive on this and found that I need to make sure of the process and I found this:

2 Azure-based DCs with FSMO roles and AD Connect is syncing from on-prem to Azure, I need to keep them operational until all dependent services on-premises are fully migrated. Once that’s complete, they can be decommissioned ??

Also If any of these VMs are tightly coupled with Kubernetes clusters or other infrastructure, those dependencies should be validated before migration.

My question is out of all the 28 vms how do I determine which ones

Have dependent services on-prem that need to be migrated or would prevent from being migrated?
Also which ones are using Kubernetes or other infrastructure ? What does this mean??

Any and all advise and help would be great on what you have done or are doing with this scenario

7 Spice ups

If you’re moving your on-prem AD to the cloud, what does this have to do with your vSphere? Unless you’re migrating to MS Hyper-V these should be unaffected??

1 Spice up

Well since the on-prem AD is syncing with AD connect to azure one way then on prem is still the boss as per se and cannot totally be moved to the Azure AD vms until I figure this out:

My question is out of all the 28 vms how do I determine which ones

Have dependent services on-prem that need to be migrated or would prevent from being migrated?
Also which ones are using Kubernetes or other infrastructure ? What does this mean??

1 Spice up

Just to piggy back here, on premise entra connect controls the sync from AD to azure/m365. If your referencing the azure migration appliance, are you migrating to AVS? That is the only way the migration tool and vmware come into play here.

1 Spice up

Well not there yet trying to find out best way to get this information because we may not be able to do it.

My question is out of all the 28 vms how do I determine which ones

Have dependent services on-prem that need to be migrated or would prevent from being migrated?
Also which ones are using Kubernetes or other infrastructure ? What does this mean??

1 Spice up

Which Azure Mirgation assessment did you run? The Azure Migrate appliance should be able to map dependencies to tell you which servers communicate with each other.

Also check for Windows services that run as service accounts, because those depend on AD.

2 Spice ups

Azure VM assessment is what I ran

1 Spice up

Check out the dependency analysis.

2 Spice ups

This is not what you want to hear but your scenario is best to keep on premise. Running VM with workload for long term is very expensive. Compared to VMWare it might be cheap, but look at the hypervisor competitors if vmware is your reason. If you don’t plan to to remove AD entirely and use Entra native you also should stay on premise. If you use the Azure backup and recovery you will have extreme problems in case you get ransomed. I don’t remember the details but Truesec professionals have explained the process for recovery and we talk weeks instead of hours.
And third: did I mention cost? Cloud is very good for highly volatile loads and temporary needs, but in the long run on-prem is cheaper.

2 Spice ups