Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Identity for hosted servers: extend your domain, build a new one, or use Entra ID

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

For Windows servers moved to a hosting provider, there are three main identity designs: extend your existing Active Directory domain with a domain controller at the host, build a separate domain for the hosted servers, or rely on Microsoft Entra services. Extending fits when applications need Windows sign-in (Kerberos), group policy or directory lookups (LDAP) and staff should keep one password. Before choosing, list which applications depend on those services, because that list narrows the options.

Why it matters

Identity touches every sign-in, file permission and application connection. Choosing the wrong model can mean two passwords for every staff member, applications that cannot authenticate, or servers that stop working when the office link drops. Changing the design later costs more than choosing carefully at the start.

How it works

Extend the existing domain

A domain controller is placed at the hosting provider, connected to the office over a private link or VPN, and replicates with the existing domain controllers. Hosted servers join the same domain. Users keep one account; group policy and permissions carry over.

Microsoft's planning guidance asks you to "plan where you want to place domain controllers, including forest root domain controllers, regional domain controllers, operations master role holders, and global catalog servers". With a domain controller at the host, hosted servers can keep authenticating if the office link is down.

One domain controller at the host is itself a single point of failure for sign-in to the hosted servers. In our view, as engineers rather than as a sourced rule, a second domain controller at the host, or at least a documented and tested way to recover the first, should be considered; the right answer depends on how long the business can go without hosted sign-in. Our published article Domain Controllers on VMware: Snapshots and Restores covers why domain controllers need particular care when they are restored.

Build a separate domain

A new domain for the hosted servers keeps them independent of the office directory. It can suit a software vendor hosting clients, or an isolated environment. The cost is separate accounts for users, or a trust between domains to be designed and maintained.

Use Microsoft Entra services

Microsoft describes Entra Domain Services as providing "managed domain services such as domain join, group policy, lightweight directory access protocol (LDAP), and Kerberos/NTLM authentication" without deploying domain controllers yourself. It also states that "Two Windows Server domain controllers are deployed into your selected Azure region as part of a replica set."

Microsoft positions it narrowly. The same page says it can be used "as a transitional capability for Azure-hosted workloads that require legacy authentication, rather than as a general replacement for your on-premises Active Directory", and that a managed domain "is a stand‑alone domain and isn’t an extension of an on‑premises domain", although forest trusts can be configured. So it is a separate domain, not a way of extending your office domain, and the page does not describe using it for servers at another hosting provider. Servers outside Azure would at least need network connectivity to that Azure region; ask Microsoft or your Azure partner whether that design is supported before planning on it.

Separately, Microsoft documents signing in to Windows Server virtual machines in Azure with Entra ID. Its documentation warns: "your Azure virtual machine will be Microsoft Entra joined. You can't join them to another domain, like on-premises Active Directory or Microsoft Entra Domain Services." That feature is described for Azure virtual machines; check whether any Entra sign-in option applies to servers at another host before planning on it.

What to choose and why

A decision table

If… Consider Depends on
Applications need Kerberos, LDAP or group policy, and staff should keep one account Extend the existing domain Reliable private link; domain controller backup and patching at the host; a second domain controller or tested recovery
Hosted servers serve a separate group or clients Separate domain Separate accounts or a designed trust
Workloads run in Azure, need legacy domain authentication, and a separate managed domain is acceptable Entra Domain Services Azure subscription; a separate domain, not an extension of yours; for servers at another host, confirm support first
No application needs domain services Lighter options, after checking each application Application vendor confirmation

The table is editorial guidance and simplifies real designs.

Record application dependencies first

For each application, record how users sign in, whether it uses Windows authentication to its database, and whether it reads users or groups from the directory. Also note file shares that rely on domain group permissions, printers deployed by group policy, and scheduled tasks or services running under domain accounts; these are easy to miss and stop working if the design changes. Ask vendors where unsure. This list decides more than any general preference.

Protect the domain controller

A domain controller at the host holds the keys to the business. Agree who patches and backs it up, restrict who can sign in to it, and include it in restore tests.

Illustrative example

A 40-person firm moves its accounting and document servers to a host. Both applications use Windows authentication, and staff sign in to office PCs with domain accounts. The firm extends its domain with a domain controller at the host over a private link. When the office internet fails one morning, staff working from home still reach the hosted servers, because their remote access does not run through the office. The example is illustrative.

Risks and limits

  • Links matter. An extended domain depends on a stable private connection for replication.
  • Separate domains add friction. Two accounts per person invite password reuse.
  • Cloud features change. Entra capabilities and their limits are updated; verify before designing.
  • Migrations need sequencing. Identity changes during a move need their own plan; our published article Planning identity, DNS and application cutovers for hosted services covers the order. Our companion article on bringing customer staff identities into a hosted application covers the software-vendor case.

Sources

Opened 15 November 2026; all three Microsoft pages and the published articles reopened 16 November 2026.

Related articles: Domain Controllers on VMware: Snapshots and Restores; "The Trust Relationship Failed" After a Member Server Restore; Planning identity, DNS and application cutovers for hosted services.

Related service: VPC networking.

Learning notes

  • Three main designs: extend the domain, build a separate one, or use Entra services.
  • List which applications need Kerberos, LDAP or group policy before choosing.
  • Entra Domain Services runs its domain controllers in an Azure region, as a separate domain aimed at Azure-hosted workloads, not an extension of yours.
  • Entra-joined Azure Windows VMs cannot also join another domain.
  • A hosted domain controller needs patching, backup and restricted sign-in; consider a second one or tested recovery.