Skip to content

Organization Creation Configuration

Dashboard Location: Global Overview > Add Organization

Meraki Organization Creation and Management

Section titled “Meraki Organization Creation and Management”

Organization creation in Meraki provides administrators with comprehensive multi-tenant management capabilities, enabling hierarchical network infrastructure organization, centralized policy management, role-based access control, and scalable enterprise network deployment. This functionality supports distributed enterprise architectures, managed service provider (MSP) operations, multi-site network management, centralized security policies, and administrative delegation across geographically dispersed locations. Organization management is essential for enterprise scalability, operational efficiency, compliance governance, cost allocation, and maintaining consistent network policies while supporting independent administrative domains and customizable network hierarchies.

This resource also has the ability to manage the complete organization by creating a new instance or unmange the organization.

If unmanaged then terraform will import the existing organization.

Diagram
NameTypeConstraintMandatoryDefault Value
nameStringmin: 1, max: 127No
managedBooleantrue, falseNotrue

Example-1: The example below demonstrates basic organization creation.

This configuration establishes the foundational organizational structure for managing networks and devices within the Meraki cloud platform. The example creating the organization that is defined with “org_name” enviromental variable.

The example also demonstrates how to manage pre existing organisations. With the ‘managed’ set to ‘false’ we can allow terraform to import the existing organization whilst still being able to maintain and manage other attributes within the organization.

Naturally if this key is set to ‘true’ then terraform will create this organization.

meraki:
domains:
- name: !env domain
administrator:
name: !env org_admin
organizations:
- name: !env org
managed: false