Integration architecture on Azure

Fewer connections. More control.

Most integration landscapes grow one link at a time until nobody can change anything safely. Our team replaces that web of point-to-point connections with one governed integration layer on Azure, and builds it together with your developers so they can keep it running.

Book an intro call See how we did it for AkzoNobel
15+ years in integration100+ projects deliveredNL · EN · FR · DE
ERP CRM IoT Partner Data Apps ERP CRM IoT Partner Data Apps Integration BEFOREAFTER 15 point-to-point links6 links, one governed layer
Sound familiar?

Signs your integration landscape is holding you back

These are the situations we are usually called in for.

  • A small change takes monthsBecause nobody knows which other interfaces will break.
  • Every system talks to every other systemPoint-to-point connections, each built differently, by different people.
  • Failures are found by users firstNo central monitoring, so errors surface as complaints or missing orders.
  • Legacy middleware nobody wants to touchBizTalk or custom brokers that are end-of-life but still run the business.
  • Teams build APIs, but nobody can find themNo catalogue, no versioning rules, no shared security model.
  • The cloud migration stalled on integrationSystems moved to Azure, but the connections between them did not.
See how we help
What you get

An integration layer you are in control of

One governed layer instead of dozens of separate connections means you can see, secure and change every integration from one place.

Discuss your landscape
Monitoring and alerting
Every message and API call is logged centrally in Azure Monitor and Application Insights. Failures raise an alert to the right team before users notice.
End-to-end tracing
Follow one order, invoice or event across all systems with a shared correlation ID, so you can answer "where is it now?" in minutes, not days.
Governance and ownership
An API catalogue, naming and versioning rules, and a named owner for every integration. Everyone knows what exists, who maintains it and what depends on it.
Security by default
Authentication with Entra ID and OAuth, policies in API Management, secrets in Key Vault and private networking where needed, applied the same way for every interface.
Reliability
Queues, retries, dead-letter handling and idempotent processing. Temporary outages of a system no longer mean lost messages or manual repair work.
Audit and compliance
A traceable record of who exchanged which data and when, to support audits, privacy requirements and partner agreements.
Faster change
Reusable templates, infrastructure as code and CI/CD pipelines. A new integration starts from a proven pattern and goes to production through a repeatable process.
Cost insight
Usage per API, consumer and integration is visible, so you can see what each connection costs and where to optimize.
Featured case

AkzoNobel: from point-to-point sprawl to one global API layer

AkzoNobel's integration landscape had grown into dozens of point-to-point connections. Each one was built in its own way, maintenance was expensive, and there was no consistent way to publish or secure APIs across regions.

We designed a centralized, modular integration approach on Azure with a multi-region Azure API Management setup at its core. Standard patterns for publishing, routing and governance mean new integrations start from a template instead of from scratch, and every region follows the same rules.

Starting point
Dozens of legacy point-to-point integrations with high maintenance overhead
What we built
Multi-region Azure API Management as the central API layer, with shared patterns and governance
Result
Shorter lead times for new integrations, fewer incidents and one governance model across regions
Services

Three ways we can help

You can start with any of these. Many clients begin with a review and continue into design and delivery.

Integration architecture

We map what is running today, design the target architecture and define the standards, patterns and governance to get there, written so developers can actually use them.

Call us whenyou are planning a cloud migration, replacing middleware, or need one direction across several teams.

Azure Integration Services delivery

Our engineers build, migrate and stabilize integrations with Logic Apps, Azure Functions, Service Bus and Event Grid, including infrastructure as code, CI/CD and monitoring.

Call us whenthe design is clear but you need hands to build it, or existing integrations keep failing.

API platform and governance

We set up Azure API Management as a product: design guidelines, versioning, security with Entra ID, a developer portal and the processes that keep it tidy.

Call us whenteams publish APIs in different ways, or partners need secure access to your data.

Approach

From first conversation to a platform that scales

Each phase ends with something your teams can use straight away.

  1. Discover

    Intake, landscape scan and priority mapping with business and IT.

    Landscape overview and a prioritized list of problems

  2. Design

    Target architecture, integration patterns and governance, validated with your architects and developers.

    Architecture, standards and reusable templates

  3. Deliver

    The first use cases built together with your team, including pipelines and monitoring.

    Working integrations in production

  4. Scale

    Standardize, measure and roll out across domains, business units or countries.

    A platform your teams can extend themselves
More client work

Different sectors, the same principles

Utilities, food production, mobility, education, healthcare and life sciences each have their own constraints. The patterns that make integrations manageable stay the same.

Waternet

Real-time data and API governance

An event-driven backbone on Service Bus and Event Grid, with API lifecycle rules shared by all teams.

Vion

Hybrid integration at scale

Cloud and on-prem systems connected with messaging-first patterns and controlled retries, so load peaks are absorbed.

Allego

IoT and fleet data

Integration for a new IoT unit providing real-time monitoring and fleet management.

HAN

Architecture review

An assessment that left teams with guidelines, templates and reference designs they now use themselves.

JDB Groep

Hybrid integration platform

API Management, Logic Apps and on-premises gateways connecting cloud and on-prem systems, ready for an analytics data warehouse.

Lab automation

RabbitMQ architecture review

A messaging review for an international supplier of automated lab equipment, covering quorum queues, HAProxy and client implementation.

Healthcare

Medical voice assistant

A voice-driven platform for medical checks, built on Dialogflow, Logic Apps and Durable Functions.

How we build

Three principles behind every design

01

Small, independent parts

Each integration is its own deployable unit. A change in one domain does not ripple through the rest.

02

Patterns over one-offs

Messaging, API publishing, retries and error handling follow shared templates, so the tenth integration is faster than the first.

03

Governance per module

Ownership, security and monitoring are defined per module, under central rules. Teams stay autonomous, the platform stays manageable.

FAQ

Common questions

Something else? Email us.

Can you help us move off BizTalk or other legacy middleware?

Yes. We inventory the existing interfaces, decide per interface whether to rebuild, replace or retire it, and migrate in stages so the business keeps running.

Do you build, or only advise?

Both. We design the architecture and then build the first integrations with your developers, so the standards are proven in practice before they are rolled out.

Do you only work with Azure?

Azure Integration Services is our focus and where our experience is deepest. We regularly connect Azure to SAP, Dynamics 365, SaaS applications and on-premises systems.

Where do you work?

We are based in the Netherlands and work for clients across Europe, on site and remotely, in Dutch, English, French and German.

Contact

Let's look at your landscape together

No sales pitch. You talk directly with an architect.

  1. You send a short descriptionA few lines about your systems and what is not working.
  2. We plan an intro callAbout 30 minutes to understand the situation and your goals.
  3. You get a concrete proposalScope, approach and a first step you can decide on quickly.
We only use your details to respond.

Thank you. Your request has been sent and we will be in touch soon.

Something went wrong. Please email info@itconnector.nl.