Merge pull request #114870 from spelluru/relaynamechange-2

"Service Bus Relay" -> "Azure Relay"

Author: PRMerger17

articles/azure-relay/relay-faq.md

@@ -32,7 +32,7 @@ The [Azure Relay service](relay-what-is-it.md) facilitates your hybrid applicati
 A [namespace](relay-create-namespace-portal.md) is a scoping container that you can use to address Relay resources within your application. You must create a namespace to use Relay. This is one of the first steps in getting started.
 
 ### What happened to Service Bus Relay service?
-The previously named Service Bus Relay service is now called [WCF Relay](service-bus-relay-tutorial.md). You can continue to use this service as usual. The Hybrid Connections feature is an updated version of a service that's been transplanted from Azure BizTalk Services. WCF Relay and Hybrid Connections both continue to be supported.
+The previously named Service Bus Relay service is now called [Azure Relay](service-bus-relay-tutorial.md). You can continue to use this service as usual. The Hybrid Connections feature is an updated version of a service that's been transplanted from Azure BizTalk Services. WCF Relay and Hybrid Connections both continue to be supported.
 
 ## Pricing
 This section answers some frequently asked questions about the Relay pricing structure. You also can see the [Azure Support FAQs](https://azure.microsoft.com/support/faq/) for general Azure pricing information. For complete information about Relay pricing, see [Service Bus pricing details][Pricing overview].
@@ -71,7 +71,7 @@ In some cases, a single relay might have multiple connected listeners. A relay i
 
 In general, billable messages for relays are calculated by using the same method that is used for brokered entities (queues, topics, and subscriptions), described previously. However, there are some notable differences.
 
-Sending a message to a Service Bus relay is treated as a "full through" send to the relay listener that receives the message. It is not treated as a send operation to the Service Bus relay, followed by a delivery to the relay listener. A request-reply style service invocation (of up to 64 KB) against a relay listener results in two billable messages: one billable message for the request and one billable message for the response (assuming the response is also 64 KB or smaller). This is different than using a queue to mediate between a client and a service. If you use a queue to mediate between a client and a service, the same request-reply pattern requires a request send to the queue, followed by a dequeue/delivery from the queue to the service. This is followed by a response send to another queue, and a dequeue/delivery from that queue to the client. Using the same size assumptions throughout (up to 64 KB), the mediated queue pattern results in 4 billable messages. You'd be billed for twice the number of messages to implement the same pattern that you accomplish by using relay. Of course, there are benefits to using queues to achieve this pattern, such as durability and load leveling. These benefits might justify the additional expense.
+Sending a message to a Azure Relay is treated as a "full through" send to the relay listener that receives the message. It is not treated as a send operation to the Azure Relay, followed by a delivery to the relay listener. A request-reply style service invocation (of up to 64 KB) against a relay listener results in two billable messages: one billable message for the request and one billable message for the response (assuming the response is also 64 KB or smaller). This is different than using a queue to mediate between a client and a service. If you use a queue to mediate between a client and a service, the same request-reply pattern requires a request send to the queue, followed by a dequeue/delivery from the queue to the service. This is followed by a response send to another queue, and a dequeue/delivery from that queue to the client. Using the same size assumptions throughout (up to 64 KB), the mediated queue pattern results in 4 billable messages. You'd be billed for twice the number of messages to implement the same pattern that you accomplish by using relay. Of course, there are benefits to using queues to achieve this pattern, such as durability and load leveling. These benefits might justify the additional expense.
 
 Relays that are opened by using the **netTCPRelay** WCF binding treat messages not as individual messages, but as a stream of data flowing through the system. When you use this binding, only the sender and listener have visibility into the framing of the individual messages sent and received. For relays that use the **netTCPRelay** binding, all data is treated as a stream for calculating billable messages. In this case, Service Bus calculates the total amount of data sent or received via each individual relay on a 5-minute basis. Then, it divides that total amount of data by 64 KB to determine the number of billable messages for that relay during that time period.
 

articles/azure-relay/service-bus-relay-rest-tutorial.md

@@ -1,6 +1,6 @@
 ---
 title: 'Tutorial: REST tutorial using Azure Relay'
-description: 'Tutorial: Build an Azure Service Bus Relay host application that exposes a REST-based interface.'
+description: 'Tutorial: Build an Azure Relay host application that exposes a REST-based interface.'
 services: service-bus-relay
 documentationcenter: na
 author: spelluru

articles/azure-relay/service-bus-relay-security-controls.md

@@ -1,6 +1,6 @@
 ---
-title: Security controls for Azure Service Bus Relay
-description: This articles provides a checklist of built-in security controls for evaluating Azure Service Bus Relay.
+title: Security controls for Azure Relay
+description: This articles provides a checklist of built-in security controls for evaluating Azure Relay.
 services: service-bus-relay
 ms.service: service-bus-relay
 author: spelluru
@@ -10,9 +10,9 @@ ms.date: 01/21/2020
 ms.author: spelluru
 
 ---
-# Security controls for Azure Service Bus Relay
+# Security controls for Azure Relay
 
-This article documents the security controls built into Azure Service Bus Relay.
+This article documents the security controls built into Azure Relay.
 
 [!INCLUDE [Security controls Header](../../includes/security-controls-header.md)]