Multi-Cloud Workload Migration & Rationalization Framework¶

Workload Rationalization Economic & Architectural Governance

1. Migration vs Multi-Cloud Retention Decision Framework¶

When Mosaic Healthcare acquires an organization operating workloads in AWS or GCP, the Architecture Review Board (ARB) evaluates whether to Migrate into the Azure Landing Zone or Retain Multi-Cloud with Federated Governance.

2. Four Evaluation Pillars¶

1. Data Egress Economics & TCO¶

• Egress Penalty Threshold: Workloads exporting > 5TB of medical imaging or telemetry per month across cloud boundaries incur severe bandwidth fees ($0.02 - $0.09/GB). Consolidating into Azure reduces cross-cloud transit costs to zero.
• Enterprise Agreement (EA) Pricing: Mosaic leverages Azure EA enterprise discount tiers that typically yield 18–25% savings over uncommitted AWS/GCP retail rates.

2. Clinical Latency SLOs¶

• Tier-1 In-Hospital Clinical Systems: Must achieve < 15ms RTT from hospital bedside terminals to application backend. If the primary EHR (Epic/Cerner) resides in Azure East US 2, colocating supporting clinical engines in Azure is mandatory.
• Asynchronous Batch Analytics: Medical research, population health, and retrospective clinical trials have relaxed SLOs (hours/days) and can remain in AWS/GCP if specialized tooling warrants.

3. Specialty Capabilities & AI IP¶

• If an acquired research institute has developed proprietary deep learning models utilizing Google Cloud BigQuery ML or AWS Sagemaker / Bedrock, forced migration may disrupt clinical researchers. In such scenarios, the workload is retained with Azure Entra ID federation and Sentinel monitoring.

4. Operational Overhead & Security Surface Area¶

• Managing three distinct cloud IAM engines, firewall policies, and compliance auditing pipelines increases cyber risk surface area. Workloads are migrated to Azure by default unless an explicit ARB architectural exception is granted.

3. Workload Rationalization Action Matrix¶