Problem getting a *.local server to connect to Azure Domain

Hello Rudd van Deventer,

Thanks for sharing the logs.

From the trace, the issue is occurring before Azure provisioning starts. The Provisioning Agent is unable to discover or connect to your on‑premises Active Directory forest. The logs repeatedly show errors such as “The specified domain does not exist or cannot be contacted” and “Unable to establish a connection to the current local computer’s forest”, even when different domain formats are used (e.g., DOMAIN\user, DOMAIN.local\user).

https://learn.microsoft.com/en-us/entra/identity/hybrid/cloud-sync/how-to-install

This typically indicates a local AD connectivity problem on the server where the agent is installed, most commonly caused by:

• The agent server not being domain‑joined, or
• DNS not pointing to the AD DNS/domain controllers, or
• Missing connectivity to required AD services (forest discovery relies on DNS, Kerberos, RPC, etc., not just LDAP port 389).

Please verify that the agent server is *domain‑joined to the .local domain, uses only AD DNS servers, and can successfully locate a domain controller (for example, nltest /dsgetdc:<domain> and SRV record lookups). Once the server can properly discover the AD forest, the provisioning setup should proceed successfully.