You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/add-custom-domain.md
+32-37Lines changed: 32 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Add your custom domain
3
-
description: Instructions about how to add a custom domain using Azure Active Directory.
3
+
description: Instructions about how to add your custom domain name to your tenant.
4
4
services: active-directory
5
5
author: barclayn
6
6
manager: amycolannino
@@ -9,108 +9,103 @@ ms.service: active-directory
9
9
ms.workload: identity
10
10
ms.subservice: fundamentals
11
11
ms.topic: how-to
12
-
ms.date: 01/23/2023
12
+
ms.date: 09/12/2023
13
13
ms.author: barclayn
14
14
ms.reviewer: elkuzmen
15
-
ms.custom: "it-pro, seodec18"
16
-
ms.collection: M365-identity-device-management
17
15
---
16
+
# Add your custom domain name to your tenant
18
17
19
-
# Add your custom domain name using the Azure portal
20
-
21
-
Azure Active Directory (Azure AD) tenants come 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 *alain\@contoso.com*.
18
+
Azure Active Directory (Azure AD) tenants come with an initial domain name like, `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 `[email protected]`.
22
19
23
20
## Before you begin
24
21
25
22
Before you can add a custom domain name, create your domain name with a domain registrar. For an accredited domain registrar, see [ICANN-Accredited Registrars](https://www.icann.org/registrar-reports/accredited-list.html).
After you get your domain name, you can create your first Azure AD directory. Sign in to the [Azure portal](https://portal.azure.com) for your directory, using an account with the **Owner** role for the subscription.
28
+
After you get your domain name, you can create your first directory. Sign in to the [Azure portal](https://portal.azure.com) for your directory, using an account with the [Owner](/azure/role-based-access-control/built-in-roles#owner) role for the subscription.
32
29
33
30
Create your new directory by following the steps in [Create a new tenant for your organization](./create-new-tenant.md#create-a-new-tenant-for-your-organization).
34
31
35
-
>[!IMPORTANT]
36
-
>The person who creates the tenant is automatically the Global administrator for that tenant. The Global administrator can add additional administrators to the tenant.
32
+
>[!IMPORTANT]
33
+
>The person who creates the tenant is automatically granted [Global Administrator](../roles/permissions-reference.md#global-administrator) privileges. The Global Administrator role is highly privileged and can add additional administrators to the tenant.
37
34
38
35
For more information about subscription roles, see [Azure roles](../../role-based-access-control/rbac-and-directory-admin-roles.md#azure-roles).
39
36
40
-
>[!TIP]
41
-
> If you plan to federate your on-premises Windows Server AD with Azure AD, then you need to select **I plan to configure this domain for single sign-on with my local Active Directory** when you run the Azure AD Connect tool to synchronize your directories.
37
+
>[!TIP]
38
+
> If you plan to federate on-premises Windows Server Active Directory with Azure AD, then you need to select **I plan to configure this domain for single sign-on with my local Active Directory** when you run the Azure AD Connect tool to synchronize your directories.
42
39
>
43
-
> You also need to register the same domain name you select for federating with your on-premises directory in the **Azure AD Domain** step in the wizard. To see what that setup looks like, see [Verify the Azure AD domain selected for federation](../hybrid/connect/how-to-connect-install-custom.md#verify-the-azure-ad-domain-selected-for-federation). If you don't have the Azure AD Connect tool, you can [download it here](https://go.microsoft.com/fwlink/?LinkId=615771).
40
+
> You also need to register the same domain name you select for federating with your on-premises directory in the **Azure AD Domain** step in the wizard. To see what that setup looks like, see [Verify the domain selected for federation](../hybrid/connect/how-to-connect-install-custom.md#verify-the-azure-ad-domain-selected-for-federation). If you don't have the Azure AD Connect tool, you can [download it here](https://go.microsoft.com/fwlink/?LinkId=615771).
44
41
45
-
## Add your custom domain name to Azure AD
42
+
## Add your custom domain name
46
43
47
44
After you create your directory, you can add your custom domain name.
48
45
49
-
1. Sign in to the [Azure portal](https://portal.azure.com)using a Global administrator account for the directory.
46
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com)as at least a [Domain Name Administrator](../roles/permissions-reference.md#domain-name-administrator).
50
47
51
-
1.Search for and select *Azure Active Directory* from any page. Then select **Custom domain names** > **Add custom domain**.
54
51
55
-
1. In **Custom domain name**, enter your organization's new name, in this example, *contoso.com*. Select **Add domain**.
52
+
1. In **Custom domain name**, enter your organization's domain, in this example, *contoso.com*. Select **Add domain**.
56
53
57
54
58
55
59
-
>[!IMPORTANT]
60
-
>You must include *.com*, *.net*, or any other top-level extension for this to work. When adding a custom domain, the Password Policy values will be inherited from the initial domain.
56
+
>[!IMPORTANT]
57
+
>You must include *.com*, *.net*, or any other top-level extension for this to work. When adding a custom domain, the Password Policy values will be inherited from the initial domain.
61
58
62
-
The unverified domain is added. The **contoso.com** page appears showing your DNS information. Save this information. You need it later to create a TXT record to configure DNS.
59
+
1.The unverified domain is added. The **contoso.com** page appears showing the DNS information needed to validate your domain ownership. Save this information.
63
60
64
61
65
62
66
63
## Add your DNS information to the domain registrar
67
64
68
-
After you add your custom domain name to Azure AD, you must return to your domain registrar and add the Azure AD DNS information from your copied TXT file. Creating this TXT record for your domain verifies ownership of your domain name.
65
+
After you add your custom domain name, you must return to your domain registrar and add the DNS information from your copied from the previous step. Creating this TXT or MX record for your domain verifies ownership of your domain name.
69
66
70
-
Go back to your domain registrar and create a new TXT record for your domain based on your copied DNS information. Set the time to live (TTL) to 3600 seconds (60 minutes), and then save the record.
67
+
Go back to your domain registrar and create a new TXT or MX record for your domain based on your copied DNS information. Set the time to live (TTL) to 3600 seconds (60 minutes), and then save the record.
71
68
72
-
>[!IMPORTANT]
73
-
>You can register as many domain names as you want. However, each domain gets its own TXT record from Azure AD. Be careful when you enter the TXT file information at the domain registrar. If you enter the wrong or duplicate information by mistake, you'll have to wait until the TTL times out (60 minutes) before you can try again.
69
+
>[!IMPORTANT]
70
+
>You can register as many domain names as you want. However, each domain gets its own TXT or MX record. Be careful when you enter the information at the domain registrar. If you enter the wrong or duplicate information by mistake, you'll have to wait until the TTL times out (60 minutes) before you can try again.
74
71
75
72
## Verify your custom domain name
76
73
77
-
After you register your custom domain name, make sure it's valid in Azure AD. The propagation from your domain registrar to Azure AD can be instantaneous or it can take a few days, depending on your domain registrar.
74
+
After you register your custom domain name, make sure it's valid in Microsoft Entra. The propagation time can be instantaneous or it can take a few days, depending on your domain registrar.
78
75
79
76
To verify your custom domain name, follow these steps:
80
77
81
-
1. Sign in to the [Azure portal](https://portal.azure.com)using a Global administrator account for the directory.
78
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com)as at least a [Domain Name Administrator](../roles/permissions-reference.md#domain-name-administrator).
82
79
83
-
1.Search for and select *Azure Active Directory* from any page, then select **Custom domain names**.
80
+
1.Browse to **Identity** > **Settings** > **Domain names**.
84
81
85
82
1. In **Custom domain names**, select the custom domain name. In this example, select **contoso.com**.
86
83
87
84
88
85
89
-
1. On the **contoso.com** page, select **Verify** to make sure your custom domain is properly registered and is valid for Azure AD.
86
+
1. On the **contoso.com** page, select **Verify** to make sure your custom domain is properly registered and is valid.
90
87
91
88
92
89
93
-
After you've verified your custom domain name, you can delete your verification TXT or MX file.
94
-
95
90
## Common verification issues
96
91
97
-
If Azure AD can't verify a custom domain name, try the following suggestions:
92
+
If you can't verify a custom domain name, try the following suggestions:
98
93
99
-
-**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.
94
+
-**Wait at least an hour and try again.** DNS records must propagate before you can verify the domain. This process can take an hour or more.
100
95
101
96
-**If you are trying to verify a child domain, verify the parent domain first.** Make sure the parent domain is created and verified first before you try to verify a child domain.
102
97
103
-
-**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.
98
+
-**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 in the Microsoft Entra admin center.
104
99
105
-
If you can't update the record on the registrar site, share the entry with someone who has permissions to add the entry and verify it's correct.
100
+
-If you can't update the record on the registrar site, share the entry with someone who has permissions to add the entry and verify it's correct.
106
101
107
102
-**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](../enterprise-users/domains-manage.md).
108
103
109
-
-**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. For more information, see [Take over an unmanaged directory as administrator in Azure Active Directory](../enterprise-users/domains-admin-takeover.md).
104
+
-**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. For more information, see [Take over an unmanaged directory](../enterprise-users/domains-admin-takeover.md).
110
105
111
106
## Next steps
112
107
113
-
- Add another Global administrator to your directory. For more information, see [How to assign roles and administrators](./how-subscriptions-associated-directory.md).
108
+
- Add another Global Administrator to your directory. For more information, see [How to assign roles and administrators](./how-subscriptions-associated-directory.md).
114
109
115
110
- Add users to your domain. For more information, see [How to add or delete users](./add-users.md).
0 commit comments