warning & missing contents fixed

Author: v-hearya

articles/azure-monitor/agents/diagnostics-extension-stream-event-hubs.md

@@ -173,7 +173,7 @@ You can use a variety of methods to validate that data is being sent to the even
 
 * [Event Hubs overview](../../event-hubs/event-hubs-about.md)
 * [Create an event hub](../../event-hubs/event-hubs-create.md)
-* [Event Hubs FAQ](../../event-hubs/event-hubs-faq.md)
+* [Event Hubs FAQ](../../event-hubs/event-hubs-faq.yml)
 
 <!-- Images. -->
 [0]: ../../event-hubs/media/event-hubs-streaming-azure-diags-data/dashboard.png

articles/azure-relay/relay-faq.yml

@@ -31,8 +31,10 @@ sections:
         answer: |
           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.
           
-  - name: Pricing
-    questions:
+          ## 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](https://azure.microsoft.com/pricing/details/service-bus/).
+
       - question: |
           How do you charge for Hybrid Connections and WCF Relay?
         answer: |
@@ -78,8 +80,16 @@ sections:
           
           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.
           
-  - name: Quotas
-    questions:
+          ## Quotas
+          
+          | Quota name | Scope |  Notes | Value |
+          | --- | --- | --- | --- |
+          | Concurrent listeners on a relay |Entity (hybrid connection or WCF relay) |Subsequent requests for additional connections are rejected and an exception is received by the calling code. |25 |
+          | Concurrent relay connections per all relay endpoints in a service namespace |Namespace |- |5,000 |
+          | Relay endpoints per service namespace |Namespace |- |10,000 |
+          | Message size for [NetOnewayRelayBinding](/dotnet/api/microsoft.servicebus.netonewayrelaybinding) and [NetEventRelayBinding](/dotnet/api/microsoft.servicebus.neteventrelaybinding) relays |Namespace |Incoming messages that exceed these quotas are rejected and an exception is received by the calling code. |64 KB |
+          | Message size for [HttpRelayTransportBindingElement](/dotnet/api/microsoft.servicebus.httprelaytransportbindingelement) and [NetTcpRelayBinding](/dotnet/api/microsoft.servicebus.nettcprelaybinding) relays |Namespace |No limit on message size. |Unlimited |
+
       - question: |
           Does Relay have any usage quotas?
         answer: |
@@ -101,6 +111,26 @@ sections:
           How do I migrate a namespace to another Azure subscription?
         answer: |
           To move a namespace from one Azure subscription to another subscription, you can either use the [Azure portal](https://portal.azure.com) or use PowerShell commands. To move a namespace to another subscription, the namespace must already be active. The user running the commands must be an Administrator user on both the source and target subscriptions.
+
+          **Azure portal**
+
+          To use the Azure portal to migrate Azure Relay namespaces from one subscription to another subscription, see [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md#use-the-portal). 
+
+          **PowerShell**
+
+          To use PowerShell to move a namespace from one Azure subscription to another subscription, use the following sequence of commands. To execute this operation, the namespace must already be active, and the user running the PowerShell commands must be an Administrator user on both the source and target subscriptions.
+
+          ```azurepowershell-interactive
+          # Create a new resource group in the target subscription.
+          Select-AzSubscription -SubscriptionId 'ffffffff-ffff-ffff-ffff-ffffffffffff'
+          New-AzResourceGroup -Name 'targetRG' -Location 'East US'
+
+          # Move the namespace from the source subscription to the target subscription.
+          Select-AzSubscription -SubscriptionId 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa'
+          $res = Find-AzResource -ResourceNameContains mynamespace -ResourceType 'Microsoft.ServiceBus/namespaces'
+          Move-AzResource -DestinationResourceGroupName 'targetRG' -DestinationSubscriptionId 'ffffffff-ffff-ffff-ffff-ffffffffffff' -ResourceId $res.ResourceId
+          ```
+
           
   - name: Troubleshooting
     questions:

articles/event-hubs/event-hubs-create.md

@@ -49,7 +49,7 @@ An Event Hubs namespace provides a unique scoping container, in which you create
    1. Select the **resource group** you created in the previous step.   
    1. Enter a **name** for the namespace. The system immediately checks to see if the name is available.  
    1. Select a **location** for the namespace.
-   1. Choose the **pricing tier** (Basic or Standard). To learn about some of the differences between basic and standard tiers, see [Event Hubs pricing](https://azure.microsoft.com/pricing/details/event-hubs/), [Differences between tiers](event-hubs-faq.yml#what-is-the-difference-between-event-hubs-basic-and-standard-tiers), and [Quotas and limits](event-hubs-quotas.md). 
+   1. Choose the **pricing tier** (Basic or Standard). To learn about some of the differences between basic and standard tiers, see [Event Hubs pricing](https://azure.microsoft.com/pricing/details/event-hubs/), [Differences between tiers](event-hubs-faq.yml#what-is-the-difference-between-event-hubs-basic-and-standard-tiers-), and [Quotas and limits](event-hubs-quotas.md). 
    1. Leave the **throughput units** settings as it is. Throughput units are pre-purchased units of capacity. To learn about throughput units, see [Event Hubs scalability](event-hubs-scalability.md#throughput-units).  
    1. Select **Review + Create** at the bottom of the page.
 

articles/event-hubs/event-hubs-faq.yml

@@ -19,7 +19,7 @@ sections:
       - question: |
           When do I create a new namespace vs. use an existing namespace?
         answer: |
-          Capacity allocations ([throughput units (TUs)](#throughput-units)) are billed at the namespace level. A namespace is also associated with a region.
+          Capacity allocations ([throughput units (TUs)](/event-hubs-faq.yml#throughput-units)) are billed at the namespace level. A namespace is also associated with a region.
           
           You may want to create a new namespace instead of using an existing one in one of the following scenarios: 
           

articles/iot-hub/iot-hub-scaling.md

@@ -50,7 +50,7 @@ IoT Hub also offers a free tier that is meant for testing and evaluation. It has
 
 Azure IoT Hubs contain many core components of [Azure Event Hubs](../event-hubs/event-hubs-features.md), including [Partitions](../event-hubs/event-hubs-features.md#partitions). Event streams for IoT Hubs are generally populated with incoming telemetry data that is reported by various IoT devices. The partitioning of the event stream is used to reduce contentions that occur when concurrently reading and writing to event streams.
 
-The partition limit is chosen when IoT Hub is created, and cannot be changed. The maximum partition limit for basic tier IoT Hub and standard tier IoT Hub is 32. Most IoT hubs only need 4 partitions. For more information on determining the partitions, see the Event Hubs FAQ [How many partitions do I need?](../event-hubs/event-hubs-faq.yml#how-many-partitions-do-i-need)
+The partition limit is chosen when IoT Hub is created, and cannot be changed. The maximum partition limit for basic tier IoT Hub and standard tier IoT Hub is 32. Most IoT hubs only need 4 partitions. For more information on determining the partitions, see the Event Hubs FAQ [How many partitions do I need?](../event-hubs/event-hubs-faq.yml#how-many-partitions-do-i-need-)
 
 ## Tier upgrade
 

articles/time-series-insights/concepts-streaming-ingress-throughput-limits.md

@@ -55,7 +55,7 @@ When planning your Azure Time Series Insights Gen2 environment, it's important t
 
 A *partition* is an ordered sequence of events held in a hub. The partition count is set during the hub creation phase and cannot be changed.
 
-For Event Hubs partitioning best practices, review [How many partitions do I need?](../event-hubs/event-hubs-faq.yml#how-many-partitions-do-i-need)
+For Event Hubs partitioning best practices, review [How many partitions do I need?](../event-hubs/event-hubs-faq.yml#how-many-partitions-do-i-need-)
 
 > [!NOTE]
 > Most IoT Hubs used with Azure Time Series Insights Gen2 only need four partitions.

includes/event-hubs-partitions.md

@@ -41,7 +41,7 @@ Capacity Unit in Event Hubs Dedicated.
 
 We recommend that you choose at least as many partitions as you expect to
 require in sustained [throughput units
-(TU)](../articles/event-hubs/event-hubs-faq.yml#what-are-event-hubs-throughput-units)
+(TU)](../articles/event-hubs/event-hubs-faq.yml#what-are-event-hubs-throughput-units-)
 during the peak load of your application for that particular Event Hub. You
 should calculate with a single partition having a throughput capacity of 1 TU (1
 MByte in, 2 MByte out). You can scale the TUs on your namespace or the capacity