Carefully determining a Dashboard organizational structure for your managed service customers is important, as there are several meaningful consequences for each type of structure. There are two common scenarios for a Meraki partner offering managed services, and the type of solution or service being offered can help determine the recommended organizational structure:
Sell-Through Managed Service |
Sell-To Managed Service (i.e. Network-as-a-Service) |
|---|---|
Any service offered by a partner that shares control of customer-owned Meraki equipment and manages the network and IT. Characteristics
|
Any service offered by a partner organization that provides IT and network connectivity as a service, and typically includes the hardware. Characteristics
|
Figure 1: Organization per customer (one-to-one)
Figure 2: Network as a Service Structure (many-to-one)
It is also possible to have a hybrid structure -- where certain customers have their own organization, while all others are grouped into a single organization (a combination of Figure 1 and Figure 2). An MSP may choose this hybrid structure, for example, in cases where only a small subset of customers have more customized service requirements, or leverage SD-WAN services (e.g., Auto-VPN). Additional details are available via product documentation: Meraki Dashboard Organization Structure
- To receive notifications for new content, go to the Options menu (above) and select Subscribe.
- If you find a resource helpful, give it kudos! (The little green arrow below each post:
) - Please ask any general MSP-related questions in the MSP forum.
