Client project · Azure · Large-scale retail
An Azure landing zone. Infrastructure and standards for retail.
For one of Italy's leading large-scale retail businesses, I built an Azure landing zone and oversaw the addition of a range of resources. Alongside the infrastructure work, I guided the client in writing internal standards, documenting processes and making strategic technology decisions.
The context
A cloud foundation for diverse resources.
The project included virtual networks and subnets, firewalls, virtual machines, Blob Storage, Azure databases, service principals and Microsoft Entra ID. The engagement combined the technical implementation of the landing zone and its resources with discussions about how the client would define and document its cloud working practices.
Illustrative diagram
From the landing zone to internal standards.
An illustration of the work covered by this anonymised client project. The connections link technical implementation, resources and documentation; they do not show the order of every task or the production topology. Names, identifiers and confidential connections are omitted.
Open the full-resolution diagramProject responsibilities
Connect technical decisions to internal standards.
The range of resources required networking, compute, data and identity to be considered together. My role also included supporting decisions: helping the client make strategic technology choices and translate them into internal standards and documented processes.
Work carried out
From the landing zone to working practices.
Build the landing zone
I built the Azure landing zone and oversaw the addition of its resources. Networking included VNets, subnets and firewalls: components of the infrastructure covered by the engagement.
Add a range of services
The work included virtual machines, Blob Storage and Azure databases. I oversaw the implementation of these resources alongside the other landing zone components, addressing compute, storage and data management needs.
Work on identity
I also worked on the project's identity components: Microsoft Entra ID and service principals. This work sat alongside the implementation of networking, VMs and data services.
Guide standards and process documentation
I guided the client in writing internal standards and documented the processes. Alongside the resources implemented, the work therefore included written guidance for the team.
Support strategic decisions
I supported the client with strategic technology choices, connecting architecture decisions with the implementation of the environment and its internal standards.
Project outcomes
What the project delivered.
The engagement covered both the implementation of the Azure environment and support for the client's working practices and decisions.
- Infrastructure implementation
- Azure landing zone
A landing zone populated with networking, firewalls, VMs, storage, databases and identity management components.
- Working alongside the client
- Standards and processes
Guidance in writing internal standards and documenting the processes associated with the cloud work.
- Technology consulting
- Strategic decisions
Direct support for the client's technology decisions, alongside the infrastructure implementation work.
My role
Cloud Engineer and Cloud Architect in one project.
As a Cloud Engineer, I worked on implementing the landing zone and adding its resources. As a Cloud Architect, I supported the client with strategic technology decisions, standards and process documentation. Both responsibilities came together in the same engagement: building the environment and supporting the decisions around it.
What the engagement represents
Infrastructure, decisions and documentation.
This project reflects my approach to cloud consulting: following through on the technical implementation while working with the client on the decisions and processes around it. The landing zone, deployed resources and internal standards are parts of the same work.