locked
AD with the same name of Office 365 domain RRS feed

  • Question

  • Hello

    I write from Spain, sorry for my english. My question it´s about the idea of make AD with the same domain that we use in Office 365. I want to shutdown my physical servers and create new servers in Azure with the new AD and later connect all my computers to the new AD

    Somepeople said me that it´s a bad idea use the same name to the domain (AD) and the Office 365 domain that obviusly it´s the name of the web page of the organization.

    What do you think about this?

    I hope that i explained well my doubt.

    Thanks for all.

    • Moved by Ajay Kadam Monday, March 19, 2018 1:12 PM better suited here
    Monday, March 19, 2018 10:53 AM

Answers

  • Do not create new Active Directory forests with the same name as an external DNS name. For example, if your Internet DNS URL is http://contoso.com, you must choose a different name for your internal forest to avoid future compatibility issues. Refer: Install a new Windows server active directory forest

    You may also refer the best practices for naming convention of domain described here.

    Now, you can create a new Windows Server Active Directory environment on a virtual machine on an Azure virtual network. In this case, the Azure virtual network is not connected to an on-premises network. You should use site to site VPN connection to this virtual network for getting your on-premise machine in newly created domain. Refer: Install a new Active Directory forest on an Azure virtual network.

    ---------------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    • Proposed as answer by Ajay Kadam Monday, March 19, 2018 1:13 PM
    • Marked as answer by Luis CDS Wednesday, March 21, 2018 11:41 AM
    Monday, March 19, 2018 1:13 PM

All replies

  • Do not create new Active Directory forests with the same name as an external DNS name. For example, if your Internet DNS URL is http://contoso.com, you must choose a different name for your internal forest to avoid future compatibility issues. Refer: Install a new Windows server active directory forest

    You may also refer the best practices for naming convention of domain described here.

    Now, you can create a new Windows Server Active Directory environment on a virtual machine on an Azure virtual network. In this case, the Azure virtual network is not connected to an on-premises network. You should use site to site VPN connection to this virtual network for getting your on-premise machine in newly created domain. Refer: Install a new Active Directory forest on an Azure virtual network.

    ---------------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    • Proposed as answer by Ajay Kadam Monday, March 19, 2018 1:13 PM
    • Marked as answer by Luis CDS Wednesday, March 21, 2018 11:41 AM
    Monday, March 19, 2018 1:13 PM
  • Thank you very much for the reply.

    Regarding what you comment about VPN site to site, I know it and I have mounted an Azure to my private network. But above all it is clear that it is better not to use domains that are on the internet. I will use the option of trusted domains or something similar.

    Regards

    Wednesday, March 21, 2018 11:40 AM