A startup with no on-premises monitoring platform wants vendor-hosted dashboards for its brand-new appliance - nothing to install locally. The team enables the cloud monitoring option in the management interface, yet the next morning the hosted portal still shows no telemetry for the system. Which prerequisite step most likely explains the gap?

Vendor-cloud monitoring for these appliances is not a standalone feature you simply switch on - it is a service layered on top of the support infrastructure. The system must hold a support registration with an entitlement, and it must reach the vendor cloud over an outbound path, proxy or direct, with the required destinations reachable, so periodic metrics can flow up. Only after registration and connectivity are in place does enabling the monitoring option produce a populated portal view. 'It pings, so it should report' mistakes reachability for enrollment: an appliance that answers ICMP but holds no registration and no cloud route streams nothing. Restarting management services is a troubleshooting reflex, not a prerequisite - a restart cannot manufacture the entitlement or open the firewall path the service depends on. Inbound polling ports invert the actual design: telemetry is pushed from the appliance over outbound connections, and opening inbound holes both misunderstands the flow and adds attack surface for a service that never needed them. Exam caveat: registration and connectivity are post-deployment configuration, so a freshly installed system that looks perfectly healthy locally can still be invisible in the portal - check both ends of the chain. Operational check: after configuring support connectivity and registration, confirm the system appears in the portal with a current timestamp on its capacity metrics before declaring success.