Logic Apps, Functions, Service Bus, Event Grid or API Management?

Azure has five services that all look like "integration". A plain guide to what each one is for, and how they fit together in an event-driven integration platform.

When teams start connecting business systems on Azure, the first question is usually which service to use. The answer is usually several of them, each doing one job.

Service Use it for Avoid it for
Logic Apps Workflows that connect systems, using built-in connectors, with a visual history of every run Heavy data transformation or complex logic
Azure Functions Custom code: transformations, validation, calls to APIs without a connector Long orchestration that's easier to see as a workflow
Service Bus Reliable business messages between systems: queues, topics, ordering with sessions, dead-lettering Broadcasting simple notifications to many listeners
Event Grid Reacting to events such as "a file arrived" or "an order changed", pushed to many subscribers Messages that must be processed exactly in order
API Management One secure front door for your APIs: authentication, rate limits, versioning, documentation Business logic of any kind

How they fit together

A typical event-driven flow looks like this:

  1. A source system calls an API published through API Management, or raises an event through Event Grid.
  2. The message lands on a Service Bus topic, so it's stored durably even if downstream systems are down.
  3. A Logic App picks it up and runs the workflow: look up reference data, call the target system, handle approvals.
  4. Where the workflow needs real code, it calls an Azure Function.
  5. Failures go to the dead-letter queue, where they're monitored and replayed instead of lost.

Legacy systems are part of the picture

Most estates still include older integration platforms such as BizTalk, or systems that exchange files in their own formats. Modernization rarely means switching them off on day one. Hybrid integrations let the old and new platforms exchange messages while flows move across one at a time.

The rules that keep it maintainable

  • Every integration flow has an owner, documentation and monitoring.
  • Messages carry a correlation ID from end to end, so one business transaction can be traced across all five services.
  • Systems talk to the integration platform, never directly to each other. That's what stops point-to-point connections from creeping back.

Dealing with this in your own system? We do this work for a living. The first call is free.

Book a call