Zpa Create Server Group

zpa_list_app_connector_groups()```text
**Evaluate results:**
- If a suitable connector group already exists, note its `id` for use in Step 4- If no connector groups exist or none are suitable, proceed to Step 3- Present the list to the administrator and ask which to use (or confirm creating a new one)
#### Example Response
```textI found the following existing app connector groups:
1. **US-East Connectors** (ID: 72058304567890)   - Location: New York, US   - Enabled: Yes   - Connectors: 3
2. **EU-West Connectors** (ID: 72058304567891)   - Location: Dublin, IE   - Enabled: Yes   - Connectors: 2
Would you like to use one of these, or should I create a new app connector group?```text
---
### Step 3: Create App Connector Group (if needed)
If a new app connector group is required:
```textzpa_create_app_connector_group(  name="<connector_group_name>",  description="<description>",  enabled=True,  latitude="<latitude>",  longitude="<longitude>",  location="<location_name>",  city_country="<city>, <country>",  country_code="<ISO_country_code>")```text
**Important notes:**
- `country_code` accepts full names (e.g., "United States") or ISO codes ("US")- `latitude` and `longitude` help with geo-proximity routing- Save the returned `id` -- it is required in the next step
#### Confirm creation
```textzpa_get_app_connector_group(group_id="<returned_id>")```text
---
### Step 4: Create the Server Group
With the app connector group ID(s) in hand, create the server group:
```textzpa_create_server_group(  name="<server_group_name>",  app_connector_group_ids=["<connector_group_id>"],  description="<description>",  enabled=True,  ip_anchored=False,  dynamic_discovery=True)```text
**Parameter guidance:**
- `app_connector_group_ids` (required): List of one or more app connector group IDs from Step 2 or Step 3- `dynamic_discovery`: Set to `True` when application servers are discovered automatically; `False` when specifying servers manually via `server_ids`- `ip_anchored`: Set to `True` only when source IP anchoring is required (advanced use case)
---
### Step 5: Verify and Summarize
Confirm the server group was created successfully:
```textzpa_get_server_group(group_id="<returned_server_group_id>")```text
#### Present Summary
```textServer group created successfully.
**Server Group:**- Name: <name>- ID: <id>- Enabled: Yes- Dynamic Discovery: Yes/No- IP Anchored: Yes/No
**Associated App Connector Group(s):**- <connector_group_name> (ID: <connector_group_id>)
**Next Steps:**- You can now reference this server group (ID: <id>) when creating  application segments using `zpa_create_application_segment`- To create a complete application, see the "application_segment-onboard" skill```text
---
## Dependency Chain Reference
```textApp Connector Group (no dependencies)        │        ▼   Server Group (requires app_connector_group_ids)        │        ▼Application Segment (requires segment_group_id, optionally server_group_ids)        │        ▼ Access Policy Rule (references application segments, groups, users)```text
---
## Edge Cases
### Multiple Connector Groups
A server group can reference multiple app connector groups for redundancy:
```textzpa_create_server_group(  name="Multi-Region Servers",  app_connector_group_ids=["<us_east_id>", "<eu_west_id>"],  dynamic_discovery=True)```text
### Microtenant Scoping
In multi-tenant environments, pass `microtenant_id` to both the connector group and server group:
```textzpa_create_app_connector_group(  name="Tenant-A Connectors",  microtenant_id="<tenant_id>",  ...)
zpa_create_server_group(  name="Tenant-A Servers",  app_connector_group_ids=["<id>"],  microtenant_id="<tenant_id>")```text
### Static Server Assignment
When dynamic discovery is disabled, associate specific application servers:
```textzpa_list_application_servers()
zpa_create_server_group(  name="Static Servers",  app_connector_group_ids=["<connector_group_id>"],  server_ids=["<server_id_1>", "<server_id_2>"],  dynamic_discovery=False)```text
---
## Quick Reference
**Dependency:** App Connector Group must exist before creating a Server Group.
**Tools used:**
- `zpa_list_app_connector_groups()` -- find existing connector groups- `zpa_create_app_connector_group(name, ...)` -- create if needed- `zpa_get_app_connector_group(group_id)` -- verify connector group- `zpa_create_server_group(name, app_connector_group_ids, ...)` -- create server group- `zpa_get_server_group(group_id)` -- verify server group
**Remember:**
- Always check for existing resources before creating new ones- The `app_connector_group_ids` parameter on server groups is required- Present the dependency chain to the administrator so they understand the relationship