- Client
- European industrial group
- Sector
- Industrial
- Services
- Azure Infrastructure, Landing Zone Design
- Year
- 2025
- Timeline
- Design and review
- Read time
- 3 min read
2
European regions designed, primary and standing recovery
SD-WAN
Existing network preserved in the design
1
Superseded firewall order caught before delivery
01 · The challenge
What we walked into
The group was committed to leaving a managed provider's datacentre and needed its Azure environment designed around the estate it runs today, with an existing SD-WAN carrying traffic between sites, compliance obligations across Europe, and no appetite for a network redesign on top of a cloud migration.
The landing zone also had to hold up in front of the group's own architects, which is a higher bar than simply working. Every design decision needed an owner, an evidence base, and a version history that could survive review rounds.
02 · Our approach
How we got there
- 01
Establish the estate
We pinned the premise and the target state down before designing anything, so the SD-WAN, site inventory, and compliance constraints were all established from evidence before a single subscription was drawn.
Evidence first
- 02
Design the landing zone
Management groups, subscriptions, connectivity, and a standing recovery region in Europe, all designed around the existing SD-WAN, which carried the landing zone without redesign.
Core design
- 03
Carry it through review
The same architect stayed through every review round, and revisions were issued as tracked changes against specific comments, so nothing was re-litigated from scratch.
Review rounds
- 04
Order against the final design
The design was specific enough to procure against. We stayed through procurement and caught a firewall order scoped against a superseded diagram before it was delivered.
Handover
03 · The outcome
What changed
The group moved to Azure on a landing zone designed for its actual network and compliance position, with a design that survived review unchanged in substance and every procurement order checked against the final revision of the plan.
A defensible design
The landing zone passed the group's internal architecture review with every decision traceable to evidence.
Recovery built in
A standing recovery region in Europe was part of the core design from the first revision.
Procurement protected
Hardware and circuit orders were checked against the final design revision, catching one scoped against a diagram that no longer existed.
Technologies
- Azure Landing Zone
- Azure Policy
- SD-WAN
A note on confidentiality
Much of our work takes place in regulated and security-sensitive sectors, where the details of a client's environment are confidential by default. In line with our commitments to those clients, identifying details in this case study have been anonymised or generalised, while the work, the decisions, and the outcomes are described as delivered.
If you would like to know more about this engagement, we are happy to discuss it further and can share additional information on request.