How to Unlink a Meraki Organization from a LogCentral Organization

Overview

Unlinking a Cisco Meraki organization from your LogCentral organization disconnects the integration at the organization level, affecting all locations that have linked Meraki networks. This action stops automatic log ingestion from all Meraki networks across your organization and removes the stored Meraki API credentials.

Understanding the difference between organization-level and location-level unlinking is important:

• Organization-level unlinking (this article): Disconnects the entire Meraki organization integration, affecting all locations
• Location-level unlinking: Disconnects individual Meraki networks from specific locations (see the Meraki Network Integration article)

When to Unlink at Organization Level

Common reasons for unlinking a Meraki organization include:

• Switching to a different Meraki organization
• Removing Meraki integration entirely from LogCentral
• Troubleshooting connection issues by reconnecting
• Revoking LogCentral’s access to your Meraki dashboard
• Organizational changes or security requirements

What Happens When You Unlink

When you disconnect a Meraki organization from LogCentral:

• API access is revoked: LogCentral loses authorization to access your Meraki dashboard
• All location-level links are affected: Every location with a linked Meraki network loses its connection
• Log ingestion stops: New logs from all Meraki networks stop flowing to LogCentral
• Existing logs remain: Historical logs already stored in LogCentral are preserved
• Network configurations are removed: Meraki organization and network selections are cleared

How to Unlink a Meraki Organization

Prerequisites

• Organization owner or member permissions in LogCentral
• Access to the Organization Integrations page

Unlinking Process

1. Navigate to the Organization Integrations page at /organizations/:orgId/integrations
2. Locate the Cisco Meraki integration card
3. Click the “Disconnect” button
4. Review the confirmation dialog explaining the effects
5. Confirm the disconnection

The integration will be immediately removed, and all linked Meraki networks across your locations will be disconnected.

Cascade Effects Across Locations

Unlinking at the organization level has widespread effects:

• Multiple locations impacted: All locations with linked Meraki networks lose their connections simultaneously
• Active log streams interrupted: Real-time log ingestion from all Meraki devices stops
• Monitoring affected: Any monitoring or alerts based on Meraki logs may be impacted
• No partial unlinking: You cannot keep some networks linked while unlinking others at the organization level

If you need to unlink only specific networks, use the location-level Meraki Network Integration page instead.

Re-linking After Disconnection

Unlinking is reversible. To reconnect:

1. Return to the Organization Integrations page
2. Click “Connect Meraki” to start the OAuth authorization flow
3. Authorize LogCentral to access your Meraki dashboard
4. Re-link individual networks at each location as needed

Note that you’ll need to manually re-link networks at the location level after reconnecting at the organization level.

Troubleshooting

Integration won’t disconnect: Verify you have owner or member permissions in the LogCentral organization.

Need to keep some networks connected: Use location-level unlinking on the Meraki Network Integration page instead of organization-level disconnection.

Logs still appearing after unlinking: Existing logs remain in LogCentral. Only new log ingestion is stopped.

Want to reconnect: Follow the standard Meraki connection process from the Organization Integrations page.

Related Resources

• Organization Integrations page: Manage all third-party integrations
• Meraki Network Integration page: Link/unlink individual networks at the location level
• Meraki Import page: Bulk import Meraki networks as locations (Enterprise feature)