Managed first run onboarding

Managed first deployment run

Managed mode is fast to start, but the first run defines your operational standard. This guide connects onboarding, preflight, and change control into one repeatable flow.

Purpose

• Keep the first managed run reliable and controlled,
• confirm owner and approval model,
• capture baseline evidence for future runs.

Prerequisites

• Managed onboarding is complete (registration, workspace, server),
• template selected for intended scenario,
• deployment window and approver are defined.

Step-by-step

1. Validate scope — confirm workspace, target servers, and expected impact.
2. Run managed onboarding flow in managed getting started and complete all required inputs.
3. Review core values — domain, SSL expectation, DNS and service context.
4. Execute preflight in managed preflight and clear warning conditions.
5. Confirm approvals and communication before execution.
6. Start a minimal baseline rollout with a safe tag set.
7. Validate result immediately after completion: service health, run history and deployment details.
8. Close the run with owner, verifier, and remaining follow-up tasks.

Verification checklist

• Is scope and change owner explicit?
• Is there ticket/reference and approver trace?
• Did preflight pass all blocking checks?
• Is communication and rollback owner prepared?
• Is the run record complete in history?

Common mistakes

• Treating preflight warnings as cosmetic.
• Skipping approval window and comms in a production change.
• Undefined approver or rollback owner.
• Missing run notes that become the only missing compliance evidence.

Next steps

• Move to managed operations and governance for daily rhythm.
• Use managed onboarding checklist for standardization.
• Add template standards in managed templates and workflow.
• Review team access in managed workspace and security.

Next step: After the first run, validate managed governance checklist and keep run evidence in runbook and governance.