Portfolio · Case studies

Projects

A selection of projects I've worked on as a Cloud Solution Architect, together with my team and customer teams, from assessment to delivery. Very different technologies and contexts, with one common thread: secure, well-governed, production-ready platforms.

projects
15
technologies
119+
industries
13
areas of expertise
8

Some of the technologies used across these projects

  • Cloud Adoption Framework
  • Azure Files
  • Azure Landing Zone
  • Hub & Spoke
  • Azure Backup
  • AD Certificate Services
  • Azure Virtual Desktop
  • Conditional Access
  • Availability Zones
  • Active Directory
  • Web Application Firewall
  • Private Link
  • Private Endpoint
  • Two-Tier PKI
  • Offline Root CA
  • RemoteApp
  • Scaling Plan
  • FSLogix
  • Azure Firewall
  • Microsoft Intune
  • Windows Autopilot
  • Entra Connect
  • Windows LAPS
  • OneDrive Known Folder Move
  • Microsoft Authenticator
  • Microsoft Entra ID
  • Entra Application Proxy
  • Azure Virtual Machines
  • Azure Migrate
  • WatchGuard Firebox Cloud
  • Site-to-Site VPN
  • NSG / ASG
  • Azure Bastion
  • SQL Server Always On
  • Azure Load Balancer
  • Azure Monitor
  • Azure Front Door Premium
  • Azure Firewall Premium
  • IDPS
  • Hub-and-Spoke
  • Private DNS Zones
  • VPN Gateway
  • Microsoft Defender for Cloud
  • Log Analytics
  • Cloud Security Benchmark
  • Enterprise Subordinate CA
  • Hardware Security Module
  • Certificate Templates
  • CRL / CDP
  • Privileged Access Workstation
  • Privileged Access Management
  • SIEM
  • Windows Server 2022 Core
  • Windows 11 multi-session
  • GPU VMs (NVv4)
  • Private DNS Resolver
  • AVD Insights
  • Defender for Endpoint
  • Attack Surface Reduction
  • Windows Hello for Business
  • Hybrid Join
  • BitLocker
  • Windows Update for Business
  • Win32 App Packaging
  • Always On VPN
  • Device Tunnel / IKEv2
  • Azure VPN Gateway
  • Internal Load Balancer
  • Configuration Manager
  • Well-Architected Framework
  • Azure Policy
  • Defender for Cloud
  • Azure SQL
  • Azure Database for MySQL
  • Microsoft Fabric
  • VMware vSphere 7.0
  • Dell PowerEdge
  • Dell EMC Unity XT 380
  • Fibre Channel SAN
  • Synchronous Replication
  • SAN Copy Pull
  • Veeam Backup & Replication
  • Veeam File Share Backup
  • Scale-Out Backup Repository
  • Azure Blob Storage
  • Windows Server File Server
  • Microsoft Entra ID P2
  • Privileged Identity Management
  • PIM for Groups
  • Authentication Context
  • Role-assignable Groups
  • Break Glass Accounts
  • Group Policy
  • AD FS
  • Windows Server 2022
  • PowerShell
  • Hybrid Entra Join
  • NDES / SCEP
  • Intune Certificate Connector
  • SSPR
  • Android Enterprise
  • iOS / iPadOS
  • Azure File Sync
  • Cloud Tiering
  • Storage Sync Service
  • Azure Storage GPv2
  • Recovery Services Vault
  • Windows Server 2019
  • Data Deduplication
  • Microsoft Hyper-V
  • Windows Server
  • Connector Groups
  • Split-brain DNS
  • TLS Certificates
  • NVIDIA Omniverse
  • Azure Virtual Network
  • Network Security Group
  • Azure Storage
  • Azure RBAC

All projects are anonymized: customer names and identifying details have been omitted.

  • Migration & Assessment
  • Networking
  • Landing Zone & Governance

Azure Landing Zone and VMware Lift & Shift migration

CAF hub & spoke landing zone, NVA firewall, zone-redundant domain controllers and wave-based Azure Migrate migration, including a SQL Server Always On cluster.

Industry
Transport & mobility
Scope
Up to 48 servers · 29 migrated VMs
Role
Architect · team delivery
Complexity
High

As Cloud Solution Architect I led the design of the Azure landing zone for a transport operator; together with the team we then carried the delivery through to the Lift & Shift migration of workloads from VMware. The journey covered a CAF subscription model, hub & spoke networking with an NVA firewall and site-to-site VPN, zone-redundant domain controllers and Azure Migrate migration by application islands and weekly waves.

Migrated VMs
29
SQL availability groups
11
CAF subscriptions
4
  • Azure Landing Zone
  • Cloud Adoption Framework
  • Azure Migrate
  • Hub & Spoke
  • WatchGuard Firebox Cloud
  • Site-to-Site VPN
  • NSG / ASG
  • Azure Bastion
  • +6
Challenge, solution and outcomes

The challenge

  • Build a Cloud Adoption Framework-governed landing zone ready for both migrated and cloud-native workloads.
  • Migrate 29 heterogeneous VMs (Windows Server and Linux) respecting dependencies: about 70% during business hours and 30% outside.
  • Rebuild a SQL Server Always On cluster with 11 availability groups and 12 listeners in Azure while keeping high availability.

The solution

  • CAF landing zone across 4 subscriptions (management, identity, connectivity, application) with hub & spoke: 5 VNets, 8 subnets and Azure Bastion.
  • NVA firewall (WatchGuard Firebox Cloud) in the hub VNet for symmetric control of all inbound and outbound internet traffic.
  • East-west segmentation with 4 per-tier Network Security Groups and VM-based Application Security Groups.
  • Domain controllers across Availability Zones on a dedicated identity subscription, following virtualized-DC best practices.
  • Azure Migrate with a discovery appliance on VMware, 33 VMs assessed and migration organized into 4 application islands.
  • SQL Server Always On on a Standard Azure Load Balancer with 12 frontend IPs, nodes across Availability Zones and a file share witness.

The outcomes

  • Governed Azure platform ready to host the remaining on-premises infrastructure and new cloud-native workloads.
  • Centralized network security: internet under perimeter firewall control, east-west segmentation and admin access through Bastion.
  • Increased resilience for critical services with domain controllers and SQL nodes spread across Availability Zones.

Skills demonstrated

  • Azure Landing Zones per the Cloud Adoption Framework
  • Azure networking: hub & spoke, NVA, UDR, VPN, NSG/ASG
  • Datacenter migration by application islands and waves
  • High availability with Availability Zones and Load Balancer
  • Team-based technical delivery and as-built documentation

Technology stack

  • Azure Landing Zone
  • Cloud Adoption Framework
  • Azure Migrate
  • Hub & Spoke
  • WatchGuard Firebox Cloud
  • Site-to-Site VPN
  • NSG / ASG
  • Azure Bastion
  • Availability Zones
  • SQL Server Always On
  • Azure Load Balancer
  • Active Directory
  • Azure Backup
  • Azure Monitor
  • Networking
  • Security & Zero Trust
  • Landing Zone & Governance

Azure Network Hardening: Hub-and-Spoke, Front Door WAF and Azure Firewall

Assessment and High Level Design to eliminate application public IPs, privatize PaaS services and centralize ingress, egress, DNS, logging and security posture.

Industry
ICT · Document management SaaS
Scope
27 VMs · 31 App Services · 13 VNets
Role
Architect · assessment & design
Complexity
High

Together with the team we assessed the Azure environment of a software company delivering a document management SaaS platform; as Cloud Solution Architect I led the High Level Design for its network hardening. VMs and PaaS services were exposed directly to the internet without a centralized WAF, with a Secure Score of 39.41%: the target architecture introduces a single entry point with Front Door Premium and WAF, a single egress point with Azure Firewall Premium and PaaS privatization through Private Endpoints.

Baseline Secure Score
39.41%
App Services to privatize
31
App public IPs in target design
0
  • Azure Front Door Premium
  • Web Application Firewall
  • Azure Firewall Premium
  • IDPS
  • Hub-and-Spoke
  • Private Link
  • Private Endpoint
  • Private DNS Zones
  • +4
Challenge, solution and outcomes

The challenge

  • 10 production VMs with public IPs directly on their NICs and 31 App Services with public access, mostly without WAF.
  • Direct internet egress from VMs without IDPS and a weak posture: 39.41% Secure Score and 334 unhealthy controls.
  • Fragmented network (partial peerings, one isolated VNet, non-zone-redundant VPN Gateway) and 6 open service-retirement categories.

The solution

  • Hub-and-Spoke topology with a dedicated hub, peering to spokes and UDRs forcing egress through the firewall.
  • Ingress only through Azure Front Door Premium with WAF (Default Rule Set, Bot Manager, rate limiting) and 4 Origin Groups.
  • Egress through Azure Firewall Premium with IDPS in Alert+Deny, DNS Proxy, FQDN application rules and network rules.
  • PaaS privatization (App Service, Function Apps, SQL, Key Vault) with Private Endpoints and public access disabled.
  • Centralized Private Link DNS, a single Log Analytics workspace and Microsoft Defender for Cloud across all subscriptions.
  • Segregation by subscription (2 platform + 3 workload), CAF naming and remediation of service retirements.

The outcomes

  • Significantly reduced attack surface: ingress only through WAF, egress only through IDPS, PaaS reachable only privately.
  • Clear governance with platform/workload separation, CAF naming, centralized DNS and logs.
  • Measurable security posture with Defender for Cloud and the Microsoft Cloud Security Benchmark, starting from a documented baseline.

Skills demonstrated

  • Azure environment and security posture assessment
  • Hub-and-Spoke and Zero Trust network architectures
  • Front Door / WAF and Azure Firewall Premium / IDPS
  • Private Link and centralized private DNS
  • Defender for Cloud and Cloud Adoption Framework
  • Risk management and multi-phase cutover planning

Technology stack

  • Azure Front Door Premium
  • Web Application Firewall
  • Azure Firewall Premium
  • IDPS
  • Hub-and-Spoke
  • Private Link
  • Private Endpoint
  • Private DNS Zones
  • VPN Gateway
  • Microsoft Defender for Cloud
  • Log Analytics
  • Cloud Security Benchmark
  • Security & Zero Trust
  • Identity & Access

Two-Tier enterprise PKI with HSM

Low-level design of a multi-site Microsoft Certification Authority: offline Root CA, private keys in HSM, highly available CRL, privileged access via PAW/PAM and SIEM integration.

Industry
Public sector · critical infrastructure
Scope
2 segregated PKIs · 8 VMs · 4 HSM modules
Role
Architect · assessment & design
Complexity
High

As Cloud Solution Architect I contributed to the low-level design of an enterprise PKI based on Active Directory Certificate Services in a Two-Tier model, for a public-sector critical infrastructure. Offline Root CA with HSM-protected keys, Enterprise Subordinate CA with auto-enrollment, highly available CRL on a multi-site architecture, admin access only through PAW/PAM and audit logs sent to a SIEM.

HSM modules
4
Segregated PKIs
2
Monitored security events
21
  • AD Certificate Services
  • Two-Tier PKI
  • Offline Root CA
  • Enterprise Subordinate CA
  • Hardware Security Module
  • Certificate Templates
  • CRL / CDP
  • Privileged Access Workstation
  • +3
Challenge, solution and outcomes

The challenge

  • Protect the Root CA private key from any compromise while keeping the certification service available.
  • Distribute the PKI across a multi-site high-availability architecture with secure key replication.
  • Integrate the PKI with HSM, PAM, SIEM and backup, with clear and repeatable operational processes.

The solution

  • Two-Tier hierarchy: offline standalone Root CA integrated with HSM and Enterprise Subordinate CA for auto-enrollment and scale.
  • 4 HSM modules with offline (Root CA) and active (Sub CA) partitions replicated; RSA 4096-bit / SHA-256 keys generated inside the HSM.
  • Two independent, segregated PKIs for distinct service perimeters, limiting incident propagation.
  • CRL published over HTTP by web servers distributed across sites, reachable even if one site is unavailable.
  • Admin access only from Privileged Access Workstations through PAM, with local accounts disabled.
  • Audit logs to a SIEM with a catalogue of 21 security events and monthly patching validated in the lab.

The outcomes

  • Protected chain of trust: offline Root CA and HSM-held keys drastically reduce compromise risk.
  • Always-available certification service through a load-balanced CRL and VM and HSM replication.
  • Governance and traceability: PAW/PAM access, centralized audit and patching and renewal processes defined for every role.

Skills demonstrated

  • Enterprise PKI design for high-criticality environments
  • AD CS and HSM integration and key management
  • Multi-site high-availability architectures
  • Privileged Access Management and least privilege
  • Security monitoring and SIEM integration
  • Low-level design, sizing and traffic-flow matrix

Technology stack

  • AD Certificate Services
  • Two-Tier PKI
  • Offline Root CA
  • Enterprise Subordinate CA
  • Hardware Security Module
  • Certificate Templates
  • CRL / CDP
  • Privileged Access Workstation
  • Privileged Access Management
  • SIEM
  • Windows Server 2022 Core
  • Virtual Desktop
  • Networking

Enterprise multi-pool Azure Virtual Desktop

From PoC to production: 5 host pools for different profiles (standard users, ERP developers, IT, GPU-powered CAD) on a hub & spoke network with Azure Firewall, hybrid DNS and FSLogix profiles.

Industry
Industrial manufacturing · Plant engineering
Scope
5 host pools · 14 session hosts
Role
Architect · team delivery
Complexity
Medium-high

Together with the team we designed and delivered the Azure Virtual Desktop platform of an international industrial group, providing a standard virtual workstation accessible from any device and location. Starting from a two-pool PoC, we took 5 host pools and 14 Windows 11 multi-session hosts into production for very different profiles, including CAD designers on GPU VMs.

Host pools
5
Session hosts
14
Application groups
14
  • Azure Virtual Desktop
  • Windows 11 multi-session
  • RemoteApp
  • Scaling Plan
  • GPU VMs (NVv4)
  • FSLogix
  • Azure Files
  • Azure Firewall
  • +4
Challenge, solution and outcomes

The challenge

  • Turn a single-subscription PoC, with on-premises AD and site-to-site VPN, into a production service for users with diverse needs.
  • Ensure on-premises reachability, correct hybrid DNS and traffic control through a centralized firewall.
  • Align with the existing operating model (Configuration Manager, GPOs) without overturning it.

The solution

  • Hub & spoke network with Azure Firewall for centralized inspection of east-west and north-south traffic.
  • Hybrid DNS with Azure Private DNS Resolver for bidirectional resolution between Azure and on-premises.
  • 5 pooled host pools and 14 session hosts across 3 Availability Zones, sized for standard, ERP, IT and GPU CAD profiles.
  • 3 optimized master images and 14 application groups across Desktop and RemoteApp.
  • FSLogix Profile Containers on Azure Files through a private endpoint, joined to Active Directory.
  • Scaling plan, depth-first load balancing and monitoring with AVD Insights.

The outcomes

  • Standard virtual workstation, as Full Desktop or RemoteApp, accessible from any device and location.
  • Network under control with hub & spoke, a centralized firewall and per-subnet NSGs.
  • Contained costs: depth-first and scaling plans keep only the required VMs running.

Skills demonstrated

  • Enterprise multi-pool AVD design and delivery
  • Azure networking: hub & spoke, Azure Firewall, hybrid DNS
  • Image management and session host optimization
  • Profile management with FSLogix and Azure Files
  • From PoC to production

Technology stack

  • Azure Virtual Desktop
  • Windows 11 multi-session
  • RemoteApp
  • Scaling Plan
  • GPU VMs (NVv4)
  • FSLogix
  • Azure Files
  • Azure Firewall
  • Hub & Spoke
  • Private DNS Resolver
  • Private Endpoint
  • AVD Insights
  • Modern Workplace
  • Security & Zero Trust
  • Identity & Access

Modern Endpoint Management & Zero Trust Security

From domain-managed PCs to a cloud-managed model: Intune, Defender for Endpoint, Conditional Access and passwordless.

Industry
ICT · Software development
Scope
~50 users · 42 devices
Role
Architect · team delivery
Complexity
Medium-high

As Cloud Solution Architect I led the design of the Windows endpoint management and security transformation for a software SME, then delivered it together with the team: from a fleet managed only through Active Directory, with partial MFA, to a hybrid cloud-managed model on Intune and Defender for Endpoint, governed by Conditional Access and with passwordless sign-in. The rollout was progressive, test → pilot → production, across 42 devices.

Devices rolled out
42
ASR rules
19
Users protected by MFA
39 → all
  • Microsoft Intune
  • Windows Autopilot
  • Defender for Endpoint
  • Attack Surface Reduction
  • Conditional Access
  • Windows Hello for Business
  • Entra Connect
  • Hybrid Join
  • +4
Challenge, solution and outcomes

The challenge

  • MFA enforced for only 39 users and Office 365 apps only; no structured MDM, EDR or disk encryption.
  • Introduce Zero Trust without blocking developers, whose toolchain is sensitive to aggressive security rules.
  • Manage coexistence between Active Directory, Entra ID, GPOs and Intune during the transition.

The solution

  • Controlled Hybrid Join via GPO, Intune auto-enrollment and a static/dynamic group model to move from pilot to production.
  • Zero-touch provisioning with Windows Autopilot and 15 packaged apps across two software profiles (General and Development).
  • Patch management with 3 update rings (0 / 2 / 9 days) and Windows 11 on the N-1 release.
  • BitLocker XTS-AES 256, cloud-native Windows LAPS and mandatory device compliance.
  • Defender for Endpoint with 19 ASR rules (14 Block, 5 Audit) and targeted exclusions for developer workstations.
  • Conditional Access with MFA for everyone, legacy auth and geo blocking, Windows Hello for Business Cloud Kerberos Trust.

The outcomes

  • Zero Trust posture: verified identity, verified device (compliance, encryption, EDR) and least privilege.
  • Lower credential-theft risk through passwordless, LSASS protection and local admin password rotation.
  • Less operational work for IT thanks to zero-touch provisioning and automatic software and patch delivery.

Skills demonstrated

  • Modern Workplace and Zero Trust in hybrid scenarios
  • End-to-end endpoint security on the Microsoft Defender stack
  • Identity & Access Management with Entra ID
  • Enterprise application packaging and software delivery
  • Phased rollout and change management

Technology stack

  • Microsoft Intune
  • Windows Autopilot
  • Defender for Endpoint
  • Attack Surface Reduction
  • Conditional Access
  • Windows Hello for Business
  • Entra Connect
  • Hybrid Join
  • BitLocker
  • Windows LAPS
  • Windows Update for Business
  • Win32 App Packaging
  • Networking
  • Virtual Desktop
  • Security & Zero Trust

Secure remote access: Always On VPN and Azure Virtual Desktop

Transparent Device Tunnel on an Azure VPN Gateway concentrator, virtual desktops and RemoteApp publishing of a legacy application with FSLogix and Azure Files.

Industry
Central public administration
Scope
VPN up to ~500 connections · AVD Full Desktop and RemoteApp
Role
Architect · team delivery
Complexity
Medium-high

Together with the team we designed and delivered a secure remote access program for a public body, built on two complementary services: Always On VPN Device Tunnel with Azure VPN Gateway as concentrator and Azure Virtual Desktop in Full Desktop and RemoteApp. Domain PCs connect transparently to the internal network with a machine certificate, while a legacy application tied to Internet Explorer becomes available remotely.

VPN connections at scale
~500
Networks routed in the tunnel
17
Remote access services
3
  • Always On VPN
  • Device Tunnel / IKEv2
  • Azure VPN Gateway
  • Internal Load Balancer
  • AD Certificate Services
  • Configuration Manager
  • Azure Virtual Desktop
  • RemoteApp
  • +4
Challenge, solution and outcomes

The challenge

  • Provide transparent, scalable remote access, from fewer than 250 pilot connections to about 500 at scale.
  • Overcome native Windows VPN limits: at most 25 IKEv2 routes, no NRPT for DNS and proxy in the Device Tunnel.
  • Make a legacy, Internet Explorer-only application available remotely while keeping cloud costs under control.

The solution

  • Azure VPN Gateway (VpnGw2) as concentrator instead of RRAS/NPS: only 2 VMs to manage instead of at least 4.
  • Dedicated gateway linked to the hub over IPsec, split tunneling with 17 routed networks and machine certificates from the Enterprise PKI.
  • VPN profile deployed with SCCM and dedicated DNS/proxy on 2 VMs behind an Internal Load Balancer, with 3 resolution modes.
  • Windows 10 multi-session golden image with 10 apps, FSLogix on Azure Files and App Masking for the legacy application.
  • Scaling Plan and Start VM on Connect to optimize Azure Virtual Desktop costs.
  • 4-step migration from the existing VPN and rollback, with technical and functional UAT.

The outcomes

  • Transparent remote access: domain PCs connect automatically and remain manageable off-site.
  • Security by design: access only from devices with the organization's certificate, IKEv2 and a segregated access network.
  • Legacy application available remotely with no code changes and a consistent experience across physical and virtual PCs.

Skills demonstrated

  • Secure remote access architectures on Azure
  • Always On VPN, Device Tunnel and VPN Gateway
  • Hybrid networking: routing, DNS and proxy
  • Azure Virtual Desktop, RemoteApp and FSLogix
  • Public sector projects

Technology stack

  • Always On VPN
  • Device Tunnel / IKEv2
  • Azure VPN Gateway
  • Internal Load Balancer
  • AD Certificate Services
  • Configuration Manager
  • Azure Virtual Desktop
  • RemoteApp
  • FSLogix
  • Azure Files
  • Scaling Plan
  • OneDrive Known Folder Move
  • Migration & Assessment
  • Landing Zone & Governance
  • Security & Zero Trust

Azure Assessment and evolution roadmap

End-to-end review of a mature Azure estate and proposal for a new CAF Landing Zone, with wave-based migration and a Zero Trust approach.

Industry
Contract catering
Scope
48 VMs · 16 Azure SQL databases · 14 PaaS apps
Role
Architect · team delivery
Complexity
Medium-high

Together with the team we ran a full assessment of an Azure estate that had grown over time, analyzing 11 areas across 48 VMs, 16 SQL databases and 14 PaaS apps. The findings led to an evolution roadmap: a new Landing Zone per the Cloud Adoption Framework, with workloads migrated in waves and modernized toward PaaS and containers under a Zero Trust model.

Areas analyzed
11
VMs assessed
48
Idle VMs to decommission
20
  • Cloud Adoption Framework
  • Azure Landing Zone
  • Well-Architected Framework
  • Azure Policy
  • Hub & Spoke
  • Azure Firewall
  • Web Application Firewall
  • Private Link
  • +4
Challenge, solution and outcomes

The challenge

  • Large estate on a single subscription, with no Management Groups, Azure Policy or structured governance.
  • Critical risks: retiring services (MariaDB, Basic IPs), non-privatized resources, standing privileges and incomplete backups.
  • Turn findings into a concrete proposal that cuts risk and cost without disrupting operations.

The solution

  • End-to-end assessment of 11 areas: subscriptions, identity, networking, IaaS, PaaS, applications, data, security, governance and cost.
  • New CAF Landing Zone with hub & spoke, perimeter firewall, NSG/ASG segmentation and zone redundancy.
  • Progressive wave-based migration with rehost / rebuild / refactor assessment toward PaaS and containers.
  • MFA for everyone, Azure Firewall and WAF, PaaS privatization with Private Link and Defender for Cloud.
  • Migration from Azure Database for MariaDB to MySQL and evaluation of Microsoft Fabric for the data platform.

The outcomes

  • Complete visibility over the estate, with risks made explicit and prioritized on objective evidence.
  • Clear roadmap toward a CAF Landing Zone with wave-based migration, modernization and Zero Trust.
  • Savings levers identified: 20 deallocated VMs to decommission, 3 VMs to resize and Reserved Instances.

Skills demonstrated

  • End-to-end Azure assessment of brownfield estates
  • Cloud Adoption Framework and Well-Architected Framework
  • Cloud security and governance
  • FinOps: right-sizing and waste removal
  • Migration strategy and executive communication

Technology stack

  • Cloud Adoption Framework
  • Azure Landing Zone
  • Well-Architected Framework
  • Azure Policy
  • Hub & Spoke
  • Azure Firewall
  • Web Application Firewall
  • Private Link
  • Defender for Cloud
  • Azure SQL
  • Azure Database for MySQL
  • Microsoft Fabric
  • Storage & Backup
  • Migration & Assessment

File Server refresh and hybrid backup with Veeam and Azure

New VMware cluster, Dell EMC Unity XT storage, block-level migration of ~27 TB and protection with Veeam File Share Backup and five-year archiving on Azure.

Industry
Fashion & apparel
Scope
5 file servers · 19 volumes · ~27 TB
Role
Architect · team delivery
Complexity
Medium-high

Together with the team we designed and delivered the File Server refresh of a fashion group: a new VMware vSphere 7.0 cluster, a Dell EMC Unity XT 380 array sized for 5 years and block-level migration of 5 file servers and ~27 TB of data. Protection relies on Veeam Backup & Replication with 28-day local retention and 5-year archiving on Azure.

Data migrated at block level
~27 TB
Veeam backup jobs
13
Archiving on Azure
5 years
  • VMware vSphere 7.0
  • Dell PowerEdge
  • Dell EMC Unity XT 380
  • Fibre Channel SAN
  • Synchronous Replication
  • SAN Copy Pull
  • Veeam Backup & Replication
  • Veeam File Share Backup
  • +3
Challenge, solution and outcomes

The challenge

  • 5 file servers on VMware 5.5 with 19 volumes and ~26.8 TB used, many close to full.
  • Data on two arrays of different generations, with capacity and protection no longer adequate.
  • File servers embedded in core applications: migrate tens of TB with minimal disruption and full backup within 24 hours.

The solution

  • 5-year capacity planning with 15% yearly growth, from ~26.8 TB to ~54 TB used.
  • VMware vSphere 7.0 cluster with 3 hosts (72 cores, 384 GB RAM) on 16 Gbps Fibre Channel.
  • Dell EMC Unity XT 380 with differentiated tiers: all-flash, auto-tiering and Nearline SAS for backup.
  • Block-level SAN migration with synchronous replication and SAN Copy Pull, with failback always available.
  • Veeam Backup & Replication with 13 jobs, File Share Backup and five-year archiving on Azure Blob Storage.

The outcomes

  • Capacity secured for 5 years on a modern, supported platform.
  • Migration with no file-level copies and failback available, reducing risk and downtime.
  • Structured protection: daily incremental backup, granular restore and long-term archiving on Azure.

Skills demonstrated

  • VMware vSphere and Fibre Channel SAN design
  • Multi-year capacity planning
  • Block-level storage migration with failback planning
  • Veeam backup architectures and hybrid archiving on Azure
  • Coordinating team-based technical delivery

Technology stack

  • VMware vSphere 7.0
  • Dell PowerEdge
  • Dell EMC Unity XT 380
  • Fibre Channel SAN
  • Synchronous Replication
  • SAN Copy Pull
  • Veeam Backup & Replication
  • Veeam File Share Backup
  • Scale-Out Backup Repository
  • Azure Blob Storage
  • Windows Server File Server
  • Identity & Access
  • Security & Zero Trust

Privileged Identity Management and Just-in-Time Administration

From 100+ standing admin role assignments to a PIM for Groups model with time-bound elevation, Authentication Context MFA and governed break glass accounts.

Industry
Digital publishing & services
Scope
102 standing assignments · 23 roles
Role
Architect · assessment & design
Complexity
Medium

As Cloud Solution Architect I led the design of the privileged access model on Microsoft Entra ID for an enterprise organization with 102 standing assignments across 23 roles, including 10 Global Administrators. The design introduces Just-in-Time administration with PIM for Groups, elevation MFA through Authentication Context, an approval workflow and two governed break glass accounts; the configuration was then implemented by the customer's team.

Initial standing assignments
102
PIM role-assignable groups
21
Governed break glass accounts
2
  • Microsoft Entra ID P2
  • Privileged Identity Management
  • PIM for Groups
  • Conditional Access
  • Authentication Context
  • Role-assignable Groups
  • Microsoft Authenticator
  • Break Glass Accounts
Challenge, solution and outcomes

The challenge

  • 102 standing privileged role assignments across 23 roles, with 10 Global Administrators.
  • Drastically reduce standing privileges without blocking the admin teams' day-to-day work.
  • Introduce JIT and elevation MFA with a model that is simple to run and aligned with Microsoft best practices.

The solution

  • Full review of assignments and removal of unnecessary direct privileges.
  • PIM for Groups model with 21 cloud-only role-assignable groups, one per role.
  • Time-bound elevation with mandatory justification for every activation.
  • Dedicated Conditional Access policy with Authentication Context: MFA required at elevation time.
  • Two cloud-only break glass accounts with a 90-day verification cycle and a password split into 3 parts.

The outcomes

  • Privilege exists only when needed and for a limited time.
  • Reduced attack surface on admin identities, with traceable activations.
  • Group-based management that scales to new admins and roles, with verified emergency access.

Skills demonstrated

  • Identity & Access Management with Entra ID
  • Privileged Access Management and Just-in-Time
  • Conditional Access and Authentication Context
  • Zero Trust applied to admin identities
  • Security operations processes

Technology stack

  • Microsoft Entra ID P2
  • Privileged Identity Management
  • PIM for Groups
  • Conditional Access
  • Authentication Context
  • Role-assignable Groups
  • Microsoft Authenticator
  • Break Glass Accounts
  • Identity & Access
  • Security & Zero Trust

Identity & Security Hardening: PKI, Windows LAPS and Entra ID

A three-workstream program to secure certificates, local admin credentials and privileged identities in a hybrid Active Directory + Microsoft 365 environment.

Industry
Pharmaceutical · Life Sciences
Scope
3 workstreams · hybrid AD + Microsoft 365
Role
Architect · team delivery
Complexity
Medium

As Cloud Solution Architect I coordinated, together with the team, a three-workstream hardening program: a two-tier Microsoft PKI with an offline Root CA and auto-enrollment, remediation of privileged roles in Entra ID down to at most 5 cloud-only Global Administrators, and Windows LAPS for local admin and domain controller DSRM passwords.

Coordinated workstreams
3
Cloud-only Global Admins
≤ 5
Certificate templates
4
  • AD Certificate Services
  • Two-Tier PKI
  • Offline Root CA
  • Windows LAPS
  • Group Policy
  • Microsoft Entra ID
  • Microsoft Authenticator
  • Entra Connect
  • +3
Challenge, solution and outcomes

The challenge

  • Raise identity and credential security in a live hybrid environment without disrupting critical services.
  • Reduce the number and risk of Global Administrators while keeping the Microsoft 365 tenant operational.
  • Protect the Root CA key and manage certificates at scale.

The solution

  • Two-Tier PKI with an offline Root CA and Enterprise Subordinate CA, RSA 4096-bit / SHA-256 keys.
  • Auto-enrollment via Group Policy with 4 certificate templates built on real use cases.
  • Global Administrators reduced to ≤ 5 named cloud-only accounts and unused privileged roles removed.
  • SMS MFA replaced with Microsoft Authenticator for admins and least privilege for service accounts.
  • Windows LAPS for clients and domain controller DSRM passwords, with a controlled pilot.
  • Risk analysis of Entra Connect and AD FS with modernization recommendations.

The outcomes

  • Privileged identities under control: few Global Administrators, named cloud-only accounts only.
  • Lower credential-theft risk: app-based MFA, unique rotated local passwords, DSRM no longer static.
  • Internal PKI ready to support future projects.

Skills demonstrated

  • Hybrid Identity & Access Management
  • Two-tier Microsoft AD CS PKI
  • Privileged access hardening
  • Windows LAPS and credential protection
  • Production delivery and change management

Technology stack

  • AD Certificate Services
  • Two-Tier PKI
  • Offline Root CA
  • Windows LAPS
  • Group Policy
  • Microsoft Entra ID
  • Microsoft Authenticator
  • Entra Connect
  • AD FS
  • Windows Server 2022
  • PowerShell
  • Modern Workplace
  • Identity & Access
  • Security & Zero Trust

Modern Device Management with Intune, SCEP and Entra Application Proxy

Multi-platform pilot: Hybrid and Entra Join, Autopilot, NDES/SCEP published with no firewall openings, Conditional Access and SSPR.

Industry
Cultural foundation · non-profit
Scope
Multi-platform pilot · Microsoft 365 A5
Role
Architect · team delivery
Complexity
Medium

Together with the team we designed and delivered the introduction of Microsoft Intune in a hybrid environment, validating the full modern management chain on Windows, iOS and Android as a pilot. The distinctive element: SCEP certificates from the internal CA to off-network devices, with NDES published through Entra Application Proxy on redundant connectors and no firewall ports opened.

Technical streams
12
SCEP certificate profiles
5
Firewall ports opened for NDES
0
  • Microsoft Intune
  • Windows Autopilot
  • Hybrid Entra Join
  • Entra Application Proxy
  • NDES / SCEP
  • Intune Certificate Connector
  • Conditional Access
  • SSPR
  • +3
Challenge, solution and outcomes

The challenge

  • Introduce cloud device management without impacting production, validating every component on an isolated scope.
  • Deliver internal PKI certificates to off-network devices without new firewall rules.
  • Manage heterogeneous platforms with different ownership and privacy models.

The solution

  • 12 technical streams with a shared naming convention and one security group per stream, to scale from pilot to production.
  • Controlled Hybrid Join and Windows Autopilot with two profiles (Hybrid Join and Entra Join).
  • NDES and Intune Certificate Connector published with Entra Application Proxy on 2 redundant connectors.
  • 5 SCEP certificate profiles, certificate-based Wi-Fi and OneDrive Known Folder Move.
  • Compliance Policy, Conditional Access on MFA + compliant device and SSPR with password writeback.
  • Corporate and personal iOS and Android Enterprise Work Profile.

The outcomes

  • Modern management foundations validated on every platform and ready for mass rollout.
  • Certificates available off-site with an unchanged perimeter attack surface.
  • Access conditioned on MFA and device compliance, ready for enforcement.

Skills demonstrated

  • Multi-platform device management
  • Hybrid identity and Hybrid Join
  • PKI, NDES and SCEP certificates
  • Secure publishing with Entra Application Proxy
  • Structured pilot projects

Technology stack

  • Microsoft Intune
  • Windows Autopilot
  • Hybrid Entra Join
  • Entra Application Proxy
  • NDES / SCEP
  • Intune Certificate Connector
  • Conditional Access
  • SSPR
  • Android Enterprise
  • iOS / iPadOS
  • OneDrive Known Folder Move
  • Storage & Backup

Hybrid file server with Azure File Sync and Cloud Tiering

From file server analysis to design and production rollout: Azure Files sync, tiering of rarely used data and agentless backup with Azure Backup.

Industry
Industrial automation
Scope
1 file server · 8 TB volume
Role
Architect · team delivery
Complexity
Medium

Together with the team we took Azure File Sync with Cloud Tiering into production on a file server, following a POC that had validated the technology. The result is a hybrid file server: the full copy of the data lives in Azure Files, only "hot" data stays on-premises and protection is handled by Azure Backup with no on-premises agents.

Synced volume
8 TB
Deduplication savings
2.46 TB
Backup retention
10 years
  • Azure File Sync
  • Cloud Tiering
  • Azure Files
  • Storage Sync Service
  • Azure Storage GPv2
  • Azure Backup
  • Recovery Services Vault
  • Windows Server 2019
  • +1
Challenge, solution and outcomes

The challenge

  • 8 TB volume (~9.4 TB logical before deduplication) with data heavily used at first and then kept as history.
  • Server resources (2 vCPU, 8 GB RAM) inadequate for current and future load.
  • Free up on-premises space and simplify protection without changing the user experience.

The solution

  • File server assessment and resource upgrade from 2 vCPU / 8 GB to 8 vCPU / 32 GB RAM.
  • Storage Sync Service, Sync Group and Cloud Endpoint on Azure Files holding a full copy of every file.
  • Cloud Tiering with a 20% free space policy and a 1-year date policy.
  • Agentless Azure Backup with Recovery Services Vault and GFS retention (30 days · 10 weeks · 12 months · 10 years).

The outcomes

  • Full, always up-to-date copy of the data in Azure Files.
  • Local space under control with no change to paths or user habits.
  • Cloud-native backup with retention up to 10 years and no load on the local server.

Skills demonstrated

  • Hybrid storage with Azure File Sync and Azure Files
  • File server assessment and data analysis
  • Azure Backup and GFS retention
  • Cloud Adoption Framework and FinOps
  • Design and as-built documentation

Technology stack

  • Azure File Sync
  • Cloud Tiering
  • Azure Files
  • Storage Sync Service
  • Azure Storage GPv2
  • Azure Backup
  • Recovery Services Vault
  • Windows Server 2019
  • Data Deduplication
  • Migration & Assessment
  • Landing Zone & Governance

Hyper-V assessment and Azure migration roadmap

On-premises current-state analysis, migration blockers and an adoption path based on the Cloud Adoption Framework.

Industry
Multi-site private company
Scope
2 Hyper-V hosts · 2 application islands
Role
Architect · assessment & design
Complexity
Medium

Together with the team we assessed the Hyper-V infrastructure of a site data center to define the vision and strategy for migrating to Azure. The analysis of identity, network, virtualization and applications identified 5 blockers to remove before migration and a structured path based on the Cloud Adoption Framework.

Migration blockers
5
Core areas analyzed
4
CAF phases
4
  • Microsoft Hyper-V
  • Windows Server
  • Active Directory
  • Cloud Adoption Framework
  • Azure Landing Zone
  • Azure Virtual Desktop
  • Azure Files
Challenge, solution and outcomes

The challenge

  • Domain based on Small Business Server 2011, the main scalability and security constraint.
  • Flat, unsegmented network and limited WAN connectivity.
  • Two monolithic application islands dependent on vendor support.

The solution

  • 5-phase assessment across 4 core areas: identity, network, Hyper-V and applications.
  • 5 blockers identified: connectivity, monolithic applications, barcode terminals, AD domain and file servers.
  • 4-phase CAF path: Strategy, Plan, Ready, Adopt.
  • Greenfield landing zone to avoid carrying identity and network limits into the cloud.
  • Evaluation of Azure Virtual Desktop and Azure Files as the target model.

The outcomes

  • Clear picture of the current state, with constraints made explicit.
  • Migration prerequisites identified early, reducing surprises during the project.
  • Roadmap aligned with the Cloud Adoption Framework and ready for the design phase.

Skills demonstrated

  • On-premises infrastructure assessment
  • Migration planning and Cloud Adoption Framework
  • Azure landing zone design
  • Risk and prerequisite analysis
  • Presenting findings to stakeholders

Technology stack

  • Microsoft Hyper-V
  • Windows Server
  • Active Directory
  • Cloud Adoption Framework
  • Azure Landing Zone
  • Azure Virtual Desktop
  • Azure Files
  • Identity & Access
  • Networking
  • Security & Zero Trust

Secure web portal publishing with Entra Application Proxy

From firewall NAT to a cloud reverse proxy: redundant connectors in Azure across Availability Zones, custom domain and split-brain DNS.

Industry
Healthcare
Scope
1 published web portal · 2 connectors
Role
Architect · team delivery
Complexity
Medium-low

Together with the team we designed and delivered the internet publishing of a booking portal through Microsoft Entra Application Proxy, removing direct exposure through NAT. Two connectors on Azure VMs in different Availability Zones, a custom domain, a public certificate and split-brain DNS keep access unchanged for internal users.

Inbound firewall ports
0
Connectors across AZs
2
Published portal
1
  • Entra Application Proxy
  • Microsoft Entra ID
  • Connector Groups
  • Azure Virtual Machines
  • Availability Zones
  • Split-brain DNS
  • TLS Certificates
Challenge, solution and outcomes

The challenge

  • Keep the portal available on the internet with no inbound ports open on the perimeter.
  • Ensure high availability of the publishing path.
  • Keep the public address and internal users' direct access unchanged.

The solution

  • Entra Application Proxy as a managed reverse proxy instead of DNAT publishing.
  • 2 connectors on Azure VMs in different Availability Zones, in a dedicated connector group.
  • Custom domain with a public TLS certificate and split-brain DNS.
  • Passthrough pre-authentication for external users not managed in Entra ID.
  • Documented procedures for certificate renewal and admin roles.

The outcomes

  • Reduced attack surface: no NAT exposure and no inbound ports.
  • Resilient publishing path with connectors across Availability Zones.
  • No user impact and a platform ready for Conditional Access.

Skills demonstrated

  • Secure application publishing
  • Resilient architectures with Availability Zones
  • Public and split-brain DNS
  • TLS certificate lifecycle
  • Operational documentation

Technology stack

  • Entra Application Proxy
  • Microsoft Entra ID
  • Connector Groups
  • Azure Virtual Machines
  • Availability Zones
  • Split-brain DNS
  • TLS Certificates
  • Landing Zone & Governance
  • Networking

NVIDIA Omniverse Proof of Concept on Azure

A lean landing zone in the Italy North region to host NVIDIA Omniverse: remote-streaming VM, NSG-protected network, storage for working files and backup.

Industry
ICT · System integration
Scope
1 dedicated subscription · 1 application VM
Role
Architect · team delivery
Complexity
Medium-low

Together with the team we designed and built the Azure infrastructure for an NVIDIA Omniverse Proof of Concept on a deliberately lean landing zone. The environment is isolated, cost-contained and documented with recommendations to evolve toward a CAF-aligned production setup.

Dedicated subscription
1
Resource groups
5
Inbound NSG rules
8
  • NVIDIA Omniverse
  • Azure Virtual Machines
  • Azure Virtual Network
  • Network Security Group
  • Azure Storage
  • Azure Backup
  • Azure RBAC
  • Cloud Adoption Framework
Challenge, solution and outcomes

The challenge

  • Evaluate NVIDIA Omniverse in the cloud with a quick, isolated environment and no hardware investment.
  • Allow both administration and remote streaming while exposing only the required ports.

The solution

  • Dedicated subscription with 5 resource groups by function and CAF-aligned naming.
  • VNet with NSG: admin access limited to 2 authorized IPs, dedicated streaming rules and default deny-all.
  • Storage Account for working files and Azure Backup with a dedicated policy.
  • Documented recommendations on MFA, PIM and risk-based access.

The outcomes

  • Operational POC environment with no hardware investment.
  • Controlled exposure with admin access restricted to known sources.
  • An orderly foundation ready to evolve toward production.

Skills demonstrated

  • Azure IaaS infrastructure for specialized workloads
  • Landing zones and CAF conventions
  • Network security with NSG
  • POC-first approach built to evolve

Technology stack

  • NVIDIA Omniverse
  • Azure Virtual Machines
  • Azure Virtual Network
  • Network Security Group
  • Azure Storage
  • Azure Backup
  • Azure RBAC
  • Cloud Adoption Framework

Working on something similar?

If you're facing a similar challenge on Azure, reach out on LinkedIn.

Learn more about me