Microsoft is giving API developers a simpler path into event-driven systems. The company has introduced a new Azure APIM Service Bus policy that lets teams send messages directly from API Management to Azure Service Bus without writing glue code or deploying extra components. The feature, now in preview, marks a meaningful shift in how organizations connect their API layer to asynchronous workflows.
Previously, integrating APIM with Service Bus required a custom channel adapter — often a Logic App or Azure Function — to accept an HTTP request, reshape the payload, and forward it. The new policy removes that middle layer, reducing latency, cost and architectural friction.
How the new Azure APIM Service Bus policy works
With the send-service-bus-message policy, APIM can forward any incoming API request straight into a Service Bus queue or topic. Instead of treating message publishing as a separate workflow, APIM now handles it natively as part of the inbound pipeline.
Brandon Verzuu, a business architect at ApplyThing, explains the significance in a recent post. According to him, teams no longer need a dedicated adapter whose only job is to take an API call and turn it into a Service Bus message. The policy assumes that responsibility, creating a direct bridge between HTTP-triggered actions and asynchronous consumers.
Meanwhile, Microsoft MVP Luke Murray demonstrated what the policy looks like in practice, showing how developers can enrich messages with metadata such as API names, operations, client IPs and timestamps. The policy then pushes both the metadata and the original payload into the configured queue.
Use cases that benefit from first-class messaging
Microsoft outlined several scenarios where the Azure APIM Service Bus policy becomes particularly useful. Event notifications are an obvious example: APIM can capture a REST call and fan it out to internal systems that rely on asynchronous triggers. Partner integrations are another, allowing organizations to expose REST endpoints publicly while preserving internal event-driven contracts behind the scenes.
However, the shift isn’t just functional. By using managed identities, APIM can authenticate securely against Service Bus without storing connection strings or secrets. Teams also retain all APIM advantages: rate limits, quotas, access control, transformation rules, and detailed logging for every dispatched message.
Cloud Solutions Architect Stefan van der Loop welcomed the change, adding that the feature makes decoupled designs “much easier and more robust.” He also pointed to today’s compound SLA of 99.8 percent, suggesting that higher guarantees would make the approach even more production-friendly.
A step forward for event-driven architecture on Azure
The preview underscores Microsoft’s broader strategy: streamline integration patterns, reduce architectural overhead and make asynchronous systems easier to adopt. While the Azure APIM Service Bus policy won’t eliminate every challenge in event-driven architectures, it removes one of the most common pain points — the need for intermediary compute.
As organizations scale API traffic and move toward more loosely coupled services, this built-in capability could quickly become a standard part of Azure’s integration toolkit.
Read also
Join the discussion in our Facebook community.