Power Automate Azure Service Bus Connector Still Generating SBMP Traffic - Impact of Azure Service Bus SBMP Retirement?

Josue Gonzalez 190 Reputation points
2026-08-17T23:03:43.9866667+00:00

Hello,

We are preparing for the Azure Service Bus SBMP protocol retirement and have been reviewing our Service Bus namespaces for any remaining SBMP traffic prior to the retirement date.

During our investigation, we identified several Power Automate flows using the Azure Service Bus connector (triggered by incoming messages on Service Bus topics/subscriptions) that appear to be generating traffic reported as SBMP.

Environment

  • Azure Service Bus Topics/Subscriptions
  • Power Automate Cloud Flows
  • Azure Service Bus Connector
  • Trigger pattern: "When a message is received" (long-running listener scenarios)

What we observed

  1. We identified persistent SBMP traffic in our Service Bus metrics/logs.
  2. We disabled the affected Power Automate flows and observed that the SBMP traffic stopped.
  3. We re-enabled the flows and the SBMP traffic resumed.
  4. We recreated the Azure Service Bus connections used by the flows.
  5. We also recreated/re-imported the flows.
  6. Despite these actions, the traffic still appears as SBMP.

Questions

  1. Is the Azure Service Bus connector used by Power Automate expected to continue functioning after the Azure Service Bus SBMP retirement?
  2. Does the managed backend infrastructure for the connector still use SBMP today, even if customers cannot directly configure the transport protocol?
  3. Has Microsoft already transitioned the connector backend to AMQP, and could the observed traffic be reported differently than expected?
  4. Is there any customer action required before the SBMP retirement date for flows that use the Azure Service Bus connector as a trigger?
  5. Are there any documented migration steps, known limitations, or announcements specifically related to Power Automate and the Azure Service Bus connector in the context of SBMP deprecation?

Business Impact

These flows support business-critical processes and ultimately impact thousands of Dynamics 365 users. We are looking for confirmation from Microsoft that no service disruption is expected and whether any proactive remediation is required on our side.

Any guidance from the Azure Service Bus or Power Platform teams would be greatly appreciated.

Thank you.Hello,

We are preparing for the Azure Service Bus SBMP protocol retirement and have been reviewing our Service Bus namespaces for any remaining SBMP traffic prior to the retirement date.

During our investigation, we identified several Power Automate flows using the Azure Service Bus connector (triggered by incoming messages on Service Bus topics/subscriptions) that appear to be generating traffic reported as SBMP.

Environment

  • Azure Service Bus Topics/Subscriptions
  • Power Automate Cloud Flows
  • Azure Service Bus Connector
  • Trigger pattern: "When a message is received" (long-running listener scenarios)

What we observed

  1. We identified persistent SBMP traffic in our Service Bus metrics/logs.
  2. We disabled the affected Power Automate flows and observed that the SBMP traffic stopped.
  3. We re-enabled the flows and the SBMP traffic resumed.
  4. We recreated the Azure Service Bus connections used by the flows.
  5. We also recreated/re-imported the flows.
  6. Despite these actions, the traffic still appears as SBMP.

Questions

  1. Is the Azure Service Bus connector used by Power Automate expected to continue functioning after the Azure Service Bus SBMP retirement?
  2. Does the managed backend infrastructure for the connector still use SBMP today, even if customers cannot directly configure the transport protocol?
  3. Has Microsoft already transitioned the connector backend to AMQP, and could the observed traffic be reported differently than expected?
  4. Is there any customer action required before the SBMP retirement date for flows that use the Azure Service Bus connector as a trigger?
  5. Are there any documented migration steps, known limitations, or announcements specifically related to Power Automate and the Azure Service Bus connector in the context of SBMP deprecation?

Business Impact

These flows support business-critical processes and ultimately impact thousands of Dynamics 365 users. We are looking for confirmation from Microsoft that no service disruption is expected and whether any proactive remediation is required on our side.

Any guidance from the Azure Service Bus or Power Platform teams would be greatly appreciated.

Thank you.

Azure Service Bus
Azure Service Bus

An Azure service that provides cloud messaging as a service and hybrid integration.

0 comments
Answer accepted by question author
Allan Solomon Mejia 8,170 Reputation points
2026-08-18T00:27:36.8766667+00:00

Hello @Josue Gonzalez

The key point here is that the Azure Service Bus connector in Power Automate is a Microsoft-managed connector. Unlike an application using the Service Bus SDK directly, Power Automate doesn't offer a customer-configurable option to select SBMP versus AMQP.

Microsoft has announced that support for the SBMP protocol and legacy Service Bus SDK libraries ends on September 30, 2026. The migration guidance primarily applies to applications using legacy libraries such as WindowsAzure.ServiceBus or Microsoft.Azure.ServiceBus, where customers control the SDK and transport implementation.

For Power Automate, recreating the connection or re-importing the flow is not expected to change the underlying protocol, since Microsoft's connector infrastructure handles that implementation.

If your Service Bus telemetry still reports SBMP traffic specifically from Power Automate, I recommend opening a Microsoft support case and providing the namespace, timestamps, flow/connection IDs, and the telemetry showing the SBMP connections. Microsoft can confirm whether this is actual SBMP traffic from the managed connector, how the metric is being classified, and whether any backend migration is required before the retirement date.

I would not redesign the flows or replace the connector solely because of the SBMP metric unless Microsoft confirms that customer action is required. At present, I am not aware of a documented customer-side procedure for migrating the Power Automate Service Bus managed connector from SBMP to AMQP.

Sharing these references with you:

Microsoft Service Bus performance improvements and SBMP/legacy SDK retirement:

Azure Service Bus performance improvements | https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-performance-improvements?

Power Automate / Logic Apps Azure Service Bus connector documentation:

Azure Service Bus connector reference | https://learn.microsoft.com/en-us/connectors/servicebus/

Use Azure Service Bus with Power Automate and Logic Apps | https://learn.microsoft.com/en-us/azure/connectors/connectors-create-api-servicebus?

Please "Accept the Answer" if this information helped you. This will help us and others in the community.

Was this answer helpful?

1 person found this answer helpful.
0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.