In build250K-member electric cooperative Confidential system, demo on request

Azure Hybrid Cloud Migration (In progress)

A ₱14.95M hybrid cloud program (in progress) designed and led by a single architect.

A ₱14.95M multi-milestone migration (in progress) of core operational workloads to Microsoft Azure, keeping compliance-bound systems on-prem.

Azure Hybrid Cloud Migration (In progress) screenshot

Team of one· Solo architect

No team, no agency, no hand-offs. I owned this project end to end:

  • Requirements
  • Architecture
  • Database
  • Infra & deployment
Stack
AzureHybrid CloudIdentity & DRArcherOS HCIVendor Mgmt

What was broken, and what fixed it

  1. Problem: Identity, collaboration, and disaster recovery needed to move to the cloud.

    Fix: Identity and collaboration move to Microsoft Azure, and disaster recovery runs there too, so a site failure has an off-site recovery target. In progress.

  2. Problem: Some workloads are compliance-bound and have to stay on-prem.

    Fix: A hybrid topology keeps those workloads on the on-prem HCI cluster. Workloads are placed by compliance requirement first, so regulated systems never leave the premises.

  3. Problem: A multi-milestone program can drift from its design along the way.

    Fix: Delivered in milestones under one architect, so each phase lands before the next starts and design decisions stay consistent.

Approach

  • A hybrid topology: on-prem HCI keeps the compliance-bound workloads, Azure takes identity, collaboration, and DR.
  • Delivered in milestones, with vendor management under one architect. In progress.

What I built

  • Hybrid cloud topology linking on-prem HCI with Azure
  • Identity and collaboration moved to Azure
  • Disaster recovery on Azure

Architecture

Data

  • Vendor Mgmt

Infrastructure & delivery

  • Azure
  • Hybrid Cloud
  • Identity & DR
  • ArcherOS HCI
  1. 1
    HCI cluster

    On-prem HCI keeps the compliance-bound workloads inside the cooperative.

  2. 2
    AzureIdentity

    Identity and collaboration move to Microsoft Azure.

  3. 3
    Azure

    Disaster recovery runs on Azure, so a site failure has an off-site recovery target.

  4. 4
    Azure

    A hybrid link ties the on-prem cluster and Azure into one topology.

Engineering

  • Delivered as a multi-milestone program, so each phase lands before the next one starts.
  • Workloads are placed by compliance requirement first, so regulated systems never leave the premises.
  • Vendor work is managed under one architect, so design decisions stay consistent across milestones.

Outcome

  • A ₱14.95M program led by a single architect.