Independent Microsoft Azure consultant in the Netherlands

Architectural view, not vendor catalog

Decisions on landing zone, identity, networking and data residency are taken on the merits of your context, not based on what a partner needs to sell this quarter. No artificial vendor lock-in.

Personal accountability

Same face from first call to delivery. No team rotation, no "the architect who designed this has left the project". The person who proposes a choice is the same one accountable for it eighteen months later.

Knowledge transfer to your team

The goal is to bring your internal architects and platform engineers to a level where they no longer need a consultant, not to make them dependent on one. Documentation, decisions and operational capability stay inside.

Engagement model

Day-rate friendly. Typical setups: focused architectural assessment (a few weeks), fractional architect alongside the internal team, or full delivery on a defined scope. T&M or fixed scope, depending on what fits the decision you need to make.

Contracting setup

Registered Dutch entity (KvK 42083735, VAT NL005481493B60) for local procurement, invoicing in EUR. Open to working through Dutch agencies or detachering structures where your procurement requires it.

Working languages

English (primary) and Italian (native). Comfortable in Dutch professional environments; written and spoken Dutch on my side is limited. All meetings, documentation and delivery happen in English. Honest about it from day one, not at the first meeting.

Microsoft Azure consulting

Enterprise architectures, landing zones, governance, identity, security and cost control for platforms ready to scale.

Read more →

Cloud migration

Phased migrations to Azure with operational continuity, workload-by-workload assessment and a real rollback strategy.

Read more →

DevOps automation

CI/CD pipelines, Infrastructure as Code and release engineering to reduce lead time and post-release incidents.

Read more →

FinOps & cost optimization

Cost visibility per team, governance, rightsizing, reservations and continuous workload optimization on Azure.

Read more →

DevOps & platform engineering

The core of what I do. Hands-on Azure DevOps Engineer and Azure Platform Engineer: CI/CD, Infrastructure as Code and self-service platforms that cut lead time and post-release incidents. Comfortable in Site Reliability Engineer and Azure Kubernetes Engineer territory when reliability is the bottleneck.

Cloud architecture & infrastructure

Fifteen-plus years as Azure Solutions Architect, Azure Cloud Engineer and Azure Infrastructure Engineer. Landing zones, identity, networking and data residency designed for your context — the architecture an Azure Consultant is actually accountable for eighteen months later.

Security & identity

Security designed into the platform, not bolted on after the audit. Azure Security Specialist and identity work: hardening, monitoring, governance and least-privilege that your CISO and DPO can sign off.

AI & data platform

Data and AI workloads held to the same governance discipline as the rest of the platform. Azure Data Engineer, Azure Data Architect and AI / ML Engineer scope: pipelines, lakehouse and production-grade AI services — not demos that never reach production.

FinOps & cloud sovereignty

Two things Dutch and EU clients increasingly put on the table early: cost accountability as an Azure FinOps Engineer, and a pragmatic cloud sovereignty posture — EU Data Boundary and Microsoft Cloud for Sovereignty applied where they materially reduce risk, skipped where they are only branding.

Data residency

EU-region first by default. West Europe / North Europe as primary regions for Dutch workloads, with explicit decisions on cross-region data flow when the architecture requires it.

GDPR-aware architecture

Identity, logging, backup and lifecycle decisions made with GDPR and DPIA implications in mind. No legal advice — engineering decisions framed in a way your DPO can sign off.

Sovereignty options

Awareness of Microsoft Cloud for Sovereignty and EU Data Boundary. Pragmatic posture: use what materially reduces risk for your sector, skip what is only branding.