Enterprise Azure migration
One Azure platform transition across 30 locations and 700 users.
For Dentalum, I led a migration that crossed infrastructure, identity, collaboration, access, and the operational processes around them. The challenge was not moving one workload. It was creating a coherent transition for 30 locations and 700 users without treating each technical boundary as a separate project.
- Scale
- 30 locations / 700 users
- Driver
- NIS2-aligned platform transition
- Role
- Architecture and migration lead
01
Treat the migration as one operating system.
Identity, email, SharePoint, networking, virtual desktops, and staff administration all affected one another. Planning them as isolated workstreams would have moved the integration risk into daily operations.
I led the architecture, migration planning, and coordination across those boundaries, keeping the technical design tied to how clinics and staff would actually work.
02
Separate access without fragmenting the platform.
The network design used a shared Azure virtual network with deliberately separated clinic subnets. Azure Virtual Desktop and virtual machines provided controlled remote access, while Entra ID and dynamic security groups established the identity structure around each clinic.
- Mail migration, Entra ID, and dynamic clinic security groups
- A shared Azure VNet with separated clinic subnets
- Azure Virtual Desktop and virtual machines for controlled access
- SharePoint and collaboration-platform migration
03
Make staff changes part of the architecture.
Onboarding and offboarding are platform events, not administrative afterthoughts. Azure Functions connected business systems to staff lifecycle workflows so access changes could follow the same structure as the rest of the environment.
The same systems view now informs a separate phased transition between two core operational platforms, including migration planning, data mapping, system analysis, and vendor coordination.
Complex migrations become dependable when identity, infrastructure, data, access, and operating routines are designed as one transition.