Skip to content

Commit af2e63f

Browse files
committed
Learn Editor: Update troubleshoot-azure-network-connection.md
1 parent ecd01df commit af2e63f

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

support/windows-365/troubleshoot-azure-network-connection.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,14 @@ Successful communication with a domain controller within your organization is es
4141
> [!NOTE]
4242
> This section only applies to hybrid environments.
4343
44+
### WinRM requirements for ANC
45+
46+
WinRM (Windows Remote Management) is required to complete ANC setup.
47+
48+
To ensure successful provisioning, please verify that WinRM is not restricted to specific IP Addresses, whether through Group Policy Object (GPO) or Microsoft Intune Configuration Service Provider (CSP), for groups used in your provisioning policies. WinRM should be configured to allow network requests from any IP address.
49+
50+
Learn More: [GPO Configuration](/windows/win32/winrm/installation-and-configuration-for-windows-remote-management) [Intune CSP Documentation](/windows/client-management/mdm/policy-csp-remotemanagement)
51+
4452
### ANC Endpoint Access
4553

4654
During ANC configuration, the service needs to download configuration data from various Microsoft endpoints as listed in [Network requirements](/windows-365/enterprise/requirements-network). Failure to reach these endpoints due to misconfigured network settings can lead to a failure. To ensure successful access, Transport Layer Security (TLS) inspection should be avoided on any vNET used for ANC connections. Ensure that you can successfully resolve and reach these endpoints through the Azure vNet used and ensure that any firewall, proxy, or other Network services employed within the network allow access to them.

0 commit comments

Comments
 (0)