Nordlicht Reisen GmbH, a fictional travel agency, wants to leave its data center in Hamburg. Before the first machine moves, it has to be settled where it goes: into which subscriptions, under which rules, with which connection to the old data center. This is exactly what Microsoft wrote the Cloud Adoption Framework (CAF) and the landing zones for. This lesson assesses how a migration builds on them and chooses how the landing zone comes about. How a server, an application or a database moves is covered in lessons 5.2 to 5.4.
Prior knowledge. You design management groups, subscriptions and resource groups in lesson 1.5 of this course and compliance with Azure Policy in lesson 1.6; governance and cost as an architecture topic appear in "K4, lesson 4.7.7", the frame of an architecture decision in "K4, lesson 4.7.1" and in lesson 0.1 of this course. None of that is repeated here. What is new is how the CAF arranges these parts into a sequence and which landing zone carries the migration.
The requirement
All numbers are assumptions of the exercise, not measured. G-01 to G-10 apply (lesson 0.2), especially G-03, G-06 and G-08.
| No. | Requirement | Type | Metric | Weight | Source |
|---|---|---|---|---|---|
| 5.1-01 | The data center in Hamburg is vacated. | R | lease ends in 18 months; assumption | Must | Management |
| 5.1-02 | Data and resources stay in the EU, enforced rather than agreed. | R | violations are rejected, not just reported (G-08) | Must | Data protection |
| 5.1-03 | The portal and the partner API are run by two teams, each within its own scope. | F | two teams, separate permissions; assumption | Must | Operations |
| 5.1-04 | During the migration, Azure and Hamburg stay connected. | F | applications in both worlds can reach each other | Must | Operations (G-03) |
| 5.1-05 | The foundations of the platform are code and are reviewed. | Q | every change through a pipeline; assumption | Should | Operations |
| 5.1-06 | New subscriptions for teams are available quickly and governed the same way. | Q | within 2 business days; assumption | Should | Operations |
| 5.1-07 | The team has had little experience with infrastructure as code so far. | R | two people with basic knowledge; assumption | Should | Operations |
| 5.1-08 | In the early period, the platform should have as little running cost as possible. | K | only building blocks that the first move needs | Could | Management |