Service · Consultancy

Azure consulting for organisations that want to set up their cloud properly.

Architecture advice and delivery for clients who run on Microsoft Azure or are considering it. We design scalable, secure and cost-efficient Azure environments, and we build them ourselves too. Vendor-independent: we know AWS and GCP just as well, and we won't choose Azure if something else fits better.

Azure Landing ZoneWell-Architected reviewsCost optimisationEntra ID

Advising and building on Azure — no separate tracks.

Azure consulting at Appfront is not an abstract architecture exercise detached from delivery. We have worked with Microsoft Azure for years for clients who run production workloads on the platform — web applications, customer portals, data platforms, integration layers and, increasingly, AI solutions built around Azure OpenAI. The conversations about architecture, security and cost are held with the same people who go on to deliver. That keeps the advice honest and the delivery sharp.

We are a Dutch software development company with a cloud practice. Our position is deliberately independent: we are not a reseller, we have no licence quotas, and we have no incentive to sell you more Azure services than you need. If AWS suits a particular workload better, we will say so. If a hybrid setup is the smartest choice, we will build that. The starting point is always your situation, not a vendor's portfolio.

Azure consulting is an umbrella over several more specific engagements. If you want to approach the cloud more broadly or haven't yet chosen a provider, you can start with broader digital consulting. If you have just decided to move to the cloud, you often begin with cloud migration support. And if you are still choosing a platform, see also the parallel page on AWS consulting — the same principles, different tools.

What we mean by Azure consulting.

The question "do you do Azure consulting?" breaks down into very different areas of work. Below are the six that come up most often in our practice — in different proportions in every engagement.

Architecture

Cloud architecture design

An Azure design that fits your workload: which services, how they are distributed across subscriptions and management groups, with which network segmentation via virtual networks and which redundancy approach via availability zones or paired regions. Not a reference architecture from a whitepaper, but a design that fits your traffic pattern, team size and growth assumptions.

Review

Well-Architected reviews

A structured review of an existing Azure environment along the pillars of the Microsoft Azure Well-Architected Framework: reliability, security, cost optimisation, operational excellence and performance efficiency. We dig into the Bicep or Terraform code, the RBAC assignments and the runtime metrics in Azure Monitor. At the end you receive a prioritised list with concrete next steps.

Costs

Cost optimisation

Azure bills tend to grow in a way that rarely feels linear to the business. We analyse where the money really goes — over-provisioned virtual machines, poorly matched managed disk tiers, unused public IPs, missing Reservations or Savings Plans, expensive egress caused by badly placed resources — and build an approach to realise the worthwhile savings on a lasting basis.

Security

Security & Entra ID

A good Azure tenant differs enormously from a mediocre one in its security foundation. A multi-subscription strategy via management groups and Azure Policy, an identity layer in Entra ID with conditional access and privileged identity management, encryption via Key Vault, segmentation via NSGs and private endpoints, logging via Log Analytics and Microsoft Defender for Cloud. We work from a clear information security policy — not from a checklist applied afterwards.

Migration

Migration to Azure

From on-premises, from AWS or from a SaaS context. We map the existing landscape, choose the right migration strategy for each workload (rehost, replatform, refactor or replace), and build the migration path without bringing the business to a halt. For the broader migration context, see cloud migration support.

Modernisation

Containers, serverless & events

If you already run on Azure but have a lot of lift-and-shift workloads, modernising can pay off: containerised services via AKS or Container Apps, event-driven flows via Event Grid and Service Bus, short transactions on Azure Functions, an API layer via API Management. Not as an end in itself, but where it makes things simpler, cheaper or more robust than your current setup.

Three ways we deliver Azure consulting.

It depends on where your Azure practice stands and which decision you have on the table. We decide together in the first conversation which format fits. A engagement often starts with a review and grows into an implementation phase.

Compact project · fixed sprint budget

Azure Well-Architected review

A structured scan of your existing Azure environment across the five pillars of the Microsoft Well-Architected Framework. We look at RBAC assignments, network topology, cost drivers, observability via Log Analytics and Application Insights, backup strategy and deployment pipelines. At the end you get a findings report plus a prioritised list: not an endless document, but concrete improvements your team can start on tomorrow.

Five pillarsRBAC auditCost scanQuick wins
Mid-sized project · fixed sprint budget

Azure Landing Zone and architecture design

A design for a new Azure environment or a redesign of an existing one. An Azure Landing Zone (ALZ) following the Cloud Adoption Framework: management group hierarchy, subscription vending, hub-and-spoke network, identity baseline in Entra ID, baseline policies via Azure Policy and an IaC approach using Bicep or Terraform. The result is an environment where your teams can build safely and predictably.

Azure Landing ZoneManagement groupsBicep/TerraformAzure Policy
Ongoing engagement · sprint-based

Guided implementation and modernisation

Strategy without execution stays theory. In this engagement we guide not only the architecture choices but also the delivery: migrating workloads, CI/CD via Azure DevOps Pipelines or GitHub Actions, modernising to AKS, Container Apps or Functions, and observability via Azure Monitor, Application Insights and Log Analytics. We stay on board until it works in production and your team can carry on building independently.

CI/CDAKSAzure FunctionsApp Insights

Which Azure services we use in practice.

Azure now has hundreds of services and the portfolio grows every quarter. Honestly: no one knows everything in detail, and neither do we. What we do is deliberately focus on the services we work with structurally in client projects, and we have in-depth practical knowledge of those. The rest we learn as needed within the scope of a specific project.

For compute, App Service is often the starting point, with Azure Kubernetes Service (AKS) where the team has Kubernetes maturity and Container Apps for managed containers with less operational overhead. Azure Functions for event-driven or short-running code, with API Management as the front layer. For data: Azure SQL Database and Managed Instance, Cosmos DB for document and key-value stores that need to be globally distributed, and Azure Storage (Blob, Files, Queues, Tables) for object storage. Azure Front Door and CDN for edge distribution.

For security and identity, we use Entra ID (formerly Azure Active Directory) for workforce identity and Entra External ID or Azure AD B2C for customer-facing authentication, Key Vault for secrets and certificates, and Microsoft Defender for Cloud for security posture monitoring. For AI workloads, Azure OpenAI Service and Azure AI Foundry are the two services we work with most: Azure OpenAI for managed access to GPT and embedding models, plus Cognitive Services for vision and speech pipelines. For event-driven architecture, we rely on Event Grid, Service Bus and Logic Apps; for observability, on Azure Monitor with Log Analytics and Application Insights. For an AI project on Azure, see AI development for our broader practice.

What you get from an Azure engagement.

No vague deliverables, but artefacts your cloud team, security officer and business owners can put to use straight away.

  • Architecture documentA readable overview of the Azure services chosen, how they work together, which trade-offs were made and why. Not just a diagram, but the reasoning behind it.
  • Infrastructure as codeA Bicep or Terraform repository that describes the environment. Reproducible, versioned and linked to your CI/CD via Azure DevOps or GitHub Actions, with no manual portal clicks that nobody can reconstruct later.
  • Azure Landing Zone baselineA management group structure, a subscription vending approach, a hub-and-spoke network, baseline policies via Azure Policy and a documented runbook for safely adding new subscriptions, identities and workloads.
  • Identity and security baselineEntra ID tenant setup, least-privilege RBAC, conditional access, Privileged Identity Management, a Key Vault strategy and Defender for Cloud onboarding. Plus a clear picture of who is allowed to do what.
  • Cost overview and optimisation planInsight into where the money is actually going via Microsoft Cost Management, plus a concrete list of measures, from VM rightsizing to Reservations and Savings Plans, that make a structural difference.
  • CI/CD and observability setupWorking deployment pipelines via Azure DevOps Pipelines or GitHub Actions, plus the monitoring around them (Azure Monitor dashboards, alerts, Application Insights, Log Analytics), so production incidents become visible before your customers report them.
  • Hands-on build role (optional)If you wish, we stay on board as a delivery partner for the migration, the modernisation work or further development on the new environment. That way, advice and execution stay with the same people.

When Azure consulting makes a difference.

Six situations in which clients come to us for Azure work. If you recognise one, we'd be glad to talk further. A no-obligation conversation is enough to see whether the chemistry is right.

Greenfield

A new environment for a new product

You're starting a new platform and have chosen Azure as the foundation, often because your existing Microsoft stack (Entra ID, Microsoft 365, on-prem Active Directory) makes it a logical choice. You want to get it right first time: a clean subscription structure, IaC via Bicep or Terraform, an identity baseline in Entra ID, deployment pipelines. Not a messy proof of concept that later has to be laboriously cleaned up, but a foundation on which the team can be productive straight away.

Audit

The bill is higher than it should be

You're already running on Azure, but the monthly bill has structurally risen above what the business expected. You suspect overcapacity, badly placed resources (expensive egress!), overpriced managed disk tiers or missing Reservations, but you don't have the exact picture. A Well-Architected review focused on the cost pillar puts the insight on the table and gives you levers to make a structural difference.

Compliance

GDPR, DORA, NIS2 or NEN pressure

Your sector sets requirements for data residency, logging and incident procedures: GDPR, DORA for financial service providers, NIS2 for essential and important entities, NEN 7510 for healthcare. Your Azure environment must demonstrably comply, and you need a partner who gets the design and the evidence in order. See also ISO 27001-compliant software development for the broader security context.

AI on Azure

Making Azure OpenAI production-ready

You are experimenting with Azure OpenAI and want to take it from prototype to production, with network isolation via private endpoints, content filtering, prompt logging without leaks outside the EU Data Boundary, cost monitoring and a fallback strategy for model deprecations. We have been through this process before and know where the sharp edges are.

Scale

The MVP is outgrowing itself

The platform is running in production, customers are enthusiastic, and growth is outpacing what the architecture was designed for. Single-region becomes multi-region, a handful of containers become dozens, and the original choices are starting to pinch. You need a partner who can take it to the next level of maturity without a major rebuild.

Vendor selection

Azure versus AWS versus GCP

You are about to choose a platform and you don't want a sales pitch. You want an independent analysis that lays out the real trade-offs: costs, talent availability, ecosystem fit (often decisive with Azure: the Microsoft stack integration), compliance evidence and migration flexibility. We also advise on where Azure is not the smartest choice. See also our parallel page on AWS consulting.

EU data residency and compliance on Azure.

For European customers, data residency is often not a detail but a prerequisite. Azure offers several regions within the EU: West Europe (Amsterdam, the default for many Dutch customers because of latency), North Europe (Dublin), Sweden Central, Germany West Central (Frankfurt) and France Central (Paris). Which region fits depends on your customer base, legal context and service availability. Azure OpenAI, for example, is available in fewer regions than classic compute, and not every region has availability zones. Since 2024, Microsoft has also been building the EU Data Boundary: a commitment that customer data and diagnostics stay within the EU for most services. It's no silver bullet, as data can still leak through misconfigured logging, but it is a serious step for anyone with strict data residency requirements.

For financial service providers, the DORA regulation has applied since 2025: digital operational resilience, exit strategies for critical ICT providers and third-party risk management. For healthcare providers, NEN 7510 remains the framework for information security. Essential and important entities face additional obligations under NIS2. And the GDPR applies to all personal data. We design the Azure environment so that it demonstrably supports these frameworks, with evidence that comes structurally from Azure Monitor, Defender for Cloud and Microsoft Purview instead of being compiled by hand when the auditor arrives.

One specific point of attention is vendor lock-in without an exit plan. Some Azure managed services gradually make an organisation hard to move, which isn't necessarily bad, but it is something to decide on consciously. For every significant service choice, we put the dependency explicitly on the table: what would an exit look like, and do the benefits outweigh the portability you give up? For us, vendor independence doesn't mean "not using managed services", but "knowing what you're getting into".

How an Azure consulting engagement works with us.

1

Introduction and scope kick-off

An initial conversation to understand where your Azure practice stands, what decision is on the table and what constraints apply, such as budget, compliance, team skills and timing. After that comes a short proposal phase in which we agree which format (review, architecture design or guided implementation) fits best.

2

Research and discovery

We get read access to your Azure tenant and look at IaC repositories, RBAC assignments in Entra ID, network topology, Cost Management reports and monitoring data from Azure Monitor. We also speak with cloud engineers, your security officer and application owners, not to know everything, but to be able to ask the right questions.

3

Workshops and architecture choices

In a number of focused sessions we put the options on the table: service choices, management group and subscription structure, network blueprint (hub-and-spoke versus virtual WAN), identity and security baseline, and deployment approach. No black-box analysis: your team takes part in the decisions and keeps ownership.

4

Plan and business case

We translate the choices into a phased plan covering sequencing, team deployment and investment. It is concrete enough for the board or the finance team, and flexible enough to adjust as your understanding develops.

5

Delivery (optional)

If you wish, we stay on board for delivery, as a building partner, programme manager or interim cloud engineer. That way advice and delivery stay with the same people, and the engagement only ends once the Azure environment is running in production and your team can continue building on it independently.

Frequently asked questions.

What clients usually ask us before we start: honest answers, no sales talk.

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.

Talk to us about your Azure question.

An introductory conversation, with no obligation and no sales pressure. We listen to your situation, ask questions and give you direction you can actually use, even if it turns out that working with us is not the right next step, or that another cloud provider is a better fit.

Edit content