Settings file (group_vars/all/main.yml)

main.yml is the heart of a client deployment. It holds the global settings every module shares — region, naming, tagging, the administrator identity and the internal domain — and it turns individual modules on or off. Together with Users and access (files/users.csv) it is the only file you edit; everything the collections build is rendered from these two.

The file opens with a small fixed block that must be left exactly as it is — these paths are assumed throughout the roles:

# BEGIN Do not change the values below
linux_temp_path: /opt/maintenance
windows_temp_path: C:\MAINTENANCE
mountpoint: /opt
# END Do not change the values

Global settings

These apply to the whole deployment and feed Azure resource naming, tagging, and the jumphost / VM administration identity.

Key

Purpose

owner

Email of the person to contact about the Azure resources (also tagged onto them).

team

Team code used in resource names and tags (for example be1).

az_env

Environment code for names/tags: p prod, d dev, t training, e demo.

env_name

Short name of this environment (for example dfir); part of every resource name.

az_location

Azure region for the deployment (for example westeurope).

subscription_id / tenant_id

Target Azure subscription and tenant (GUIDs).

engagement_code

Engagement / billing code tagged onto the resources.

admin_user

Local administrator username created on the deployed VMs.

admin_ssh_key

SSH public key installed on the jumphost and for VM administration.

internal_domain

Internal DNS domain for the environment (for example dfir.lab).

timezone

Timezone applied to every server (for example Europe/Brussels).

Enabling modules

Each module is a services_* key (or a module-specific key from asc.ap / asc.dfir / asc.xhack). Set enabled: true and supply the module’s options underneath; omit the key, or set enabled: false, to skip it.

services_guacamole:
  enabled: true
  vm_size: Standard_B2as_v2
  vm_name: vmguacamole01
  enable_aad_auth: true          # Entra sign-in; needs rights to create an app registration
  admins:
    - ada.lovelace@example.com

services_elastic:
  enabled: true
  vm_name: elastic
  vm_size: Standard_D2s_v3
  vm_disk_size: 128

Every option a module accepts, with its default, is listed on that module’s role page under the Collections index — the role page is the authoritative reference. asc.core provides the shared services (Guacamole, Elastic, file share, Ghostwriter, Mail, OpenVPN, Vault, Neo4j and Azure AI Foundry); the asc.ap, asc.dfir and asc.xhack collections add their module-specific roles on top.

Azure AI Foundry needs a little more setup around choosing models and capping spend, so it has its own page: Azure AI Foundry.

Networking

Virtual networks are declared under common_vnets_config and connected under common_vnets_peering. A shared services vnet carries the common infrastructure (management, monitoring, email, access and tools subnets); each module gets its own vnet with a distinct address space so ap, dfir and xhack can be deployed side by side without overlap.

common_vnets_config:
  services:
    address_space: 10.255.0.0/20
    subnets:
      mgmt:
        address_space: 10.255.1.0/24
      monitoring:
        address_space: 10.255.0.0/24
      access:
        address_space: 10.255.3.0/24
  dfir:
    address_space: 10.17.0.0/16
    subnets:
      vms:
        address_space: 10.17.10.0/24

common_vnets_peering:
  - primary: services
    secondary: dfir

Each peering entry links two vnets so resources in one can reach the other. Add a peering for every module vnet that must reach the shared services vnet, plus any module-to-module links your design needs (for example dfir ↔ dfirservices). The peerings and the per-module NSGs are generated from this configuration — you do not write them by hand.