Skip to main content

Task 05: Monitor Apply Stage

Objective: Monitor Terraform apply stage as Azure resources are deployed Duration: 45-90 minutes (management mode), 10-15 minutes (cluster mode)

DOCUMENT CATEGORY: Runbook SCOPE: Monitor infrastructure deployment during apply stage PURPOSE: Monitor infrastructure deployment during apply stage MASTER REFERENCE: Terraform Apply Documentation

Status: Active

What Happens​

The apply stage:

  1. Executes Terraform plan
  2. Creates Azure resources in dependency order
  3. Waits for long-running resources (VPN Gateway: 30-45 min)
  4. Configures all resources
  5. Outputs deployment information

Monitoring Procedure​

1. Watch Apply Job​

Click the apply job in the pipeline to see real-time logs.

2. Track Resource Creation​

Resources deploy in this order:

Phase 1: Foundation (5-10 min)

azurerm_resource_group.management: Creating...
azurerm_virtual_network.hub: Creating...
azurerm_subnet.gateway: Creating...
azurerm_subnet.bastion: Creating...
azurerm_log_analytics_workspace: Creating...

Phase 2: VPN Gateway (30-45 min) ⏰

azurerm_public_ip.vpn_gateway: Creating...
azurerm_virtual_network_gateway.vpn: Creating...
(This will take 30-45 minutes - DO NOT INTERRUPT)
azurerm_virtual_network_gateway.vpn: Still creating... [5m0s elapsed]
azurerm_virtual_network_gateway.vpn: Still creating... [10m0s elapsed]
...
azurerm_virtual_network_gateway.vpn: Still creating... [40m0s elapsed]
azurerm_virtual_network_gateway.vpn: Creation complete after 42m15s

Phase 3: Remaining Resources (10-15 min)

azurerm_bastion_host: Creating...
azurerm_key_vault: Creating...
azurerm_storage_account: Creating...
azurerm_private_dns_zone: Creating...

3. Expected Timing​

ComponentTime
Resource groups, VNet, subnets5-10 min
VPN Gateway30-45 min
Bastion, Key Vault, Log Analytics10-15 min
DNS, storage, remaining resources5-10 min
Total (Management Mode)45-90 min
Total (Cluster Mode)10-15 min

Progress Indicators​

Healthy Deployment​

Apply complete! Resources: 45 added, 0 changed, 0 destroyed.

Outputs:

vpn_gateway_id = "/subscriptions/.../virtualNetworkGateways/..."
key_vault_id = "/subscriptions/.../vaults/..."
bastion_id = "/subscriptions/.../bastionHosts/..."

Warning Signs​

Stuck resources:

azurerm_resource.name: Still creating... [60m0s elapsed]

If any resource (except VPN Gateway) is stuck beyond expected time, investigate in Azure Portal.

Errors:

Error: creating Resource: authorization failed
Error: Code="QuotaExceeded"

Pipeline will fail with error details. See Troubleshooting section.


During Deployment​

✅ DO:

  • Monitor pipeline logs
  • Check Azure Portal for resource creation
  • Keep stakeholders updated on progress
  • Prepare for validation steps

❌ DON'T:

  • Cancel the pipeline
  • Modify resources in Azure Portal
  • Push new commits (starts new pipeline)
  • Make configuration changes

Common Issues​

Issue: Quota exceeded errors Solution: Request quota increase for the subscription

Issue: VPN Gateway taking longer than 45 minutes Solution: Check Azure Portal for actual status; may take up to 60 minutes in some regions

Issue: Bastion creation fails Solution: Verify /26 subnet size and AzureBastionSubnet name

Issue: Key Vault name conflict Solution: Key Vault names must be globally unique; module generates unique names


Validation​

  • Apply stage completed successfully
  • All resources created without errors
  • Output values displayed
  • No warning or error messages in final summary


When to use: Use this tab if your CI/CD pipeline runs on GitHub Actions.

See procedure steps above for GitHub-specific guidance.

Toolkit Reference

Scripts for this task are located in the azurelocal-toolkit repository under scripts/deploy/ in the appropriate task folder.


Alternatives​

The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.

PreviousUpNext
Task 04 - ApprovePhase 02 - ExecutionTask 06 - Test Stage

Values from infrastructure.yml​

The pipeline settings are in the devops section of infrastructure.yml (schema 5): the platform, the project, the repository, the approval environments, the runners and the Terraform state. The Terraform code does not define these values a second time. config/variables/scripts/New-IacVariableFiles.ps1 writes terraform.tfvars.json and backend.hcl from the file. See the variables reference.


Troubleshooting​

IssueCauseResolution
Apply stage failsResource provisioning errors or quota limitsCheck Azure quota and resource provider status
Partial deploymentTransient Azure API errors during applyRe-run the pipeline to retry failed resources

Version Control​

VersionDateAuthorChanges
1.0.02026-03-24Azure Local CloudInitial release