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
# Take over an unmanaged directory as administrator in Azure Active Directory
20
20
21
-
This article describes two ways to take over a DNS domain name in an unmanaged directory in Azure Active Directory (Azure AD), part of Microsoft Entra. When a self-service user signs up for a cloud service that uses Azure AD, they're added to an unmanaged Azure AD directory based on their email domain. For more about self-service or "viral" sign-up for a service, see [What is self-service sign-up for Azure Active Directory?](directory-self-service-signup.md)
21
+
This article describes two ways to take over a DNS domain name in an unmanaged directory in Microsoft Entra ID formerly known as Azure AD. When a self-service user signs up for a cloud service that uses Microsoft Entra ID, they're added to an unmanaged Entra ID directory based on their email domain. For more about self-service or "viral" sign-up for a service, see [What is self-service sign-up for Microsoft Entra ID?](directory-self-service-signup.md)
## Decide how you want to take over an unmanaged directory
27
-
During the process of admin takeover, you can prove ownership as described in [Add a custom domain name to Azure AD](../fundamentals/add-custom-domain.md). The next sections explain the admin experience in more detail, but here's a summary:
27
+
28
+
During the process of admin takeover, you can prove ownership as described in [Add a custom domain name to Microsoft Entra ID](../fundamentals/add-custom-domain.md). The next sections explain the admin experience in more detail, but here's a summary:
28
29
29
30
* When you perform an ["internal" admin takeover](#internal-admin-takeover) of an unmanaged Azure directory, you're added as the global administrator of the unmanaged directory. No users, domains, or service plans are migrated to any other directory you administer.
30
31
31
32
* When you perform an ["external" admin takeover](#external-admin-takeover) of an unmanaged Azure directory, you add the DNS domain name of the unmanaged directory to your managed Azure directory. When you add the domain name, a mapping of users to resources is created in your managed Azure directory so that users can continue to access services without interruption.
32
33
33
34
## Internal admin takeover
34
35
35
-
Some products that include SharePoint and OneDrive, such as Microsoft 365, don't support external takeover. If that is your scenario, or if you're an admin and want to take over an unmanaged or "shadow" Azure AD organization create by users who used self-service sign-up, you can do this with an internal admin takeover.
36
+
Some products that include SharePoint and OneDrive, such as Microsoft 365, don't support external takeover. If that is your scenario, or if you're an admin and want to take over an unmanaged or "shadow" Microsoft Entra ID organization created by users who used self-service sign-up, you can do this with an internal admin takeover.
36
37
37
38
1. Create a user context in the unmanaged organization through signing up for Power BI. For convenience of example, these steps assume that path.
38
39
@@ -48,11 +49,11 @@ Some products that include SharePoint and OneDrive, such as Microsoft 365, don't
48
49
49
50

50
51
51
-
When the DNS TXT records are verified at your domain name registrar, you can manage the Azure AD organization.
52
+
When the DNS TXT records are verified at your domain name registrar, you can manage the Entra ID organization.
52
53
53
54
When you complete the preceding steps, you're now the global administrator of the Fourth Coffee organization in Microsoft 365. To integrate the domain name with your other Azure services, you can remove it from Microsoft 365 and add it to a different managed organization in Azure.
54
55
55
-
### Adding the domain name to a managed organization in Azure AD
56
+
### Adding the domain name to a managed organization in Entra ID
@@ -65,26 +66,28 @@ When you complete the preceding steps, you're now the global administrator of th
65
66
66
67
5. If you have any users or groups in Microsoft 365 that reference the removed domain name, they must be renamed to the .onmicrosoft.com domain. If you force delete the domain name, all users are automatically renamed, in this example to *user\@fourthcoffeexyz.onmicrosoft.com*.
67
68
68
-
6. Sign in to the [Azure portal](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) with an account that is the Global Administrator for the Azure AD organization.
69
-
70
-
7. Select **Custom domain names**, then add the domain name. You'll have to enter the DNS TXT records to verify ownership of the domain name.
69
+
6. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
70
+
7. In the search box at the top of the page, search for **Domain Names**.
71
+
72
+
8. Select **+ Add custom domain names**, then add the domain name. You'll have to enter the DNS TXT records to verify ownership of the domain name.
71
73
72
-

74
+

73
75
74
76
> [!NOTE]
75
77
> Any users of Power BI or Azure Rights Management service who have licenses assigned in the Microsoft 365 organization must save their dashboards if the domain name is removed. They must sign in with a user name like *user\@fourthcoffeexyz.onmicrosoft.com* rather than *user\@fourthcoffee.xyz*.
76
78
77
79
## External admin takeover
78
80
79
-
If you already manage an organization with Azure services or Microsoft 365, you can't add a custom domain name if it's already verified in another Azure AD organization. However, from your managed organization in Azure AD you can take over an unmanaged organization as an external admin takeover. The general procedure follows the article [Add a custom domain to Azure AD](../fundamentals/add-custom-domain.md).
81
+
If you already manage an organization with Azure services or Microsoft 365, you can't add a custom domain name if it's already verified in another Entra ID organization. However, from your managed organization in Entra ID you can take over an unmanaged organization as an external admin takeover. The general procedure follows the article [Add a custom domain to Entra ID](../fundamentals/add-custom-domain.md).
80
82
81
-
When you verify ownership of the domain name, Azure AD removes the domain name from the unmanaged organization and moves it to your existing organization. External admin takeover of an unmanaged directory requires the same DNS TXT validation process as internal admin takeover. The difference is that the following are also moved over with the domain name:
83
+
When you verify ownership of the domain name, Entra ID removes the domain name from the unmanaged organization and moves it to your existing organization. External admin takeover of an unmanaged directory requires the same DNS TXT validation process as internal admin takeover. The difference is that the following are also moved over with the domain name:
82
84
83
85
- Users
84
86
- Subscriptions
85
87
- License assignments
86
88
87
89
### Support for external admin takeover
90
+
88
91
External admin takeover is supported by the following online services:
89
92
90
93
- Azure Rights Management
@@ -103,17 +106,16 @@ External admin takeover isn't supported for any service that has service plans t
103
106
> [!NOTE]
104
107
> External admin takeover is not supported cross cloud boundaries (ex. Azure Commercial to Azure Government). In these scenarios it is recommended to perform External admin takeover into another Azure Commercial tenant, and then delete the domain from this tenant so you may verify successfully into the destination Azure Government tenant.
105
108
106
-
You can optionally use the [**ForceTakeover** option](#azure-ad-powershell-cmdlets-for-the-forcetakeover-option) for removing the domain name from the unmanaged organization and verifying it on the desired organization.
107
109
108
110
#### More information about RMS for individuals
109
111
110
112
For [RMS for individuals](/azure/information-protection/rms-for-individuals), when the unmanaged organization is in the same region as the organization that you own, the automatically created [Azure Information Protection organization key](/azure/information-protection/plan-implement-tenant-key) and [default protection templates](/azure/information-protection/configure-usage-rights#rights-included-in-the-default-templates) are additionally moved over with the domain name.
111
113
112
114
The key and templates aren't moved over when the unmanaged organization is in a different region. For example, if the unmanaged organization is in Europe and the organization that you own is in North America.
113
115
114
-
Although RMS for individuals is designed to support Azure AD authentication to open protected content, it doesn't prevent users from also protecting content. If users did protect content with the RMS for individuals subscription, and the key and templates weren't moved over, that content isn't accessible after the domain takeover.
116
+
Although RMS for individuals is designed to support Entra ID authentication to open protected content, it doesn't prevent users from also protecting content. If users did protect content with the RMS for individuals subscription, and the key and templates weren't moved over, that content isn't accessible after the domain takeover.
115
117
116
-
### Azure AD PowerShell cmdlets for the ForceTakeover option
118
+
### Entra ID PowerShell cmdlets for the ForceTakeover option
117
119
118
120
You can see these cmdlets used in [PowerShell example](#powershell-example).
119
121
@@ -128,7 +130,7 @@ cmdlet | Usage
128
130
`get-mgdomain` | The domain list now shows the domain name as **Verified**.
129
131
130
132
> [!NOTE]
131
-
> The unmanaged Azure AD organization is deleted 10 days after you exercise the external takeover force option.
133
+
> The unmanaged Entra ID organization is deleted 10 days after you exercise the external takeover force option.
132
134
133
135
### PowerShell example
134
136
@@ -143,7 +145,7 @@ cmdlet | Usage
143
145
```powershell
144
146
Get-MgDomain
145
147
```
146
-
3. Run the New-MgDomain cmdlet to add a new domain in Azure:
148
+
3. Run the New-MgDomain cmdlet to add a new domain:
Copy file name to clipboardExpand all lines: articles/active-directory/enterprise-users/domains-manage.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,8 @@ A domain name is an important part of the identifier for resources in many Azure
28
28
29
29
When your organization is created, the initial domain name, such as ‘contoso.onmicrosoft.com,’ is also the primary domain name. The primary domain is the default domain name for a new user when you create a new user. Setting a primary domain name streamlines the process for an administrator to create new users in the portal. To change the primary domain name:
30
30
31
-
1. Sign in to the [Azure portal](https://portal.azure.com)with an account that's a Global Administrator for the organization.
32
-
2. Select **Azure Active Directory**.
31
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com)as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
32
+
1. Select Microsoft Entra ID (Azure AD).
33
33
3. Select **Custom domain names**.
34
34
35
35

1. Sign in to the [Azure portal](https://portal.azure.com).
87
-
1. Browse to **Azure Active Directory** > **Groups**, and then select **New group**.
84
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
1. On the **New Group** page, select **Office 365**, and then fill out the required information for the new group and select a sensitivity label from the list.
89
88
90
89

@@ -95,8 +94,9 @@ Your group is created and the site and group settings associated with the select
95
94
96
95
## Assign a label to an existing group in Azure portal
97
96
98
-
1. Sign in to the [Azure portal](https://portal.azure.com) with a Groups admin account, or as a group owner.
99
-
1. Browse to **Azure Active Directory** > **Groups**.
97
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
98
+
1. Select Microsoft Entra ID (Azure AD).
99
+
1. Select **Groups**.
100
100
1. From the **All groups** page, select the group that you want to label.
101
101
1. On the selected group's page, select **Properties** and select a sensitivity label from the list.
102
102
@@ -106,8 +106,9 @@ Your group is created and the site and group settings associated with the select
106
106
107
107
## Remove a label from an existing group in Azure portal
108
108
109
-
1. Sign in to the [Azure portal](https://portal.azure.com) with a Global Administrator or Groups admin account, or as a group owner.
110
-
1. Browse to **Azure Active Directory** > **Groups**.
109
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
110
+
1. Select Microsoft Entra ID (Azure AD).
111
+
1. Select **Groups** > **All groups**.
111
112
1. From the **All groups** page, select the group that you want to remove the label from.
112
113
1. On the **Group** page, select **Properties**.
113
114
1. Select **Remove**.
@@ -146,9 +147,10 @@ If the label you are looking for is not in the list, this could be the case for
146
147
147
148
Labels can be swapped at any time using the same steps as assigning a label to an existing group, as follows:
148
149
149
-
1. Sign in to the [Azure portal](https://portal.azure.com) with a Global or Group administrator account or as group owner.
150
-
1. Browse to **Azure Active Directory** > **Groups**.
151
-
1. From the **All groups** page, select the group that you want to label.
150
+
1. 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
151
+
1. Select Microsoft Entra ID (Azure AD).
152
+
1. Select **Groups**.
153
+
1. Choose **All groups**, select the group that you want to label.
152
154
1. On the selected group's page, select **Properties** and select a new sensitivity label from the list.
# Bulk download members of a group in Azure Active Directory
19
19
20
-
You can bulk download the members of a group in your organization to a comma-separated values (CSV) file in the portal for Azure Active Directory (Azure AD), part of Microsoft Entra. All admins and non-admin users can download group membership lists.
20
+
You can bulk download the members of a group in your organization to a comma-separated values (CSV) file from the Microsoft Entra Admin center. All admins and non-admin users can download group membership lists.
1. Sign in to the [Azure portal](https://portal.azure.com) with an account in the organization.
27
-
1. In Azure AD, select **Groups** > **All groups**.
24
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
25
+
1. Select Microsoft Entra ID (Azure AD).
26
+
1. Select **Groups** > **All groups**.
28
27
1. Open the group whose membership you want to download, and then select **Members**.
29
28
1. On the **Members** page, select **Bulk operations** and choose, **Download members** to download a CSV file listing the group members.
Copy file name to clipboardExpand all lines: articles/active-directory/enterprise-users/groups-bulk-download.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,9 @@ You can download a list of all the groups in your organization to a comma-separa
27
27
>[!NOTE]
28
28
> The columns downloaded are pre-defined
29
29
30
-
1. Sign in to the [Azure portal](https://portal.azure.com) with an account in your organization.
31
-
1. In Azure AD, select **Groups** > **Download groups**.
30
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
31
+
1. Select Microsoft Entra ID (Azure AD).
32
+
1. Select **Groups** > **Download groups**.
32
33
1. On the **Groups download** page, select **Start** to receive a CSV file listing your groups.
33
34
34
35

1. Sign in to the [Azure portal](https://portal.azure.com) with a User administrator account in the organization. Group owners can also bulk import members of groups they own.
49
-
1. In Azure AD, select **Groups** > **All groups**.
48
+
49
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
50
+
1. Select Microsoft Entra ID (Azure AD).
51
+
>[!NOTE]
52
+
>Group owners can also bulk import members of groups they own.
53
+
1. Select **Groups** > **All groups**.
50
54
1. Open the group to which you're adding members and then select **Members**.
51
55
1. On the **Members** page, select **bulk operations** and then choose **Import members**.
52
56
1. On the **Bulk import group members** page, select **Download** to get the CSV file template with required group member properties.
1. Sign in to the [Azure portal](https://portal.azure.com) with a User administrator account in the organization. Group owners can also bulk remove members of groups they own.
48
-
1. In Azure AD, select **Groups** > **All groups**.
47
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Global Administrator](../roles/permissions-reference.md#global-administrator).
48
+
1. Select Microsoft Entra ID (Azure AD).
49
+
1. Select **Groups** > **All groups**.
49
50
1. Open the group from which you're removing members and then select **Members**.
50
51
1. On the **Members** page, select **Remove members**.
51
52
1. On the **Bulk remove group members** page, select **Download** to get the CSV file template with required group member properties.
0 commit comments