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/hdinsight/domain-joined/apache-domain-joined-create-configure-enterprise-security-cluster.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,9 +29,9 @@ Before you use this process in your own environment:
29
29
30
30
## Create an on-premises environment
31
31
32
-
In this section, you'll use an Azure Quickstart deployment template to create new VMs, configure DNS, and add a new Azure AD forest.
32
+
In this section, you'll use an Azure Quickstart deployment template to create new VMs, configure DNS, and add a new Active Directory forest.
33
33
34
-
1. Go to the Quickstart deployment template to [Create an Azure VM with a new Azure AD forest](https://azure.microsoft.com/resources/templates/active-directory-new-domain/).
34
+
1. Go to the Quickstart deployment template to [Create an Azure VM with a new Active Directory forest](https://azure.microsoft.com/resources/templates/active-directory-new-domain/).
35
35
36
36
1. Select **Deploy to Azure**.
37
37
1. Sign in to your Azure subscription.
@@ -122,7 +122,7 @@ The users will be synchronized with Azure AD.
122
122
123
123
Now you'll configure your Azure AD tenant so that you can synchronize users and groups from the on-premises Active Directory instance to the cloud.
124
124
125
-
1. Create an Azure AD tenant administrator.
125
+
1. Create an Active Directory tenant administrator.
126
126
1. Sign in to the Azure portal and select your Azure AD tenant, **HDIFabrikam**.
127
127
1. Under **Manage**, select **Users** > **New user**.
128
128
1. Enter the following details for the new user:
@@ -166,7 +166,7 @@ Now you'll configure your Azure AD tenant so that you can synchronize users and
166
166
167
167
1. On the **Connect to Active Directory Domain Services** page, enter the username and password for an enterprise admin account. Use the username `HDIFabrikam\HDIFabrikamAdmin` and its password that you created earlier. Then select **Next**.
168
168
169
-

169
+

170
170
1. On the **Azure AD sign-in configuration** page, select **Next**.
171
171

172
172
@@ -364,16 +364,16 @@ This step requires the following prerequisites:
364
364
1. Select **Custom (size, settings, apps)**.
365
365
2. Enter details for **Basics** (section 1). Ensure that the **Cluster type** is **Spark 2.3 (HDI 3.6)**. Ensure that the **Resource group** is **HDIFabrikam-CentralUS**.
366
366
367
-
1. For **Security + networking** (section 2), complete the following steps:
368
-
1. Under **Enterprise Security Package**, select **Enabled**.
369
-
1. Select **Cluster admin user** and select the **HDIAdmin** account that you created as the on-premises admin user. Click **Select**.
370
-
1. Select **Cluster access group** > **HDIUserGroup**. Any user that you add to this group in the future will be able to access HDInsight clusters.
367
+
1. For **Security + networking** (section 2), fill in the following details:
368
+
* Under **Enterprise Security Package**, select **Enabled**.
369
+
* Select **Cluster admin user** and select the **HDIAdmin** account that you created as the on-premises admin user. Click **Select**.
370
+
* Select **Cluster access group** > **HDIUserGroup**. Any user that you add to this group in the future will be able to access HDInsight clusters.
371
371
372
372

373
373
374
374
1. Complete the other steps of the cluster configuration and verify the details on the **Cluster summary**. Select **Create**.
375
375
376
-
1. Sign in to the Ambari UI for the newly created cluster at `https://CLUSTERNAME.azurehdinsight.net`. Use your admin username *[email protected]* and its password.
376
+
1. Sign in to the Ambari UI for the newly created cluster at `https://CLUSTERNAME.azurehdinsight.net`. Use your admin username `[email protected]` and its password.
0 commit comments