Merge pull request #106078 from udidahan/patch-2

Cross-link

Author: Jak-MS

articles/service-bus-messaging/service-bus-throttling.md

@@ -7,7 +7,7 @@ ms.date: 11/14/2022
 
 # Throttling operations on Azure Service Bus
 
-Cloud native solutions give a notion of unlimited resources that can scale with your workload. While this notion is more true in the cloud than it is with on-premises systems, there are still limitations that exist in the cloud. These limitations may cause throttling of client application requests in both standard and premium tiers as discussed in this article. 
+Cloud native solutions give a notion of unlimited resources that can scale with your workload. While this notion is more true in the cloud than it is with on-premises systems, there are still limitations that exist in the cloud. These limitations may cause [throttling](/azure/architecture/patterns/throttling) of client application requests in both standard and premium tiers as discussed in this article. 
 
 ## Throttling in standard tier
 
@@ -86,6 +86,9 @@ When a request is throttled, it implies that the service is busy because it's fa
 
 As throttling is the expected behavior of any cloud native service, retry logic is built into the Service Bus SDK itself. The default is set to auto retry with an exponential back-off to ensure that we don't have the same request being throttled each time. The default retry logic will apply to every operation.
 
+>[!NOTE]
+> Message-processing code that calls other third-party services may be throttled by those other services as well. For more information on how to handle these scenarios, see the [documentation on the Throttling Pattern](/azure/architecture/patterns/throttling).
+
 ### Does throttling result in data loss?
 
 Azure Service Bus is optimized for persistence, we ensure that all the data sent to Service Bus is committed to storage before the service acknowledges the success of the request.