Are you an official Microsoft Partner?
No. We are an independent builder agency that works extensively with Azure, but we do not present ourselves as a Microsoft Partner or Solutions Partner with a specific designation. For some clients that is actually an advantage: our advice carries no channel pressure, no partner incentives and no "we have to mention this service because we are a partner". Our value lies in hands-on experience with production workloads on Azure, not in a logo. If you explicitly need a partner relationship, for example for a Microsoft-funded migration programme, we will say so honestly and help you find the right party.
Do you also work with AWS or Google Cloud?
Yes. We have hands-on experience with all three major hyperscalers and see no reason to be dogmatic about choosing one. Azure is often a strong choice for organisations already deep in a Microsoft stack (Active Directory, Microsoft 365, Power Platform, Dynamics), because identity and data integration then become a logical continuation. For organisations without that history, AWS or GCP can be just as suitable. We also advise on where a hybrid or multi-cloud setup makes sense, and where it just adds unnecessary complexity.
How do you deal with vendor lock-in on Azure?
Deliberately. Not by avoiding all managed services, which is often more expensive in build and management costs than the benefit, but by stating the dependency explicitly for every significant service choice. For some workloads, deep Azure integration via Functions, Cosmos DB and Event Grid is perfectly fine; for others, a container approach on AKS is wiser precisely because it could run on Kubernetes elsewhere with limited changes. We weigh this case by case, so there are no hidden dependencies that catch you out years later.
What is an Azure Landing Zone and do we need one?
An Azure Landing Zone (ALZ) is a standardised baseline setup based on Microsoft's Cloud Adoption Framework: a management group hierarchy, a subscription vending approach, a hub-and-spoke network blueprint, baseline policies via Azure Policy, an identity layer in Entra ID and a documented approach to logging and monitoring. For organisations that work with Azure on an ongoing basis, it is almost always the sensible choice — restructuring a messily built Azure environment after the fact is far more expensive than putting a good landing zone in place up front. For very small organisations with a single Azure subscription, a full ALZ is overkill; in that case we recommend a lighter baseline that can grow later.
Which Azure services do you typically work with?
Compute: App Service, AKS, Container Apps and Azure Functions. Data: Azure SQL Database and Managed Instance, Cosmos DB, Azure Storage and Azure Cache for Redis. Edge: Azure Front Door and CDN. Identity: Entra ID for employee access, and Entra External ID or Azure AD B2C for customer-facing authentication. AI: Azure OpenAI Service, Azure AI Foundry and Cognitive Services — see also our
AI development page. Events: Event Grid, Service Bus and Logic Apps. Observability: Azure Monitor, Log Analytics and Application Insights. That is the core; around it we work with countless other services whenever the situation calls for it.
Where do we store data — in which Azure region?
For Dutch clients, usually West Europe (Amsterdam), with North Europe (Dublin) as the secondary region for disaster recovery. For a German focus, Germany West Central (Frankfurt) may be a better fit, and for Scandinavian clients, Sweden Central. What choosing a region does not automatically solve is data leakage via logging, AI or management services that run outside the EU. Since 2024 the Microsoft EU Data Boundary has played a role here — a serious commitment that customer data and diagnostics stay within the EU, but not a licence to skip checking the configuration. That has to be set up separately through service policies, correct Key Vault allocation and deliberate choices around cross-region features. We handle that setup as part of a security baseline.
Do you work with Azure DevOps or GitHub Actions?
Both. Microsoft has Azure DevOps and GitHub under the same roof; in practice we increasingly see GitHub Actions as the primary CI/CD tool, including for Azure deployments — the developer experience is stronger, the community is larger and the Azure integration via the official actions is mature. For organisations that are already deeply invested in Azure DevOps (work items, repos, pipelines), migrating to GitHub doesn't always make sense; in that case we keep working in Azure DevOps. It's not a religion, but we do prefer tooling that the client's developers are comfortable with.
How do you differ from an Azure-only consultancy?
An Azure-only firm often knows the platform inside out — that's where they're strong. We differ in three ways. First, we are vendor-independent, so choosing Azure is the outcome of the analysis, not the starting point. Second, we also build applications, not just infrastructure — which brings the two worlds together under one roof and avoids handovers. Third, our pricing suits mid-market budgets. For an organisation that has already chosen Azure and only wants platform-specific optimisation, an Azure-only firm can be a perfectly good fit — for those who want to keep advice and build connected, we operate in a different niche.
What determines the cost of an Azure consulting engagement?
Mainly the scope and the complexity of your existing environment. A Well-Architected review for a small, straightforward Azure tenant is a different engagement from an assessment of a multi-subscription environment with dozens of workloads, hub-and-spoke networks and complex Entra ID federations. Depth also plays a part: a quick scan to get the board up to speed is not the same as a fully worked-out restructuring proposal. We work with a fixed sprint budget per phase, so you know where you stand, and we only extend it if you decide to move on to a next phase.
Do you work with our internal cloud or IT department?
Almost always. In the first phase we actively seek contact with your cloud engineers and security officer to understand what is already running, which decisions were made historically and which sensitivities are at play. During delivery we work in mixed teams wherever possible: your people plus ours, with clearly divided ownership. Knowledge transfer is not an afterthought: when we leave, your team must be able to manage and further develop the Azure environment independently.
How does a programme start in practice?
With an introductory conversation, no obligation. We listen to your situation and advise which form fits best: a review, an architecture design or guided implementation. For a review, we first get read access to the Azure tenant so that we can base our proposal on facts, not assumptions.