Skip to content

Commit 47e119b

Browse files
authored
Update create-on-premises-network-connection.md
1 parent d18ad43 commit 47e119b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ To create an OPNC, you must:
4747
- Be an [Intune Administrator in Azure AD](/azure/active-directory/roles/permissions-reference).
4848
- 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.
4949
- Make sure that your PowerShell execution policy is configured to allow RemoteSigned scripts. If you use Group Policy to set execution policy, make sure that the Group Policy Object (GPO) targeted at the Organizational Unit (OU) defined in the OPNC is configured to allow RemoteSigned scripts. For more information, see [Set-ExecutionPolicy](/powershell/module/microsoft.powershell.security/set-executionpolicy).
50-
- For Disaster Recovery purposes, please ensure there are at least 50% of the IP addresses available in your subnet. If reprovisioning for DR is required, sufficient new IP address will be required for each Cloud PC provisioned on the subnet.
50+
- For Disaster Recovery (DR) purposes, make sure that there are at least 50% of the IP addresses available in your subnet. If reprovisioning for DR is required, sufficient new IP address are required for each Cloud PC provisioned on the subnet.
5151

5252
## Create an OPNC
5353

0 commit comments

Comments
 (0)