Windows Azure and Office 365 – Managing a Custom Domain

Share this:

In this Tutorial we are going over the process to create a custom domain in your Windows Azure subscription and this task is key to enable any future synchronization that we are planning as part of this series.

The first step is to log on on Windows Azure portal (, then on the all items area (first icon on the left side) let’s click on our directory listed (it will contain the name of your Office 365 domain).

After that click on Domains tab and a list of all domains of your subscription will be listed.

Note: In this area we can check in a glance the status and if they are the primary domain of your subscription.


In order to add a new domain, let’s click on Add button located in the middle of the screen at the bottom.


In the Specify a domain name page. Type in the name of the valid domain and click on Add.


A message informing that the domain was added properly should show up right above the current dialog box, click on Next icon located on the right side.


That completes the process to create a new domain in Windows Azure. The next step soon after is the validation where we can use two different methods: adding either a TXT record or MX record in the Public Domain. The default option is TXT, as shown in the figure below.

Having that information we just need to go to the Public DNS provider and add the information and wait for the replication to take place and validate.


In our case our test domain is hosted at a cheap provider in US which allows us to manage the DNS from a web page. We went there and add the information and wait a couple of minutes.


You don’t want to keep that window open until your DNS is being replicated, so you can at any time select the domain that was created and the option to Verify will be available at the bottom. Click on it


After that the domain will be listed besides of your default domain and now it can be used to create user in the WAAD (Windows Azure Active Directory) and as long as we configured properly our local Active Directory any synchronized object from that domain will have that domain properly configured.


Written by Anderson Patricio

Anderson Patricio is a Canadian Exchange Server MVP and MCSM (Solutions Master) and he contributes to the Microsoft Community with articles, tutorials, blog posts, forums and book reviews. He is a regular contributor at, and (Portuguese).