Merge branch 'patch-6' of https://github.com/ChristianMontoya/memdocs-pr into patch-6

Author: ChristianMontoya

windows-365/enterprise/create-on-premises-network-connection.md

@@ -47,36 +47,25 @@ To create an OPNC, you must:
 - Be an [Intune Administrator in Azure AD](/azure/active-directory/roles/permissions-reference).
 - Have [Owner permissions on the Azure subscription](/azure/cost-management-billing/manage/add-change-subscription-administrator) that contains the virtual network.
 
-## To create an Azure Active Directory Join OPNC
+## Create an OPNC
 
-1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **On-premises network connection** > **Create** > **Azure AD Join (preview)**.
+1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **On-premises network connection** > **Create**.
+2. Depending on the type of OPNC you want to create, choose **Azure AD Join (preview)** or **Hybrid Azure AD Join**.
 ![Screenshot of create connection dropdown](./media/create-on-premises-network-connection/create-connection-dropdown.png)
-2. On the **Network details** page, enter a **Name** for the new connection. The connection name must be unique within the customer tenant.
-![Screenshot of connection name](./media/create-on-premises-network-connection/create-aadj-connection.png)
-3. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy OPNC](health-checks.md), you won't be able to proceed.
-4. Select a **Virtual network** and **Subnet**.6
-5. Select **Next**.
-6. On the **Review + Create** page, select **Create**.
-
-## To create a Hybrid Azure Active Directory Join OPNC
-
-1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **On-premises network connection** > **Create** > **Hybrid Azure AD Join**.
-![Screenshot of create connection dropdown](./media/create-on-premises-network-connection/create-connection-dropdown.png)
-2. On the **Network details** page, enter a **Name** for the new connection. The connection name must be unique within the customer tenant.
-![Screenshot of connection name](./media/create-on-premises-network-connection/create-hybridaadj-connection.png)
-3. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy OPNC](health-checks.md), you won't be able to proceed.
-4. Select a **Virtual network** and **Subnet**.
-5. Select **Next**.
-6. On the **AD domain** page, provide the following information:
+3. On the **Network details** page, enter a **Name** for the new connection. The connection name must be unique within the customer tenant.
+4. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy OPNC](health-checks.md), you won't be able to proceed.
+5. Select a **Virtual network** and **Subnet**.
+6. Select **Next**.
+7. For hybrid Azure AD join OPNCs, on the **AD domain** page, provide the following information:
     - **AD domain name**: The DNS name of the Active Directory domain that you want to use for connecting and provisioning Cloud PCs. For example, corp.contoso.com.
     - **Organizational unit**: (Optional.) An organizational unit (OU) is a container within an Active Directory domain, which can hold users, groups, and computers. Make sure that this OU is enabled to sync with Azure AD Connect. Provisioning will fail if this OU isn't syncing.
     - **AD domain username**: The username, in user principal name (UPN) format, that you want to use for connecting the Cloud PCs to your Active Directory domain. For example, [email protected]. This service account must have permission to join computers to the domain and, if set, the target OU. 
 
     - AD domain password: The password for the user specified above.
     - Confirm AD domain password: The password for the user specified above.
 
-7. Select **Next**.
-8. On the **Review + Create** page, select **Create**.
+8. Select **Next**.
+9. On the **Review + Create** page, select **Create**.
 
 <!-- ########################## -->
 ## Next steps