# Digital Transformation Journey to The Cloud

> Led a healthcare organization from a legacy on-prem datacenter to Azure and Microsoft 365, within strict regulation.

Canonical: https://mikereams.com/work/digital-transformation-journey-to-the-cloud

Year: 2020  
Change: On-prem DC → Azure + M365  
Technology: Microsoft Azure, PostgreSQL, Active Directory, Visual Studio Code, Azure API Management, Microsoft 365, Azure DevOps, Redis, Postman  
Topics: Cloud, Digital Transformation, Azure, API, Cloud Computing, IT Infrastructure, Security  
Write-ups: [Using the Microsoft MAP Toolkit for Estate Discovery](https://mikereams.com/writing/utilizing-microsoft-assessment-and-planning-toolkit)  
Diagrams: [Azure Hub-Spoke Network](https://mikereams.com/diagrams/azure-hub-spoke-network)

![Digital Transformation Journey to The Cloud](https://mikereams.com/work/a7d2769166b88640c943ef76e7b256aacc14240b-1024x535.jpg)

## The situation

A healthcare organization was running on a legacy on-premises datacenter and wanted to move to Azure and Microsoft 365 — while staying inside strict healthcare regulations the whole way.

## What drove it

- Faster time to market, by avoiding manual migration and minimizing custom development.
- Scaling without buying hardware.
- Building cloud-native applications.

## What I did

I orchestrated the transition. The transition-state architecture was a hybrid-cloud model: the on-premises datacenters stayed connected while workloads moved to Azure, and a new identity management system was integrated along the way. Discovery began with an agentless inventory of the estate using the [MAP Toolkit](https://mikereams.com/writing/utilizing-microsoft-assessment-and-planning-toolkit).