Standard Operating Procedure: Azure Provisioning Log

1.0 Purpose

To define the technical sequence for provisioning and hardening HWB Azure resources. This ensures absolute environment parity between local development and the high-fidelity cloud production environment.

2.0 Universal Mandates (2026 Baseline)

1. Guidance First: If an Azure resource deployment fails, ASK the CEO before initiating a multi-token troubleshooting sweep.
2. Tier 6 Telemetry: Every infrastructure change must be logged to the SigmaInteractionLog.
3. Physical Truth: Reference absolute server paths for all ARM templates and deployment scripts.

3.0 Provisioning Sequence

1. Identity Hardening: Establish Microsoft Entra ID (Active Directory) for agent authentication.
2. Compute: Provision Azure App Service (B1 Tier) for the main Flask application.
3. Data: Provision Azure SQL Database (Standard S1) for transactional persistence.
4. Security: Activate Azure Key Vault for .env secret management.

4.0 Verification (Zero-Defect Check)

• Deployment logs show 100% success for all resources.
• Application is reachable via the verified Azure DNS endpoint.
• Tier 6 logs confirm the successful connection to the cloud database.

5.0 Revision History