Skip to content

Enterprise Financial Services Organization Financial services

Consolidating Azure tenants into one governed platform for analytics and applications

A tenant-to-tenant Azure migration onto a unified AKS and data platform, delivered through Terraform, Terragrunt and Harness.

Representative experience of the VBR engineering team. The organization is not named, and internal details are omitted.

Challenge

  • Workloads were spread across separate Azure tenants with different standards for identity, networking and monitoring.
  • Data teams on Azure Databricks and Snowflake depended on credentials and network paths that would not survive the move.
  • Infrastructure changes were not consistently managed through code or a governed pipeline.

Business context

As a regulated financial institution, the client needed the consolidation to strengthen controls rather than trade them for speed. The target platform had to support both application teams on Kubernetes and analytics teams on managed data services.

Architecture

Unified Azure platforminspection point

Simplified view. Internal names, addresses and configuration are omitted.

Solution

  • Designed a unified target architecture with shared platform services for identity, networking, monitoring and security.
  • Built AKS as the standard application runtime, with Managed Identity replacing stored credentials for workloads.
  • Codified infrastructure in Terraform and Terragrunt, run through Terraform Enterprise with policy checks.
  • Implemented Harness pipelines for repeatable application and infrastructure delivery.
  • Re-established Azure Databricks and Snowflake connectivity and access in the target tenant.

Technology

  • Azure
  • AKS
  • Terraform
  • Terragrunt
  • Terraform Enterprise
  • Harness
  • Managed Identity
  • Azure Databricks
  • Snowflake
  • Azure Monitor

Engineering approach

  1. Step 1

    Target architecture first

    Agreed the shared services model and landing zone before moving any workload.

  2. Step 2

    Modules over snowflakes

    Every environment built from the same Terragrunt-composed modules.

  3. Step 3

    Identity-led migration

    Moved workloads to Managed Identity as part of migration, not as a follow-up.

  4. Step 4

    Platform observability

    Monitoring and alerting stood up in the target before cutover.

Security

  • Managed Identity in place of stored secrets
  • Policy checks in Terraform Enterprise runs
  • Centralized monitoring and security services
  • Network segmentation through shared platform networking

Outcomes

  • Standardized cloud architecture across previously separate tenants
  • Improved platform governance through code-managed, policy-checked change
  • Stronger security controls with identity-based access for workloads
  • A more scalable engineering model for application and data teams

Discuss a similar transformation

We'll talk through your environment and how we approached comparable work.