Skip to content

Commit c3858b3

Browse files
authored
Merge pull request #6822 from ErikjeMS/win365
36553606
2 parents 52a68e1 + 7535e3f commit c3858b3

1 file changed

Lines changed: 8 additions & 4 deletions

File tree

windows-365/enterprise/on-premises-network-connections.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: ErikjeMS
88
ms.author: erikje
99
manager: dougeby
10-
ms.date: 02/08/2022
10+
ms.date: 02/16/2022
1111
ms.topic: overview
1212
ms.service: cloudpc
1313
ms.subservice:
@@ -91,12 +91,16 @@ To manually trigger a full health check, sign in to the [Microsoft Endpoint Mana
9191
The OPNC wizard requires access to Azure and, optionally, on-premises domain resources. The following permissions are required for the OPNC:
9292

9393
- Azure
94-
- Sufficient permissions to grant Windows 365 reader permissions on the selected subscription.
95-
- Sufficient permissions to grant Windows 365 network contributor permissions on the selected resource group.
96-
- Sufficient permissions to grant Windows 365 network contributor permissions on the selected virtual net.
94+
- Subscription Owner or Subscription User Access Administrator.
9795
- Active directory (Hybrid Azure AD Join OPNCs only)
9896
- An Active Directory user account with sufficient permissions to join the AD domain into this Organizational Unit.
9997

98+
To create, edit , or delete an OPNC, you'll also need to have one of the following permissions:
99+
100+
- Intune Administrator in Azure AD
101+
- Cloud PC administrator
102+
- Global Administrator
103+
100104
For a full list of requirements, see [Windows 365 requirements](requirements.md).
101105

102106
## Changing an on-premises network connection

0 commit comments

Comments
 (0)