Azure AD connect - add second domain with same NetBios name (different forests, FQDNs)

Vladimir Kiesner 1 Reputation point
2019-12-18T08:13:07.72+00:00

hello. Currently we have our domain synced to Azure AD. We want to sync second domain into same tenant. Problem is - we have same NETBIOS domain name. Is it a problem?
To clarify:
Forest1/Domain1: fish.lv synced to Azure -> fish.onmicrosoft.com, internal domain fish.lv, domain name pre-Windows 2000: fish

Forest2/Domain 2: fish.lt need to be synced to same tenant -> fish.onmicrosoft.com, internal domain fish.lt, domain name pre-Windows 2000: fish

As far as i know, in general such configuration is supported (two forests|domains, one Azure AD connect server), BUT: having same legacy domain name is gray area for me. I know, what we are unable to make domain trust because of that.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,365 questions
{count} votes

18 answers

Sort by: Most helpful
  1. Biju Thankappan 101 Reputation points
    2019-12-19T04:17:34.46+00:00

    Hi, @Vladimir Kiesner Following two options are available: - Rename - Migrate However, either of the above has to performed on premises. Then, sync using Ad Connect. However, renaming can see unforeseen issues. Please refer this. Ideally, try this first in Test env and monitor for sometime to see if anything breaks. Things that could break are 3rd party apps, older versions of exchange, etc.

    1 person found this answer helpful.

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more