Entra ID Join vs On-Prem AD on a Windows VPS: Choosing the Identity Model

A Windows VPS that hosts user-facing applications or a handful of remote workers needs an identity model, and there are only three realistic options: cloud-only Entra ID join, hybrid Entra join with an on-premises domain still present, or running Active Directory Domain Services yourself inside the VM. The choice changes licensing, how policy reaches the machine, and what happens when DNS breaks.

The Three Models in One Paragraph Each

Cloud-only Entra join registers the machine directly with the tenant. No domain controller exists; policy arrives through Intune or a device management equivalent, and sign-in uses Entra credentials with Windows Hello for Business or a software token. It is the simplest to run on a VPS because there is nothing to replicate and nothing to restore.

Hybrid Entra join keeps the machine domain joined to AD DS and also registers it in Entra ID. GPO from the local domain still applies, Conditional Access and Sign-in logs come from the cloud. The cost is a working line of sight to a domain controller at every logon, plus replication and password hash sync.

Running AD DS on a VPS is the traditional model: one or two VMs host the domain, all servers join it, and policy, DNS and time all funnel through those controllers. It gives full GPO control and works offline, but it makes the VPS itself a single point of failure for every authentication decision in the estate.

What Each Model Costs per User

ModelIdentity licenceDevice managementNotes
Cloud-only Entra joinEntra ID P1 or Business PremiumIntune included in M365 E3/Business PremiumNo server CALs required.
Hybrid Entra joinEntra ID P1 + AD DS CALsIntune for device config; GPO for the restTwo stacks to patch.
AD DS in a VPSServer CALs per user/deviceGPO only, SCCM if addedDC VMs must be licensed separately.

For a team of ten, cloud-only is usually the cheapest because Business Premium bundles Entra P1, Intune, and Defender for Business in one per-seat price. AD DS looks free on paper but pulls in CALs, a second DC for resilience, and the admin time to maintain it.

GPO vs Intune: Which Controls You Actually Get

Intune covers most of what small teams use GPO for – security baselines, Defender settings, firewall profiles, BitLocker, certificate deployment, and Win32 app distribution – but a few categories still require a GPO path or a custom CSP. Administrative Templates in Intune are delivered as ADMX-backed configuration profiles and lag the Windows build slightly.

  • Covered well in Intune: Defender ASR, BitLocker, firewall, Windows Update rings, local admin management.
  • Partial: drive maps (use a script or Intune Remediation), printer deployment, logon scripts.
  • GPO still simpler: complex Group Policy Preferences, third-party ADMX with no cloud CSP.
  • Not available in either without extra licensing: legacy LDAP-bound applications.

If your line-of-business application talks to LDAP on port 389, cloud-only Entra join cannot serve it. Entra Domain Services offers an LDAP endpoint, but it is a separate paid service with its own schema limitations, and pointing a VPS workload at it is a different decision from joining the VPS itself.

DNS Dependencies and What Breaks First

Every identity model has a DNS dependency, and they fail differently. Cloud-only depends on public DNS resolving login.microsoftonline.com and the Intune endpoints listed in the Microsoft 365 network connectivity test. Hybrid join depends on the VPS resolving the domain name to a domain controller before any user logon.

In the hybrid case, if you point the NIC at the DC for DNS and the DC is unreachable, cached credentials allow one interactive logon and then everything stops. Set a secondary DNS server to the ISP resolver only if you accept that domain lookups will fail over to public DNS and break the locator record – _ldap._tcp.dc._msdcs. – in ways that look like random GPO failures.

Risks of Hosting the DC Itself on the VPS

A domain controller in a VPS is the highest-value target on the network and the hardest thing to restore. A restored DC that is behind the tombstone lifetime (180 days by default) reintroduces deleted objects and breaks replication with any surviving peer. There is no way to bring back an object that has passed the lifetime without an authoritative restore.

  • Every DC pause longer than the USN rollback window risks a broken replication topology.
  • A snapshot restore of a DC is unsupported unless it is an application-consistent hypervisor-native restore with the VM generation ID advanced.
  • DNS on a DC should never point at a public resolver, or zone transfers and SRV records leak.
  • Back up System State weekly and test an authoritative restore annually.

If AD DS is genuinely required, run two DCs on separate hosts and never restore one from a snapshot without checking repadmin /showrepl and the Dsa Not Writable registry value afterwards.

Choosing, by Team Size and Workload

A single VPS running IIS with no directory-bound application has no reason to run AD DS. Join it to Entra ID, manage it with Intune, and you have removed an entire class of failure from the deployment.

SituationRecommended modelWhy
1-3 servers, cloud apps onlyCloud-only Entra joinNo DC to patch, no CALs, Intune covers policy.
LDAP-bound line-of-business appHybrid join or AD DS in a VPSThe app needs a directory it can query.
Regulated, air-gapped requirementAD DS in a VPSOffline authentication and full GPO.
Remote desktop hostsHybrid joinGPO for RDS policy plus Entra for conditional access.

Documenting the Logon Dependency Chain

Whichever model you pick, decide where the DNS record for the VPS lives and document the logon dependency chain – user, device, DNS, identity provider – on one page. That page is what you read at 2 a.m. when nobody can sign in.

Migration Notes if You Switch

Converting an Entra-joined host to hybrid requires unjoining, domain joining, and re-registering without losing the Intune device record. Prepare with dsregcmd /status and confirm both AzureAdJoined and DomainJoined report YES before removing the old registration.

Going the other way, from domain joined to cloud-only, is simpler on a VPS because the host is usually disposable: build a fresh image with the target model, migrate workloads, and decommission the domain-joined host. For infrastructure context, see the Windows VPS platform overview and our published privacy policy if you are confirming the tenant and data-residency terms before a migration.

Leave a Comment