Cisco Meraki

Corma puts Cisco Meraki licensing costs next to your SaaS contracts: co-termination dates, renewals per site and the admins who can change licensing.

The Corma and Cisco Meraki cost integration puts your Meraki licensing next to your SaaS contracts in Corma, so IT and finance can see when the next renewal falls, what it covers, how it splits across sites, and who can change licensing in the Meraki dashboard. Cisco Meraki devices, from wireless access points to switches and security appliances, rely on the Meraki cloud for centralized management, and the organization needs valid licences to keep them in service.

Key takeaways

Under Meraki co-termination licensing, every device in an organization shares one expiration date, recalculated each time licences are added.
When a Meraki co-termination organization runs out of licences, a 30-day grace period applies before devices stop passing client traffic.
Corma brings Meraki renewal dates and spend next to your SaaS contracts, so network renewals are budgeted with the rest of the IT stack.

How do Meraki licensing models shape the bill?

Meraki uses three licensing models. Co-termination gives the whole organization a single expiration date, calculated by averaging all active licences across its devices. Per-device licensing gives each device its own term and is no longer available to new customers. Subscription licensing ties licences to networks, with terms from 12 to 84 months. Co-termination licences are prepaid, for terms of 1, 3, 5 or 7 years.

Each model moves costs differently. With co-termination, adding licences shifts the shared date, while removing devices does not move it, so a closed branch does not change your renewal. With subscriptions, renewals follow each network. Either way, the renewal is a large, infrequent invoice that a SaaS budget built month by month easily misses.

How Corma manages Meraki costs

Renewals in one calendar: Meraki expiration and subscription end dates sit with your SaaS contracts in Corma SaaS management, with forecasts of upcoming spend.
Invoices matched to contracts: Corma's invoice and contract scanner matches Meraki invoices to the right supplier and contract.
Spend per site or entity: chargebacks allocate Meraki costs to each office or subsidiary, which helps finance teams plan network budgets.
Who can change licensing: in Meraki, network administrators do not see licensing information, while organization administrators have full access to the organization. Corma puts organization administrators into access review campaigns.

Licence coverage per device is detailed on the Cisco Meraki licence management page, and dashboard access on the Cisco Meraki access management page.

Frequently asked questions

Why did our Meraki co-termination date change?

Because adding licences recalculates the shared expiration date of the organization. Removing devices does not change it, so the date only moves when licences are added.

What happens if a Meraki renewal is paid late?

Under co-termination, an organization out of compliance has a 30-day grace period, after which devices cease to pass client traffic while still passing management traffic. Under subscription licensing, devices keep forwarding traffic, but management of the non-compliant devices or networks is disabled once the grace period ends.