# Phase 2: Setup and Implementation Guide

## Overview

This guide covers the setup and deployment of Unique's weekly bundle into a Customer Managed Tenant. It defines the expected timeline, responsibilities split between the customer and Unique, dependencies, and the activities required for a successful deployment.

**Audience:** IT administrators, cloud architects, and client support teams responsible for deploying and maintaining the Unique application in Azure environments.

**Expected Duration:** Minimum **2 months** if aligned with the Unique Landing Zone (ULZ). Minimum **3 months** if the customer has deviated from ULZ.

## Dependencies

Before starting Phase 2, the following must be confirmed:

- **Phase 1 complete:** All items in the Phase 1: Prerequisites for Customer Managed Tenant checklist are fulfilled, checked, or mitigated.

- **Provisioned resources:** Initial Azure resources (AKS cluster, KeyVaults, networking, identity) are provisioned per Phase 1 specifications.

- **Pre-Installation Checklist:** Any open items or deviations from the standard ULZ have been documented and communicated to Unique.

## Out of Scope

Client-specific customizations and enhancements — such as private API Gateway compatibility, AI model usage changes, or non-standard integrations — are **out of scope** for this phase. Any customizations or enhancements will incur additional charges and affect the timeline. These should have been identified during the PREPARE phase using the Pre-Installation Checklist.

## Customer Activities

**1. Verify Prerequisites**
- **Customer must** confirm all Phase 1 prerequisites are met before proceeding with bundle installation.

**2. Install Bundle Components**
- **Customer must** install the necessary parts of the Unique weekly bundle into their environment, following Unique's provided instructions and Helm charts.

**3. Configure and Install the Unique Product**
- **Customer must** complete setup and configuration of the Unique product, including environment-specific settings (certificates, DNS, identity bindings).

**4. Appoint and Train Support Team**
- **Customer must** appoint a first-level support team responsible for ongoing maintenance and troubleshooting.
- **Customer must** ensure this team receives the necessary training — Unique will provide advisory support for this.

## Unique Activities

**1. Deliver Updated Release Bundle**
- **Unique provides** the latest weekly bundle release to the customer, including Helm charts, container images, and release notes.

**2. Advisory on Installation and Deployment**
- **Unique provides** advisory support throughout the installation and deployment process. Note: Unique advises; the customer executes.

**3. Consulting on SSO, Support Setup, and Initial Configuration**
- **Unique provides** consulting on SSO configuration, support team setup, and initial product configuration.
- **Unique monitors** the deployment to identify issues early.

**4. Ongoing Advisory Support**
- **Unique provides** ongoing advisory support on configuration and installation questions throughout the phase.

## Coordination and Communication

- **Regular check-ins:** Schedule recurring status syncs between the customer's team and Unique's SE/support team to track progress and address issues promptly.
- **Misconfiguration risk:** Coordination gaps are the primary source of deployment delays — proactive communication is essential.

> **TODO — Diagram needed:** Swimlane diagram showing the Phase 2 timeline with parallel customer and Unique activity tracks, key milestones (prerequisites verified → bundle delivered → components installed → product configured → support team trained → go-live readiness), and handoff points between the two parties.