<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Messaging</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Messaging feed</description>
    <item>
      <title>Azure APIM Simplifies Event-Driven Architecture with Native Service Bus Policy</title>
      <link>https://www.infoq.com/news/2025/11/azure-apim-service-bus-policy/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Messaging</link>
      <description>&lt;img src="https://res.infoq.com/news/2025/11/azure-apim-service-bus-policy/en/headerimage/generatedHeaderImage-1762243003474.jpg"/&gt;&lt;p&gt;Microsoft's new feature in API Management (APIM) enables seamless messaging to Azure Service Bus, simplifying API connections in event-driven architectures. By using the send-service-bus-message policy, developers can easily route HTTP requests to Service Bus for asynchronous processing, enhancing integration, security, and control without additional components.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Service Bus</category>
      <category>Cloud</category>
      <category>Messaging</category>
      <category>Microsoft Azure</category>
      <category>Azure</category>
      <category>API Gateway</category>
      <category>PaaS</category>
      <category>Microsoft</category>
      <category>Event Driven Architecture</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 06 Nov 2025 10:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2025/11/azure-apim-service-bus-policy/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Messaging</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2025-11-06T10:00:00Z</dc:date>
      <dc:identifier>/news/2025/11/azure-apim-service-bus-policy/en</dc:identifier>
    </item>
  </channel>
</rss>
