Adding and Verifying a Domain for the NEW Office 365

After you have finished Signing up for the NEW Office 365, you are issued a Microsoft Office 365 Tenant account. From this account, you will want to add your public domain. This will allow Microsoft to host the desired Office 365 services for you and will allow you to use you own domain, rather than the tenant domain account ( default account.

The process should be quite easy and painless as long as you have access to the Microsoft Online Portal, with a Global Admin account, and access to your public facing DNS.


  1. Open Internet Explorer



  3. Click Domains


  4. Click Add a Domain


  5. Click Start Step 1


  6. Enter your public domain name and click Next


  7. Domain verification needs to be completed by adding a TXT or MX record into your public facing DNS. This is critical to verify ownership of the domain. In most cases the safest and method is to add the TXT record.


  8. Login to your public DNS provider and enter the TXT record specified by Microsoft. I choose to use GoDaddy as I find they are a one stop shop for domains, DNS, hosting, certificates and the kitchen sink.


  9. After the TXT record has been added you can go back to the Office 365 Portal site. Click the Done, verify now button



  10. Once the domain is verified, click Finish


  11. Click Start Step 2


  12. At this point you have the option to add user accounts. Depending on what your plans are, you can add them manually, with a CSV file or at a later date. For this post, I elected to not add any users at this time.


  13. Click Next


  14. Click Start Step 3


  15. We have to set the purpose of the domain. For this post, we are going to select Exchange Online and Lync Online. This is the default configuration and the most common. I am also going to leave the on-premise mailbox option unchecked at this point as well. We can change this later.


  16. Click Next


  17. At this point we are supplied a list of DNS records that will have to be added for the Office 365 Services to work. Depending on your DNS setup (split brain); these will have to be entered into your public and private DNS.


    WARNING – If you are in a production state, changing the DNS records will affect service. Plan accordingly. Depending on your situation, you can add all the records except the MX record. This is usually changed after the migration is completed.


  18. For my example, I am in non-production and I have entered all DNS records as provided by Microsoft.


    After all (or the ones that you want to add now) are added, give it sometime to update


  19. Click Done, go check


  20. Your DNS records will be verified


  21. Click Finish


  22. You will now see the domain is added and Active



At this point your domain is added and active with in Office 365.


Complete Series:

Getting to know the NEW Office 365

  1. Does Microsoft have FREE training for the NEW Office 365?
  2. Signing up for the NEW Office 365
  3. Adding and Verifying a Domain for the NEW Office 365
  4. Creating Cloud Users for the NEW Office 365
  5. Configuring Desktops for the NEW Office 365
  6. Exchange 2003 Cutover Migration to the NEW Office 365
  7. Exchange 2007 Cutover Migration to the NEW Office 365
  8. Setting up AD FS and Enabling Single Sign-On to the NEW Office 365
  9. Setting up AD FS Proxy Servers for Single Sign-On to the NEW Office 365
  10. Setting up Directory Synchronization with the NEW Office 365
  11. Activating and Licensing a Synchronized User in the NEW Office 365
  12. Testing Single Sign-on to the NEW Office 365
  13. Making the Single Sign-On Solution Highly Available
  14. Exchange Hybrid Deployment with the NEW Office 365

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me

12 thoughts on “Adding and Verifying a Domain for the NEW Office 365

  1. Pingback: From the MVPs: Exchange 2007 cutover migration to the NEW Office 365 - Microsoft Press - Site Home - MSDN Blogs

  2. Pingback: Public website on Office 365 with you own domain name | Brendon Ford

  3. Rob Wellesley

    A useful addition to your series would be setting up an Internal Relay system, where the MX and some mailboxes will stay with the POP3 provider, but some mailboxes will be on O365


    1. Kelsey EppsKelsey Epps Post author

      I have a POP3 migration series, where email is in both POP3 and Exchange. It gets complicated for the average admin, because of the mail routing and vanity domains.

  4. Pingback: Public website on Office 365 with your own domain name -

  5. Vishal

    I have Hybird on Exchange 2010, MX is pointing to on-premise and migration is in progress. I will decommission on-premise I will move MX to O365 and Exchange server once all users are migrated. We have 5 accepted domain. We have verified only primary domain. Do we need to verify other domain as well prior to removing moving MX to O365 & Decommissioning on-premise server or primary verified domain will work fine.

    1. Kelsey EppsKelsey Epps Post author

      You should verify all accepted domains in Office 365. If the domain isn’t added and verified in Office 365, then you will have no DNS settings provided from Microsoft, thus you will not be able to change them.

      1. Vishal

        Hi Kelsey, Thanks for the update.

        In scenario of the Hybrid, is it ok if we have primary domain verified.

        1. Kelsey EppsKelsey Epps Post author

          If you plan to route mail to any domain, it needs to be added and verified in Office 365.

  6. Chris

    Hi Kelsey, once domain is verified, and other dns is set up, does that TXT verification record stay or can it be removed?


Leave a Reply