Skip to main content

 

Cisco Meraki Documentation

Subscription - Licensing FAQs

This article contains answers to common Subscription Licensing questions, covering the following topics: license tiers, upgrades, switching from Co-Termination licensing, and multi-organization management.

Subscription Licensing overview

What is Subscription Licensing? 

Subscription Licensing is the latest licensing model from Cisco Meraki. It offers enhanced flexibility and simplicity in terms of payment methods, configurations, management, and scalability.  

 

Why are Subscription Licenses important? 

Subscription Licensing offers options for licensing that can better align with your business needs. Subscription Licensing also allows you to make licensing decisions at the network level. With Subscriptions, you can choose different feature tiers for branch offices and headquarters, allowing you the capability to deploy features where needed.

 

How many different product license tiers are there for Subscription Licensing? 

We have moved to a 2 level feature tier for simplicity. We have also simplified SKUs making them hardware agnostic. To learn more about the new SKU and feature tiers refer to the following documentation: 

 

Where can I learn more about Subscription Licensing? 

To learn more about Subscription Licensing, review the Subscription – Licensing Overview documentation. 

 

License upgrades

How do I request to add or upgrade licenses to an existing subscription, or request end date updates? 

Work with your Cisco Meraki partner to submit a change request. For more information, refer to documentation: Subscription - Licensing Changes Cloud Managed

 

If I request Subscription license additions or upgrades, do I need to claim a license key in the Meraki dashboard? 

Subscriptions that are updated will automatically update Meraki dashboard. There will be no requirement for any further claims throughout the lifespan of the subscriptions after the initial claim. 

 

Switch to Subscription Licensing

How do I switch from Co-Termination Licensing to Subscription Licensing?

Your Co-Termination Licenses must be expired before switching to Subscription Licensing. For more information, refer to documentation: Converting Meraki Co-Term Licensing to Subscription Licensing

 

Do I need to create a new organization to convert my legacy organization with expired licenses (Co-Term or PDL) to a Subscription Licensing organization? 

No, you do not need to create a new organization. If there are no active legacy licenses (Co-Term or PDL), you are eligible to use Subscription licenses in the same organization. Once you claim the Subscription license key, the dashboard recognizes the key and converts the organization to the Subscription Licensing model. 

 

Managing licenses on networks and organizations 

If I have multiple organizations, can I use the same Subscription Licensing for all my organizations?

No, Subscription Licensing supports one or more networks within the same organization. Therefore, you would need to purchase at least one subscription per organization. 

 

Can a single organization have two subscriptions with different feature tiers? 

Yes, you can have multiple subscriptions within the same organization, and each subscription can encompass different feature tiers. Additionally, a single subscription may contain licensing for multiple feature tiers. This flexibility enables you to tailor your licensing arrangements based on specific requirements and varying needs across different products.  

 

Do I need to reach out to Support to move a subscription license from one organization to another? 

Yes, a support request is required to move a subscription license between organizations. This will impact Networks bound to a subscription currently. The ability for you to self-serve and move a subscription will be a feature in a future release. 

 

How can I ensure my networks and organizations are meeting the new compliance logic? 

Every device that is deployed on any network of your organization has a license. For more information on compliance, refer to documentation: Subscription - License Compliance Cloud Experience.

 

  • Was this article helpful?