Deployment Monitoring
DOCUMENT CATEGORY: Reference SCOPE: Phase 05 cluster deployment and validation monitoring PURPOSE: Real-time dashboard visibility into Azure Local cluster deployment MASTER REFERENCE: Microsoft Learn — Deploy via Portal
Status: Active Last Updated: 2026-03-09
Overview
Phase 05 cluster deployment runs in two sequential phases — validation (~15 minutes) then deployment (~2–3 hours). Both phases run silently in the background from Azure's perspective; the portal only updates periodically. These monitoring scripts provide a real-time ANSI dashboard that combines:
- Azure API polling — live step status from
deploymentSettings/default - Remote log streaming — live tail of
EnvironmentValidatorFullorOrchestratorFulllogs from cluster nodes via PSRemoting
Both scripts are auth-method-agnostic — they work identically for Active Directory and Local Identity deployments.
When to Run Each Script
| Phase | Script | When to Start | When It Stops |
|---|---|---|---|
| Task 9: Validation | Monitor Validation | After clicking Start validation in the portal | Auto-exits on validation success or failure |
| Task 10: Deployment | Monitor Deployment | After clicking Create in the portal | Run until deployment completes (~2–3 hours) |
Both scripts run from any machine with network access to the cluster node management IPs and an active Azure authentication context. They do not need to run from a cluster node or the management server used for toolkit scripts.
Prerequisites
| Requirement | Details |
|---|---|
| PowerShell 7+ | $PSVersionTable.PSVersion — must be 7.x |
| Az PowerShell module | Install-Module Az -Scope CurrentUser |
| Azure CLI | az --version — required for ARM API calls |
| Azure authenticated | Connect-AzAccount or existing SPN context |
| Network access | PSRemoting (TCP 5985/5986) to cluster node management IPs |
| Local admin credentials | Identical credentials used during deployment |
Script Locations
| Script | Toolkit Path |
|---|---|
| Monitor-Validation.ps1 | scripts/deploy/04-cluster-deployment/phase-05-cluster-deployment/monitoring/powershell/Monitor-Validation.ps1 |
| Monitor-Deployment.ps1 | scripts/deploy/04-cluster-deployment/phase-05-cluster-deployment/monitoring/powershell/Monitor-Deployment.ps1 |
Credential Resolution
Both scripts resolve credentials in the same priority order:
1. Direct params: -LocalAdminUsername + -LocalAdminPassword
↓ (if not provided)
2. Azure Key Vault: -KeyVaultName with -LocalAdminUsernameSecretName / -LocalAdminPasswordSecretName
↓ (if KV unavailable or not configured)
3. Interactive: Read-Host prompt at startup
Azure authentication (for API access) follows the same pattern with SPN credentials:
1. -SPNClientId + -SPNClientSecret params
↓
2. Key Vault: -SPNClientIdSecretName / -SPNClientSecretSecretName
↓
3. Existing Connect-AzAccount context
Version Control
- Created: 2026-03-09 by Azure Local Cloudnology Team
- Last Updated: 2026-03-09 by Azure Local Cloudnology Team
- Version: 1.0.0
- Tags: azure-local, monitoring, deployment, validation, runbook