Azure/OpenShift

How to add a custom domain name to Azure Active Directory

After you create your directory, you can add your custom domain name. Every new Azure AD tenant comes with an initial domain name, <domainname>.onmicrosoft.com. You can’t change or delete the initial domain name, but you can add your organization’s names. Adding custom domain names helps you to create user names that are familiar to your users, such as techdirectarchive.com. See this guide for reasons to deploy AAD.

A domain or accepted domain is a DNS zone for which a tenant has proven ownership by creating an arbitrarily named DNS record as requested by Microsoft). It represents the possible domain suffixes (or namespace) that directory objects can use. Each tenant has a core domain (onmicrosoft.com) and a default domain which by default is the core domain, but which can be changed. Neither of these is necessarily the primary domain used by the tenant as you have the option to have this changed. See this guide on how to set up an Azure AD Tenant.

A directory is the Azure AD service. Each directory has one or more domains. A directory can have many subscriptions associated with it, but only one tenant.

Follow the steps below to create a resource group
– Sign in to the Azure portal using a Global administrator account.
– Search for and select the Azure Active Directory.
– On the left pane, select Custom domain names.

– Click on Add custom domain as show

In Custom domain name dialogbox as shown below,
– Enter your organisations new name, in this example, techdirectarchive.com.
– Select Add domain.

When successfully added, you will be alerted that the Domain name was successfully added.

You will be required to add a TXT or MX file to your Domain in order to verify the domain belongs to you. See this article “what are the different types of DNS Record
– Proceed to add the TXT File or MX record to your DNS registrar for Azure AD DNS as shown below. This process might be different for your Domain.

When you are done creating the TXT or MX record , click on verify as shown below.

Note: Creating this TXT record for your domain verifies ownership of your domain name

If successful, you will get a notification that the verification process completed successfully.

Note: We can make this new custom domain as our primary domain. As you can see above, the option to make it a primary custom domain is grayed out.

Simply click on the custom domain names once again and
– Click on the new verified domain.

Note: After you've verified your custom domain name, you can delete your verification TXT or MX file.

Now you have the option to make the new custom domain the primary domain.

Upon clicking to make the new custom domain your primary domain, you will be asked to confirm the change by clicking on “Yes”.

When successfully added as the primary domain, you will get an alert that the task was successful.

When refrshed and, the verified doamin will be the primary domain as shown below.

Now you can download the Azure AD Connect to synchronize your on-premises to Azure Active Directory as well. You can download Microsoft Azure Active Directory Connect here.

Next, I will be adding (Azure Global Administrator), deleting and assigning permissions to users in Azure AD in the next guide.

Here are some common verification issues: If Azure AD can’t verify a custom domain name, try the following suggestions:

  • Wait at least an hour and try again. DNS records must propagate before Azure AD can verify the domain. This process can take an hour or more.
  • Make sure the DNS record is correct. Go back to the domain name registrar site. Make sure the entry is there, and that it matches the DNS entry information provided by Azure AD.
  • If you can’t update the record on the registrar site, share the entry with someone who has permission to add the entry and verify it’s correct.
  • Make sure the domain name isn’t already in use in another directory. A domain name can only be verified in one directory. If your domain name is currently verified in another directory, it can’t also be verified in the new directory. To fix this duplication problem, you must delete the domain name from the old directory. For more information about deleting domain names, see Manage custom domain names.
  • Make sure you don’t have any unmanaged Power BI tenants. If your users have activated Power BI through self-service sign-up and created an unmanaged tenant for your organization, you must take over management as an internal or external admin using PowerShell

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Buy me a coffeeBuy me a coffee

Advertisements
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x