Merge pull request #112082 from v-hearya/master

205156 - ms.custom value added | updated

Author: cmcclister

articles/iot-hub/iot-hub-portal-csharp-module-twin-getstarted.md

@@ -9,13 +9,14 @@ services: iot-hub
 ms.devlang: csharp
 ms.topic: conceptual
 ms.date: 08/20/2019
+ms.custom: amqp
 ---
 # Get started with IoT Hub module identity and module twin using the portal and .NET device
 
 [!INCLUDE [iot-hub-selector-module-twin-getstarted](../../includes/iot-hub-selector-module-twin-getstarted.md)]
 
 > [!NOTE]
-> [Module identities and module twins](iot-hub-devguide-module-twins.md) are similar to Azure IoT Hub device identity and device twin, but provide finer granularity. While Azure IoT Hub device identity and device twin enable the back-end application to configure a device and provide visibility on the device’s conditions, a module identity and module twin provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system based devices or firmware devices, module identities and module twins allow for isolated configuration and conditions for each component.
+> [Module identities and module twins](iot-hub-devguide-module-twins.md) are similar to Azure IoT Hub device identity and device twin, but provide finer granularity. While Azure IoT Hub device identity and device twin enable the back-end application to configure a device and provide visibility on the device's conditions, a module identity and module twin provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system based devices or firmware devices, module identities and module twins allow for isolated configuration and conditions for each component.
 >
 
 In this tutorial, you will learn:

articles/iot-hub/iot-hub-protocol-gateway.md

@@ -8,6 +8,7 @@ ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
 ms.date: 07/11/2017
+ms.custom: [amqp, mqtt]
 ---
 
 # Support additional protocols for IoT Hub

articles/iot-hub/iot-hub-python-python-c2d.md

@@ -8,6 +8,7 @@ ms.devlang: python
 ms.topic: conceptual
 ms.date: 04/09/2020
 ms.author: robinsh
+ms.custom: mqtt
 ---
 
 # Send cloud-to-device messages with IoT Hub (Python)

articles/iot-hub/iot-hub-python-python-device-management-get-started.md

@@ -8,6 +8,7 @@ ms.devlang: python
 ms.topic: conceptual
 ms.date: 01/17/2020
 ms.author: robinsh
+ms.custom: mqtt
 ---
 
 # Get started with device management (Python)

articles/iot-hub/iot-hub-python-python-file-upload.md

@@ -8,6 +8,7 @@ ms.devlang: python
 ms.topic: conceptual
 ms.date: 03/31/2020
 ms.author: robinsh
+ms.custom: mqtt
 ---
 
 # Upload files from your device to the cloud with IoT Hub (Python)

articles/iot-hub/iot-hub-python-twin-getstarted.md

@@ -8,6 +8,7 @@ ms.devlang: python
 ms.topic: conceptual
 ms.date: 03/11/2020
 ms.author: robinsh
+ms.custom: mqtt
 ---
 # Get started with device twins (Python)
 

articles/iot-hub/iot-hub-reliability-features-in-sdks.md

@@ -7,6 +7,7 @@ ms.author: robinsh
 ms.date: 07/07/2018
 ms.topic: article
 ms.service: iot-hub
+ms.custom: [amqp, mqtt]
 ---
 
 # Manage connectivity and reliable messaging by using Azure IoT Hub device SDKs

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

@@ -8,6 +8,7 @@ services: iot-hub
 ms.topic: conceptual
 ms.date: 06/28/2019
 ms.author: wesmc
+ms.custom: [amqp, mqtt]
 ---
 # Choose the right IoT Hub tier for your solution
 

articles/iot-hub/iot-hub-security-x509-get-started.md

@@ -8,6 +8,7 @@ ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
 ms.date: 08/20/2019
+ms.custom: amqp
 ---
 
 # Set up X.509 security in your Azure IoT hub
@@ -77,7 +78,7 @@ These steps show you how to add a new Certificate Authority to your IoT hub thro
 
 ## Authenticate your X.509 device with the X.509 certificates
 
-To authenticate your X.509 device, you need to first sign the device with the CA certificate. Signing of leaf devices is normally done at the manufacturing plant, where manufacturing tools have been enabled accordingly. As the device goes from one manufacturer to another, each manufacturer’s signing action is captured as an intermediate certificate within the chain. The result is a certificate chain from the CA certificate to the device’s leaf certificate. Step 4 in [Managing test CA certificates for samples and tutorials](https://github.com/Azure/azure-iot-sdk-c/blob/master/tools/CACertificates/CACertificateOverview.md) generates a device certificate.
+To authenticate your X.509 device, you need to first sign the device with the CA certificate. Signing of leaf devices is normally done at the manufacturing plant, where manufacturing tools have been enabled accordingly. As the device goes from one manufacturer to another, each manufacturer's signing action is captured as an intermediate certificate within the chain. The result is a certificate chain from the CA certificate to the device's leaf certificate. Step 4 in [Managing test CA certificates for samples and tutorials](https://github.com/Azure/azure-iot-sdk-c/blob/master/tools/CACertificates/CACertificateOverview.md) generates a device certificate.
 
 Next, we will show you how to create a C# application to simulate the X.509 device registered for your IoT hub. We will send temperature and humidity values from the simulated device to your hub. In this tutorial, we will create only the device application. It is left as an exercise to the readers to create the IoT Hub service application that will send response to the events sent by this simulated device. The C# application assumes that you have followed the steps in [Managing test CA certificates for samples and tutorials](https://github.com/Azure/azure-iot-sdk-c/blob/master/tools/CACertificates/CACertificateOverview.md).
 

articles/iot-hub/iot-hub-troubleshoot-connectivity.md

@@ -8,6 +8,8 @@ services: iot-hub
 ms.topic: conceptual
 ms.date: 01/30/2020
 ms.author: jlian
+ms.custom: mqtt
+
 # As an operator for Azure IoT Hub, I need to know how to find out when devices are disconnecting unexpectedly and troubleshoot resolve those issues right away
 ---
 # Monitor, diagnose, and troubleshoot disconnects with Azure IoT Hub