Implementation Roadmap

Audience

This roadmap is for Project Managers, IT Architects, IT Security Teams, Financial Operations, Compliance Officers, Technical Teams (Developers, DevOps, IT Support), Client’s Central Teams, and Unique Advisors. Each group ensures a coordinated approach to implementing the Customer Managed Tenant solution, facilitating a smooth and compliant deployment.

Scope

This Confluence page serves as the implementation roadmap for the Customer Managed Tenant (CMT) project. It outlines the detailed phases, activities, dependencies, and estimated timelines required to successfully implement a CMT. The project is divided into three main phases: Prepare, Set Up, and Run. Each phase contains specific tasks that must be completed sequentially to ensure a smooth and compliant implementation.

Phases, Activities, and Timelines

Phase 1: Prepare

• Expected Duration: Minimum 2 month. If deviated from ULZ, Minimum 3 months.

• Dependencies: Availability of client’s full-time employees (at least 60% FTE), support from client’s central teams (e.g., IT Security, IT Architecture, Financial Operations, Compliance).

• Client Activities:

  • Prepare Azure tenant according to the Pre-Installation Checklist.

  • May provision all Azure Entra and ARM resources required to accommodate Unique either with the provided bundle or by other means.

  • Conduct internal training sessions.

  • Develop documentation.

  • Provide initial guidance and training support.

  • Support transition to IaC (Infrastructure as Code).

  • Configure RBAC (Role-Based Access Control) and Managed Identities.

  • Implement API access management.

  • Set up egress traffic management.

  • Integrate custom gateways.

  • Prepare for certificate management.

• Unique Activities:

  • Provide a Releases bundle containing Terraform code to provision all needed resources.

  • Advise the client where desired or needed (on a daily rate), including:

    • Advisory for the prerequisites.

    • Advisory on the deployment of the Unique landing zone content.

Phase 2: Set Up

• Expected Duration: Minimum 2 month. If deviated from ULZ, Minimum 3 months.

• Dependencies: Successful completion of the Prepare phase.

• Client Activities:

  • Install parts of the bundle and verify prerequisites.

  • Configure and install Unique Product.

  • Appoint a 1st level support team and provide training.

• Unique Activities:

  • Provide updated Releases bundle.

  • Advise on installation and deployment.

  • Offer consulting on support services, SSO configurations, and initial setup.

  • Monitor deployment.

  • Provide advisory support on configuration and installation.

Phase 3: Run

• Expected Delivery: The ULZ model, when all the pre-installation steps are fulfilled, is typically ready for testing on the client's tenant after approximately 3 months. Production-ready setups often take more than 6 months due to dependencies on security requirements, processes, and client permissions.

• Deviated Models: For models that deviate from the ULZ standard, testing readiness on the client's tenant usually occurs after at least 9 months. This extended timeline is also due to the dependencies on security requirements, processes, and client permissions. In these cases, production-ready setups often take more than 12 months from the first iteration.

• Dependencies: Ongoing client support and updates.

• Client Activities:

  • Install regular updates and bundles.

  • Triage incidents and continue installing updates.

  • Provide logs and telemetry.

  • Conduct audits and compliance checks.

  • Optimize configurations.

• Unique Activities:

  • Provide new bundles as defined in Releases.

  • Investigate support tickets.

  • Offer advisory support on configuration issues.

  • Deliver updates and support.

  • Advise on compliance and optimization.

Disclaimers and Notes

• Dependencies: Each phase depends on the successful completion of the previous phase.

• All Azure costs: Directly paid by the customer.

• Availability: Timelines depend heavily on the availability of client and Unique employees.

• Non-binding estimations: Effort highly dependent on client's security requirements, processes, and permissions.

Visual Representation

Below is the Gantt Chart visual representation of the project phases and activities:

Open

See also :