Does this mean we avoid Azure?
No. We default to Azure because it is usually the fastest path to secure delivery and stable operations.
Official MPED strategy
Azure-first, Cloud-agnostic by design
We default to Microsoft Azure for speed and ecosystem benefits, while designing systems to run on other clouds or on-prem if required.
What this means in practice
- Business and domain logic decoupled from provider-specific services.
- Standards-first integration using HTTP, OpenAPI, OAuth2/OIDC, and Kubernetes-ready patterns.
- Thin adapters for identity, messaging, and storage to contain provider coupling.
- A portability path across hybrid hosting, EU sovereign cloud options, and on-prem estates.
- Security and compliance controls designed in from the start for regulated delivery.
Azure-first benefits
- Faster delivery using mature managed services, observability tooling, and Entra ID integration.
- Strong enterprise security posture with clear governance, policy, and identity controls.
- Operational reliability at scale with proven services for data, messaging, and automation.
- Best time-to-market for most organisations where Microsoft capability already exists.
Cloud-agnostic readiness
We structure solutions in layers so provider decisions stay reversible as business, regulatory, or residency needs change.
We apply portability where it materially reduces risk or improves compliance — not as default complexity.
Explore regulated environment deployment options.
DomainApp ServicesPlatform AbstractionsProvider (Azure / EU cloud / on-prem)
FAQ
Will we be incompatible with partners?
No. We favour open standards and clear APIs so partner ecosystems can integrate without tight platform dependency.
When would you run outside Azure?
When regulation, residency policy, sovereign requirements, or specific risk controls make another environment the better fit.
Is it more expensive?
Not necessarily. Cost depends on requirements and risk profile. We avoid overengineering and apply portability only where it creates measurable value.
How do migrations work?
We use a staged strangler approach with adapters, moving services incrementally while keeping business continuity and compliance evidence intact.
Built for risk-managed delivery
Our architecture choices prioritise delivery speed without compromising portability, assurance, or operational control in regulated environments.
Talk to us