Skip to content

Commit c048b8e

Browse files
authored
Merge branch 'release-win365-2201' into aadjopnc2
2 parents c8e43e7 + 30e37e7 commit c048b8e

1 file changed

Lines changed: 6 additions & 9 deletions

File tree

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

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -30,13 +30,9 @@ ms.collection: M365-identity-device-management
3030

3131
# Create on-premises network connection
3232

33-
[On-premises network connections](on-premises-network-connections.md) (OPNC) are required so that Cloud PCs can:
33+
[On-premises network connections](on-premises-network-connections.md) (OPNC) let you provision Cloud PCs that are attached to a virtual network that you manage.
3434

35-
- Be provisioned.
36-
- Be joined to your company’s domain.
37-
- Have connectivity to your organization’s on-premises resources.
38-
39-
You can have up to 10 connections per tenant.
35+
You can have up to 10 OPNCs per tenant.
4036

4137
As part of the connection process, the Windows 365 service is granted the following permissions:
4238

@@ -46,12 +42,12 @@ As part of the connection process, the Windows 365 service is granted the follow
4642

4743
## Requirements
4844

49-
To create a connection, you must:
45+
To create an OPNC, you must:
5046

5147
- Be an [Intune Administrator in Azure AD](/azure/active-directory/roles/permissions-reference).
52-
- Have [Owner permissions on the Azure subscription](/azure/cost-management-billing/manage/add-change-subscription-administrator) that contains the virtual network with connectivity to your on-premises domain controller and network.
48+
- Have [Owner permissions on the Azure subscription](/azure/cost-management-billing/manage/add-change-subscription-administrator) that contains the virtual network.
5349

54-
## To create an on-premises network connection
50+
## To create a Hybrid Azure Active Directory Join OPNC
5551

5652
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 connection**.
5753
![Screenshot of create connection](./media/create-on-premises-network-connection/create-connection.png)
@@ -64,6 +60,7 @@ To create a connection, you must:
6460
- **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.
6561
- **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.
6662
- **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.
63+
6764
- AD domain password: The password for the user specified above.
6865
- Confirm AD domain password: The password for the user specified above.
6966

0 commit comments

Comments
 (0)