Task 04: Validation Sign-Off

DOCUMENT CATEGORY: Runbook
SCOPE: Validation documentation and sign-off
PURPOSE: Document validation results and obtain approval to proceed
MASTER REFERENCE: Azure Local Cloud Deployment Standards

Status: Active Estimated Time: 30 minutes

Overview

Complete the Phase 02 validation sign-off by documenting all validation results, collecting artifacts, and obtaining approval to proceed with site network configuration.

Deliverable

This sign-off document becomes a permanent project artifact and provides audit trail for deployment readiness.

---

Validation Sign-Off Template

Copy and complete this template for project documentation:

# Phase 09: Enterprise Network Readiness Validation Sign-Off

## Deployment Information

| Field | Value |
|-------|-------|
| **Site Name** | [Customer Site Name] |
| **Site Code** | [SITE_CODE] |
| **Validation Date** | [YYYY-MM-DD] |
| **Validated By** | [Engineer Name] |
| **Validation Workstation** | [IP Address / Hostname] |

---

## Validation Results Summary

### Task 1: Visual Hardware Inspection

| Check | Status | Notes |
|-------|--------|-------|
| Servers racked and powered | ☐ PASS / ☐ FAIL | |
| Network cabling complete | ☐ PASS / ☐ FAIL | |
| OpenGear installed | ☐ PASS / ☐ FAIL | |
| TOR switches installed | ☐ PASS / ☐ FAIL | |

**Step 1 Status**: ☐ PASS / ☐ FAIL

---

### Task 2: Customer Network Service Verification

| Service | Status | Notes |
|---------|--------|-------|
| DNS - AD Domain Controllers | ☐ PASS / ☐ FAIL | |
| DNS - Planned Node FQDNs | ☐ PASS / ☐ N/A | Optional - may be created later |
| NTP - Time Synchronization | ☐ PASS / ☐ FAIL | |
| Ping - OpenGear Console | ☐ PASS / ☐ FAIL | |
| Ping - Default Gateway | ☐ PASS / ☐ FAIL | |

**Step 2 Status**: ☐ PASS / ☐ FAIL

---

### Task 3: OpenGear Lighthouse Verification

| Check | Status | Notes |
|-------|--------|-------|
| Node visible in Lighthouse | ☐ PASS / ☐ FAIL | |
| Node status Online | ☐ PASS / ☐ FAIL | |
| Serial ports configured | ☐ PASS / ☐ FAIL | |
| Console access working | ☐ PASS / ☐ FAIL | |
| iDRAC connectivity | ☐ PASS / ☐ FAIL | |

**Step 3 Status**: ☐ PASS / ☐ FAIL

---

## Overall Assessment

| Overall Status | ☐ READY TO PROCEED / ☐ BLOCKED |
|----------------|--------------------------------|

### Blocking Issues (if any)

| Issue | Severity | Owner | Resolution ETA |
|-------|----------|-------|----------------|
| | | | |

---

## Approval

| Role | Name | Date | Signature |
|------|------|------|-----------|
| Azure Local Cloud Engineer | | | |
| Customer Network Contact | | | |
| Project Manager | | | |

---

## Artifacts Collected

- [ ] Hardware inspection checklist (completed)
- [ ] Network service test output
- [ ] Network service test notes
- [ ] Lighthouse screenshot (node online)
- [ ] This signed sign-off document

Rapid Sign-Off Checklist

Use this for expedited deployments where full documentation is gathered post-deployment:

Phase 02 Step	Status	Engineer Initials
Task 1: Hardware Inspection	☐ PASS
Task 2: Customer Network Services	☐ PASS
Task 3: OpenGear Verification	☐ PASS

Overall: ☐ READY TO PROCEED

Validated By: _________________ Date: _________

warning

Full sign-off documentation must be completed within 48 hours of deployment completion.

---

Artifact Collection

Collect All Validation Artifacts

# Define paths
$ProjectName = "AZL-CustomerName"
$ArtifactSource = "C:\git\Azure Local Cloud-docs-azl-toolkit\artifacts\phase-02-enterprise-readiness-validation"
$ProjectDocs = "C:\Projects\$ProjectName\validation\phase-02-enterprise-readiness"

# Create project documentation folder
New-Item -Path $ProjectDocs -ItemType Directory -Force

# Copy all artifacts
Copy-Item -Path "$ArtifactSource\*" -Destination $ProjectDocs -Recurse

# List collected artifacts
Write-Host "`n=== Collected Artifacts ===" -ForegroundColor Cyan
Get-ChildItem -Path $ProjectDocs -Recurse | Format-Table Name, Length, LastWriteTime

Required Artifacts

Artifact	Source	Status
Hardware inspection checklist	Step 1	☐
Network service test notes	Step 2	☐
Lighthouse-NodeStatus.png	Step 3 Screenshot	☐
SignOff-phase-02-enterprise-readiness.md	This document	☐

Additional Artifacts in Phase 03

Azure endpoint validation artifacts (Environment Checker output) will be collected in Phase 03 Step 4 after network infrastructure is configured.

---

Sign-Off Workflow

1. Complete Validation Summary

Fill in all sections of the sign-off template above.

2. Collect Artifacts

Run the artifact collection script to gather all validation outputs.

3. Review with Stakeholders

Schedule brief review meeting (15-30 min) with:

• Customer network contact
• Azure Local Cloud project manager
• Deployment engineer

4. Obtain Signatures

Get approval from all parties before proceeding to Phase 03.

5. Archive Documentation

Save signed document to project folder:

Projects/
└── AZL-CustomerName/
 └── validation/
 └── phase-02-enterprise-readiness/
 ├── SignOff-phase-02-enterprise-readiness-SIGNED.pdf
 ├── ValidationReport.html
 ├── EnvironmentChecker-Connectivity.txt
 └── Lighthouse-NodeStatus.png

---

Next Steps

Sign-Off Complete?	Next Action
✅ Yes - All Approved	Proceed to Phase 10: Network Infrastructure
❌ No - Issues Found	Resolve blocking issues with customer network team
⏸️ Pending Approval	Schedule sign-off meeting

---

Phase 02 Complete

Upon successful sign-off, the following has been validated:

• ✅ Physical infrastructure installed correctly
• ✅ DNS services operational
• ✅ NTP time synchronization working
• ✅ Azure endpoint connectivity confirmed
• ✅ OpenGear console access verified
• ✅ Customer approval obtained

Proceed to Phase 10: Network Infrastructure Configuration

---

Acceptance Criteria

• All Phase 02 validation steps completed with PASS status
• Sign-off template filled with all required information
• All artifacts collected and archived in project folder
• Approval obtained from customer and Azure Local Cloud representatives
• Documentation archived to artifacts/phase-02-enterprise-readiness-validation/SignOff-phase-02-enterprise-readiness-SIGNED.pdf

---

---

Manual

When to use: Use this option for manual step-by-step execution.

See procedure steps above for manual execution guidance.

Orchestrated Script

When to use: Use this option when deploying across multiple nodes from a management server using ariables.yml.

Script: See azurelocal-toolkit for the orchestrated script for this task.

Content Pending

Orchestrated script content references the toolkit repository.

Standalone Script

When to use: Use this option for a self-contained deployment without a shared configuration file.

Script: See azurelocal-toolkit for the standalone script for this task.

Content Pending

Standalone script content references the toolkit repository.

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 scripted methods shown in the tabs above. Additional deployment methods including Azure CLI and Bash scripts are available in the azurelocal-toolkit repository under scripts/deploy/.

Method	Description
Azure CLI	PowerShell-based Azure CLI scripts for Azure resource operations
Bash	Linux/macOS compatible shell scripts for pipeline environments

Navigation

← Task 03: OpenGear Verification	↑ Part 3: On-Premises Readiness	Phase 03: Network Infrastructure →

---

Variables from variables.yml

Variable	Config Path	Example
Signoff Approvers	onprem.validation.signoff_approvers	infrastructure-team@contoso.com
Validation Checklist	onprem.validation.checklist_template	enterprise-readiness-v1

---

Troubleshooting

Issue	Cause	Resolution
Validation checklist incomplete	Prerequisites from earlier phases not fully met	Review and complete all prerequisite phase tasks
Signoff blocked	Outstanding issues preventing approval	Address all blocking issues documented in validation report

---

Version Control

Version	Date	Author	Changes
1.0	2025-06-04	Azure Local Cloud	Initial document
1.1	2026-03-03	Azure Local Cloud	Standardized runbook format

---

End of Task