How an unexpected regional constraint forced us to deeply understand Azure GPU VM families, naming conventions, and workload fit.

Introduction

As architects, we often assume that infrastructure decisions are straightforward:

"The workload is already running successfully in Region A. Let's deploy the same Kubernetes workload in Region B."

That's exactly what we thought.