diff --git a/architecture/azure/messaging.md b/architecture/azure/messaging.md
index 2763aa2f604..eed28c572bf 100644
--- a/architecture/azure/messaging.md
+++ b/architecture/azure/messaging.md
@@ -26,7 +26,7 @@ Azure Service Bus has two pricing tiers: [Standard and Premium](https://learn.mi
 - The maximum message size is 256 KB on the Standard tier
 - Cross-entity transactions are limited to 100 messages
 - No cross-namespace communication
-- No emulator for local development or testing available
+- Emulator for local development and testing [does not have required features](/transports/azure-service-bus/#transport-at-a-glance) to work with the Particular Service Platform.
 
 [**Try the Azure Service Bus Tutorial →**](https://learn.microsoft.com/en-us/azure/service-bus-messaging/build-message-driven-apps-nservicebus?tabs=Sender)
 
diff --git a/transports/azure-service-bus/index.md b/transports/azure-service-bus/index.md
index 9f8e1369b65..ab8095da59f 100644
--- a/transports/azure-service-bus/index.md
+++ b/transports/azure-service-bus/index.md
@@ -30,3 +30,5 @@ The Azure Service Bus transport leverages the [Azure.Messaging.ServiceBus](https
 
 > [!NOTE]
 > The Azure Service Bus transport only supports the Standard and Premium tiers of the Microsoft Azure Service Bus service. Premium tier is recommended for production environments.
+>
+> The Azure Service Bus transport is not compatible with the [Azure Service Bus emulator](https://learn.microsoft.com/en-us/azure/service-bus-messaging/overview-emulator) because the emulator [doesn't support on-the-fly management operations](https://learn.microsoft.com/en-us/azure/service-bus-messaging/overview-emulator#known-limitations) through the client-side SDK, which prevents operations like creating queues or subscribing to events.