Skip to content

Commit ad62ca1

Browse files
Merge pull request #8649 from ErikjeMS/win365
W38544712 gcc req
2 parents ae14972 + 83b8cac commit ad62ca1

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

windows-365/enterprise/create-azure-network-connection.md

Lines changed: 2 additions & 1 deletion
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: 10/03/2022
1111
ms.topic: how-to
1212
ms.service: cloudpc
1313
ms.subservice:
@@ -48,6 +48,7 @@ To create an ANC, you must:
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 Unrestricted 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 ANC is configured to allow Unrestricted scripts. For more information, see [Set-ExecutionPolicy](/powershell/module/microsoft.powershell.security/set-executionpolicy).
5050
- 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 addresses are required for each Cloud PC provisioned on the subnet.
51+
- For Windows 365 Governement, make sure to complete the script options listed in [Set up tenants for Windows 365 Government](set-up-tenants-windows-365-gcc.md).
5152

5253
## Create an ANC
5354

0 commit comments

Comments
 (0)