Subscription licensing is the model Re-solution recommends for nearly every new or renewing Cisco Meraki customer. Meraki licensing explained simply: there are three models on the table, and only one of them fits how modern IT teams actually procure and manage hardware.
- Subscription — licences bind to individual networks, hardware is agnostic to SKU, and lapses trigger Amber Mode instead of an outage.
- Co-Termination (Co-Term) — every device in the organisation shares one expiry date, recalculated as a weighted average whenever you add licences.
- Per-Device Licensing (PDL) — a legacy model tied to hardware serial numbers, closed to new customers.
Claiming a subscription key is a one-way move. Once you’re on Subscription, you cannot revert to Co-Term or to PDL.
Key Takeaways
Subscription licensing is the recommended default for most Meraki estates because it pairs network-level flexibility with Amber Mode continuity that Co-Term and PDL cannot match.
| Point | Details |
|---|---|
| Subscription is the default | New and renewing customers should start with Subscription unless a specific legacy constraint applies. |
| Amber Mode protects continuity | Lapsed subscriptions keep passing traffic instead of dropping offline, unlike Co-Term or PDL. |
| Co-Term expiry is dynamic | The shared organisation expiry recalculates as a weighted average whenever licences are added. |
| PDL is closed to new customers | Per-Device Licensing is legacy only, with no supported path to convert into it. |
| Migration is one-way | Claiming a subscription key is permanent, so audit legacy inventory before committing. |
| Re-solution supports the transition | Re-solution runs licensing audits and staged migration planning for organisations moving to Subscription. |
Table of Contents
- Meraki subscription licensing explained: binding, Amber Mode and billing
- How does Co-Term licensing calculate its expiry date?
- Why is Per-Device licensing considered legacy now?
- Meraki licensing comparison: compliance, expiry and flexibility
- How do you choose the right Meraki licensing model?
- Claiming and binding subscription licences: what to expect
- What we’ve seen work in real Meraki migrations
- Get help auditing or migrating your Meraki licences
- Essential Meraki documentation and next steps
- Sources
- FAQ
Meraki subscription licensing explained: binding, Amber Mode and billing
Subscription licensing attaches to a specific network rather than the whole organisation. That distinction matters the moment you run more than one site: each network binds to its own subscription, so a warehouse and a head office can sit on different tiers without cross-contaminating renewal dates. A network can only be bound to one subscription at a time, though an organisation can bind multiple networks to the same subscription where it makes sense to consolidate.
The standout operational feature is Amber Mode. If a subscription lapses, covered networks keep passing traffic instead of dropping offline, while devices outside the licensed scope are flagged for compliance. For any organisation where downtime means lost revenue or safety risk, that grace period changes the calculus entirely.
Subscription SKUs are also hardware agnostic, covering multiple devices within a model family rather than being tied to individual serial numbers. Hardware refreshes stop being a licensing headache.
- Term lengths run for extended periods, with options for periodic or prepaid billing.
- Renewals can be automatic or manual, and terms can be adjusted mid-contract.
- Some product families (MR and MX, for instance) support tiered options such as Essential and Advantage under subscription.
Availability varies by region and product line, so confirm your SKU’s subscription status before budgeting a migration.
Pro Tip: Bind your highest-risk network to subscription first. If Amber Mode behaves as expected during a real renewal cycle, you’ve validated the model before touching the rest of the estate.
How does Co-Term licensing calculate its expiry date?
Co-Term licensing keeps every device in the organisation on a single, unified expiry date. That date isn’t fixed at purchase. It’s dynamically recalculated as a weighted average whenever you claim new licences or add hardware, pulling the shared end date forward or back depending on volume.
- Predictable: one renewal date for the whole organisation simplifies budgeting cycles.
- Prepaid only: there’s no flexible billing option, and no equivalent to Amber Mode if the licence pool lapses.
- Growth-sensitive: adding a large batch of new devices can shift the org-wide expiry date more than teams expect.
Co-Term still suits organisations with a stable, slow-changing estate and a preference for a single annual renewal conversation rather than per-network tracking.
Why is Per-Device licensing considered legacy now?
Per-Device Licensing ties each licence to an individual hardware serial number, so every refresh or swap means reissuing licences device by device. That’s manageable at small scale and painful at any real growth rate.
PDL is no longer available to new customers in regions where subscription exists, and conversions into PDL from another model are unsupported. Organisations can move away from PDL, but never back.
- Still relevant if you’re running legacy estate inventory acquired before the cutover.
- Worth mapping before any hardware refresh, since PDL-locked devices need separate handling.
Meraki licensing comparison: compliance, expiry and flexibility
Set side by side, the three models diverge sharply on what happens when things go wrong and how much SKU flexibility you get day to day.
- Compliance on lapse: Subscription keeps traffic flowing via Amber Mode; Co-Term risks losing dashboard management and enforcement; PDL can trigger a harder stop at the device level.
- Expiry semantics: Subscription expiry is fixed per network subscription; Co-Term uses a dynamic, weighted-average organisation date; PDL expiry sits per individual device licence.
- SKU flexibility: Subscription supports tiered options (Essential/Advantage) within several product families; Co-Term and PDL rely on older, more rigid model-specific licensing.
- Upgrade paths: moving from Co-Term or PDL into Subscription is permanent. There’s no supported route back once a subscription key is claimed.
For estates with mixed device families across several sites, the SKU tiering under subscription tends to matter as much as the compliance behaviour. It removes the need to track which exact hardware model a licence was purchased against.
How do you choose the right Meraki licensing model?
Decision criteria worth weighing before you commit:
- Organisational scale and site count. A single site with stable hardware may tolerate Co-Term; distributed, multi-site estates benefit from Subscription’s per-network binding.
- Procurement cadence. If your finance team prefers periodic billing over one large prepaid outlay, Subscription’s flexible terms fit better.
- Risk tolerance for lapses. Organisations where downtime is costly should weight Amber Mode heavily.
- Appetite for SKU simplicity. Frequent hardware refreshes favour subscription’s hardware-agnostic model.
Run this checklist before changing anything:
- Audit current licences across every network and organisation.
- Map existing expiry dates, particularly for Co-Term’s shared date.
- Identify any PDL-locked devices that still need serial-based handling.
- Forecast growth and hardware refresh cycles for the next 36 to 84 months.
- Loop in procurement early. Since claiming a subscription is permanent, retiring unused legacy inventory first avoids paying for term exposure you don’t need.
Pro Tip: Don’t run this checklist in isolation from your renewal calendar. A licence audit two months before a Co-Term expiry date gives you room to negotiate; running it the week before doesn’t.
Claiming and binding subscription licences: what to expect
Claiming a subscription licence key only works under specific organisation states. It must be an expired organisation, one in a grace period, or a newly created organisation — active legacy licences block the claim outright.
- Confirm the organisation isn’t mid-term on an active legacy licence.
- Claim the subscription licence key into the organisation.
- Bind the subscription to the relevant network or networks.
- Verify device coverage across that network before decommissioning any old licence pool.
The most common pitfalls: active trials still running in the organisation, or an existing legacy model that hasn’t fully expired. You’ll also need organisation-level administrative permissions to complete the claim. If your estate spans multiple distributed sites, it’s worth escalating to your Meraki partner before you touch a production organisation.
What we’ve seen work in real Meraki migrations
As a Cisco partner working across education, manufacturing and logistics estates, Re-solution has watched the same pattern repeat: clients who move to subscription see fewer procurement errors and noticeably smoother hardware upgrades, because SKUs stop being tied to specific serials. For large, distributed estates, a staged migration, one pilot network first, remains the safer route.
— Jacob
Get help auditing or migrating your Meraki licences
Deciding between Subscription, Co-Term and PDL is only half the job. Executing the migration without a renewal date slipping through the cracks or a subscription key claimed into the wrong organisation is where most in-house teams lose time. Re-solution runs licensing audits and migration planning for organisations moving off Co-Term or legacy PDL, and manages Meraki estates on an ongoing basis through Network as a Service.
If you’re carrying a mixed estate with expiry dates you can’t easily forecast, or PDL inventory nobody’s mapped in years, Re-solution’s managed IT services team can run the audit first and hand you a clear picture before you claim anything. Get in touch to request a licensing audit and a migration plan tailored to your site count and renewal calendar.
Essential Meraki documentation and next steps
Consult the Meraki licensing overview and subscription licensing details directly, or contact Re-solution for an audit tailored to your estate.
FAQ
What are the recent changes in Meraki licensing?
Cisco has shifted its default model toward Subscription licensing, which is network-bound, hardware agnostic, and includes Amber Mode. Co-Term and PDL still exist for existing customers, but PDL is no longer available to new customers.
What does Meraki MX subscription licensing include?
MX subscription licences bind to a specific network, support tiered options in several product families, and offer term lengths from 36 to 84 months with flexible or prepaid billing.
How much does Meraki licensing cost?
Cost varies by tier, term length and product family, since Subscription offers multiple tiers such as Essential and Advantage on certain lines. Speak to a Meraki partner like Re-solution for a quote scoped to your estate.
What’s the difference between Meraki Co-Term and Subscription licences?
Co-Term uses one organisation-wide expiry date calculated as a weighted average, with no Amber Mode if it lapses. Subscription licences bind per network, offer flexible billing, and keep traffic flowing during a lapse via Amber Mode.
Can I switch from Per-Device licensing back after moving to Subscription?
No. Moving from PDL or Co-Term into Subscription is permanent, and reverting to a legacy model is not supported.
Recommended
- Simplify Wi-Fi with Cisco Meraki Go | Re-Solutio
- Meraki Access Control vs Cisco ISE | Re-Solution Experts
- SASE & Meraki | Cisco Cloud, Security & Datacenter Experts
- Manufacturing | Cisco Cloud, Security & Datacenter Experts
