Microsoft Cloud Infrastructure Architect

You’ll work across a varied Microsoft infrastructure estate, with responsibility including:

• Designing and delivering Azure infrastructure and hybrid cloud solutions
• Designing and evolving Azure Landing Zones, using Cloud Adoption Framework principles
• Working across Microsoft 365, including Entra ID, identity, Intune and associated infrastructure services
• Planning and leading Microsoft 365 migrations and tenant consolidation
• Supporting the integration of acquired businesses into the wider Microsoft environment
• Producing practical HLDs and LLDs and staying involved through implementation
• Working directly with infrastructure and cloud engineers to solve technical problems and guide deployments
• Using Terraform and Infrastructure as Code to standardise Azure deployments
• Working with Azure DevOps and deployment pipelines
• Supporting Azure migration, modernisation and infrastructure transformation
• Designing secure approaches to identity, networking and cloud governance
• Improving Azure environments from both a technical and cost perspective

There’s also scope to evaluate emerging Microsoft technologies, including Copilot, AI Foundry and Microsoft Fabric, as the wider technology landscape develops.

The two core requirements are Microsoft Azure and Microsoft 365.

You’ll probably have come from a strong infrastructure or cloud engineering background and progressed into architecture, while retaining the technical depth to work effectively with engineering teams.

Relevant experience is likely to include a good mix of:

• Microsoft Azure
• Microsoft 365
• Azure Landing Zones / Cloud Adoption Framework
• Terraform / Infrastructure as Code
• Azure DevOps
• Entra ID and hybrid identity
• Intune
• Azure networking and security
• Microsoft 365 and tenant-to-tenant migrations
• Cloud migration and modernisation
• HLD and LLD production
• Working with engineers from design through to implementation

Experience with FinOps / Azure Cost Management, Power Platform, Dynamics 365, Copilot or AI governance, or infrastructure across multiple companies and acquired businesses would be useful, but you’re not expected to be an expert in everything.

The important combination is strong Azure and Microsoft 365 capability, architecture-level thinking and a willingness to remain technically involved in delivery.

If you’ve moved from Microsoft infrastructure engineering into architecture but still want to stay close to the technology, this role is worth considering.

The environment spans Azure and Microsoft 365, with an ongoing programme of cloud transformation, modernisation and company acquisitions. The role sits between architecture and engineering: you’ll design solutions, produce the HLDs and LLDs, then work with engineering teams through implementation rather than handing the design over and moving on.

That means getting involved in the technical decisions that matter across Azure infrastructure, Microsoft 365, identity, networking, migrations, automation and cloud governance.