What Changed
Cisco Meraki solution v3.0.6 fixes a critical parser regression introduced in v3.0.5 where the CiscoMeraki parser function incorrectly referenced itself instead of the source table meraki_CL, causing infinite recursion and query failures.
Security Impact (Visibility & Fidelity)
Organizations running Cisco Meraki v3.0.5 have experienced a complete data visibility loss for Meraki network security events. The parser regression broke the CiscoMeraki function used by all downstream workbooks, hunting queries, and analytic rules — effectively creating a blind spot for Meraki firewall, wireless, and network infrastructure monitoring.
The issue occurred during the v3.0.5 packaging step where the parser query was incorrectly modified to reference CiscoMeraki (the parser function alias) instead of meraki_CL (the actual Log Analytics table populated by syslog ingestion). This caused the parser to recursively call itself, resulting in execution errors for any KQL using CiscoMeraki | …
The source YAML parser definition was never corrupted — only the packaged ARM template contained the broken references. Version 3.0.6 restores the correct meraki_CL table references and enables normal parser execution.
Per the support request ICM 2606010050004199, customers attempting to query Cisco Meraki data received recursion errors, breaking security monitoring for network infrastructure events.
Affected Files
(packaging artefacts: 3.0.6.zip, ReleaseNotes.md, Solution_CiscoMeraki.json, mainTemplate.json)