Skip to content

Cloud Engineer. What I have done before.

I design and migrate Azure/Microsoft 365 workloads with security controls, rollback paths and cost limits built in: hybrid identity, Intune Autopilot, infrastructure as code and cloud operations that internal IT can inherit.

Areas of capability

Cloud and endpoint delivery experience behind Magrathean: Azure, Intune Autopilot, hybrid identity, infrastructure as code, recovery and cost control.

  • Azure IaaS, PaaS and hybrid cloud architecture
  • Intune Autopilot and Microsoft Configuration Manager (MECM) device provisioning
  • Infrastructure as code with PowerShell, ARM templates and Bicep
  • Virtualisation across Hyper-V and VMware
  • Network security groups, VPNs and Azure firewall configuration
  • Hybrid identity with Entra ID and Conditional Access
  • Backup and disaster recovery design across cloud and on-premises
  • Cost optimisation and performance tuning for SME budgets
  • CI/CD pipeline integration for infrastructure updates
  • Cloud-native monitoring, logging and incident response

Results from the role

Endpoint compliance in the in-house estate went from 72% to 96%, with provisioning and device trust built on Intune and Entra ID.

What changed when I ran IT in-house
Intune device compliance
  • Before72%
  • After96%
From my in-house IT roles before Magrathean, where I also took the organisation through Cyber Essentials Plus first time. More about my background.

Recovery plans are thin in small firms

Fewer than a third of micro businesses have a continuity plan that covers cyber security. That is the gap backup and recovery design closes.

Formal cyber security policy
  • 31%Micro
  • 52%Small
  • 75%Medium
  • 89%Large
Continuity plan covering cyber
  • 29%Micro
  • 44%Small
  • 73%Medium
  • 85%Large
Source: Cyber Security Breaches Survey 2025/2026 (opens in a new tab), DSIT and Home Office, April 2026. UK businesses.

See the broader practice

The same control-first approach spans identity, endpoint, tenant security, readiness and AI adoption.

Meet the founder

Selected experience

What changed, how it was checked and who could keep it running.

  1. 01

    Migrated on-premises workloads to Azure IaaS and PaaS in stages, sequenced to keep operations live, with explicit cost ceilings and rollback paths rather than open-ended cloud spend.

  2. 02

    Implemented Intune Autopilot and MECM for standardised Windows device provisioning, with Intune enrolment for macOS and Linux devices, integrated with Entra ID for identity-driven device trust.

  3. 03

    Built infrastructure-as-code templates in PowerShell and ARM/Bicep so deployments are repeatable, auditable and reviewable rather than configured by hand in the portal.

  4. 04

    Configured VPNs, network security groups and Azure firewall rules to secure cloud connectivity without trapping operations behind brittle perimeter rules.

  5. 05

    Implemented Azure backup and disaster-recovery solutions sized to the actual recovery objectives the business operates against, with documented test restores.

Questions teams ask first

Why does this matter to me?

I have run these systems myself, so the fixes I make are ones your IT team or provider can keep running.

Do I need to prepare anything?

No. A 30-minute call is enough to see whether I can help. No logins or screen sharing are needed.

Other backgrounds

Need a specialist who understands the operating team too?

Start a conversation