Skip to content

Networking and Firewall validation ​

Select option 3 from the Beacon menu for a focused network and firewall validation. Use option 9 first to set the region, a proxy or an Arc gateway.

What it covers ​

Everything except the AD port tests (Category 3). Good for:

  • verifying firewall policy before any identity configuration
  • checking endpoint reachability from the management VLAN, through a proxy or an Arc gateway
  • confirming DNS, NTP and the public-address and HTTPS-inspection conditions Learn calls out

What you are prompted for ​

InputExampleRequired
Management gateway IP192.0.2.1Optional (taken from the network bootstrap when known)
DNS server IP(s)192.0.2.10Optional

Settings (option 9): region, proxy URL and bypass list, Arc gateway FQDN, OEM list (dell), NTP servers.

Tests run ​

CategoryTests
1 - Network and timeNIC, IP, gateway ping, NTP and clock offset
2 - DNSDNS TCP/UDP 53, forward resolution of key Azure endpoints
4 - Endpoint sweepThe region's Azure Local, Arc, ARB, AKS endpoints (plus OEM); PublicIP- and TlsInspection- checks
5 - Environment CheckerConnectivity validator (region, proxy and Arc gateway aware); Network validator when its inputs exist
6 - ArcOptional

Proxy and Arc gateway ​

SettingEffect
proxyUrlEndpoint rows are probed through the proxy with CONNECT; the proxy is TCP-checked; the TLS-inspection read goes through it too; passed to the Environment Checker
proxyBypassHosts that go direct: host, *.domain, .domain, 10.0.0.0/8, <local>
arcGatewayFqdnArc gateway mode: rows with gateway support are skipped (the gateway carries them); the gateway endpoint is probed; passed as -ARCGateway to the Environment Checker

Firewall requirements ​

See Endpoint list for the per-region counts and how each row is probed.

Microsoft documentation ​

Released under the MIT License.