Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Microsoft Entra ID – Custom Domains and Directories

Posted on August 24, 2019

Hello, everyone. Continuing our Azure series, in today’s article we’ll cover custom domains and directories in Microsoft Entra ID. We’ll show how to register a custom domain, the benefits this configuration brings, and how to work with directories in Microsoft Entra ID.

What is a custom domain?

Every customer who joins Azure receives an initial domain called “domainname.onmicrosoft.com”. The custom domain lets you change the initial domain to one that’s familiar to the end user. This option makes it possible to create accounts in Microsoft Entra ID with the familiar domain and improve the experience when accessing Azure services.

In the scenario we’ll present, we’ll create a domain called ulyssesneves.com and validate it in the external DNS that’s authoritative for that domain.

Access the custom domains menu by clicking this link.

Click Add custom domain.

Fill in the domain you want to register in Azure and click Add.

Copy the code from the Destination or points to address field and create a TXT record in the DNS that hosts the domain you want to register.

If the record hasn’t been replicated yet, you’ll receive the message below when you click verify. In that case, wait.

Once replication is complete, when you click verify and don’t receive the error, click Make primary to set the registered domain as the default domain for accessing Azure.

Confirm your choice by clicking YES.

In the screen below, you can see that the custom domain has a status of Verified.

It’s strongly recommended to register the domain, and it’s one of the first tasks in planning your Azure usage, since this way it isn’t necessary to change the domain of users’ credentials later.

If the Azure administrator decides to register the domain after users already exist in Azure, it’s possible to change the sign-in credentials as we show below.

Access the menu Azure Active Directory > Users and  select the user that was created before the domain was customized.

In the user name field, remove the “.onmicrosoft.” portion and check whether a green checkmark appears confirming that this name is available.

After changing the account, let’s test access for the user Fred, whom we just updated in the Azure portal.

As shown below, the user Fred can sign in using the credential fred@ulyssesneves.com without the initial “onmicrosoft.com” domain.

What are Directories in Microsoft Entra ID?

The directory is the Microsoft Entra ID service used to provide administrative independence, access independence, synchronization, etc. You can register more than one domain in a directory and set a default domain for it. It’s possible to assign more than one subscription to the directory, however, only one tenant.

How to add a directory in Azure?

We’ll demonstrate creating a new directory in Azure.

Access the Microsoft Entra ID menu by clicking this link.

Click the Create a directory link.

Fill in the organization name, the initial domain, and click Create.

With the new directory created, you can access it through the Azure AD menu by clicking Switch directory.

Select the directory you want to access.

Summary
In today’s article, we talked about custom domains in Microsoft Entra ID and how to register a new domain in Azure. We also explained what directories in Microsoft Entra ID are, what they’re used for, how to create a new directory, and how to navigate between directories through the Azure portal.

In the next article, I’ll start a series about the Microsoft Entra Connect tool and how important this tool is for access management in an on-premises, hybrid, or cloud domain.

I hope this content has helped enrich your knowledge of Azure.

Did you like the post? Like and share it.

If you have any suggestions or comments, let us know.

[ ]’s

Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra ID topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}