Onboard Meraki MX to Security Cloud Control

For information about connecting Security Cloud Control to your managed devices, refer to Allow inbound access for direct cloud connectivity.

For information about how Security Cloud Control communicates with Meraki, refer to How Does Security Cloud Control Communicate With Meraki.

You must first register the Meraki MX in the Meraki dashboard. Without access to the Meraki dashboard, your organization will not be recognized by the Meraki cloud. As a result, you will not be able to generate an API token to onboard your device.

Security Cloud Control converts invalid CIDR prefix notation IP addresses and IP address ranges to valid form by setting all bits associated with the host to zero.

Onboarding Meraki MX devices or templates no longer requires a connection through a Secure Device Connector (SDC). If you have Meraki MX devices that were previously onboarded and connect to Security Cloud Control using an SDC, their connection will continue to work. If you remove and re-onboard the device or update its connection credentials, the connection will stop working.

MX devices do not need to be connected to the Meraki cloud to be managed by Security Cloud Control. If an MX device has never connected to the cloud, the device connectivity is listed as unreachable. This status is normal and does not affect your ability to manage the device or deploy policies to the device.