205156 - ms.custom value added | updated

Author: v-hearya

articles/iot-central/retail/architecture-connected-logistics.md

@@ -7,6 +7,7 @@ ms.service: iot-central
 ms.subservice: iot-central-retail
 ms.topic: overview
 ms.date: 10/20/2019
+ms.custom:  mqtt
 ---
 
 # Architecture of IoT Central connected logistics application template

articles/iot-central/retail/architecture-smart-inventory-management.md

@@ -7,6 +7,7 @@ ms.service: iot-central
 ms.subservice: iot-central-retail
 ms.topic: overview
 ms.date: 10/20/2019
+ms.custom:  mqtt
 ---
 
 # Architecture of IoT Central smart inventory management application template

articles/iot-dps/about-iot-dps.md

@@ -8,6 +8,7 @@ ms.topic: overview
 ms.service: iot-dps
 services: iot-dps
 manager: eliotgra
+ms.custom:  [amqp, mqtt]
 ---
 
 # Provisioning devices with Azure IoT Hub Device Provisioning Service
@@ -18,7 +19,7 @@ There are many provisioning scenarios in which DPS is an excellent choice for ge
 
 * Zero-touch provisioning to a single IoT solution without hardcoding IoT Hub connection information at the factory (initial setup)
 * Load-balancing devices across multiple hubs
-* Connecting devices to their owner’s IoT solution based on sales transaction data (multitenancy)
+* Connecting devices to their owner's IoT solution based on sales transaction data (multitenancy)
 * Connecting devices to a particular IoT solution depending on use-case (solution isolation)
 * Connecting a device to the IoT hub with the lowest latency (geo-sharding)
 * Reprovisioning based on a change in the device

articles/iot-dps/iot-dps-mqtt-support.md

@@ -7,6 +7,7 @@ services: iot-dps
 ms.topic: conceptual
 ms.date: 10/16/2019
 ms.author: ravokkar
+ms.custom:  [amqp, mqtt]
 ---
 # Communicate with your DPS using the MQTT protocol
 
@@ -17,7 +18,7 @@ DPS enables devices to communicate with the DPS device endpoint using:
 
 DPS is not a full-featured MQTT broker and does not support all the behaviors specified in the MQTT v3.1.1 standard. This article describes how devices can use supported MQTT behaviors to communicate with DPS.
 
-All device communication with DPS must be secured using TLS/SSL. Therefore, DPS doesn’t support non-secure connections over port 1883.
+All device communication with DPS must be secured using TLS/SSL. Therefore, DPS doesn't support non-secure connections over port 1883.
 
  > [!NOTE] 
  > DPS does not currently support devices using TPM [attestation mechanism](https://docs.microsoft.com/azure/iot-dps/concepts-device#attestation-mechanism) over the MQTT protocol.

articles/iot-dps/quick-create-simulated-device-tpm-node.md

@@ -6,8 +6,8 @@ ms.author: wesmc
 ms.date: 11/08/2018
 ms.topic: quickstart
 ms.service: iot-dps
-services: iot-dps 
-ms.custom: mvc
+services: iot-dps
+ms.custom:  [mvc, amqp, mqtt]
 ---
 
 # Quickstart: Create and provision a simulated TPM device using Node.js device SDK for IoT Hub Device Provisioning Service
@@ -255,7 +255,7 @@ If you plan to continue working on and exploring the device client sample, do no
 
 ## Next steps
 
-In this quickstart, you’ve created a TPM simulated device on your machine and provisioned it to your IoT hub using the IoT Hub Device Provisioning Service. To learn how to enroll your TPM device programmatically, continue to the quickstart for programmatic enrollment of a TPM device. 
+In this quickstart, you've created a TPM simulated device on your machine and provisioned it to your IoT hub using the IoT Hub Device Provisioning Service. To learn how to enroll your TPM device programmatically, continue to the quickstart for programmatic enrollment of a TPM device. 
 
 > [!div class="nextstepaction"]
 > [Azure quickstart - Enroll TPM device to Azure IoT Hub Device Provisioning Service](quick-enroll-device-tpm-node.md)

articles/iot-dps/quick-create-simulated-device.md

@@ -8,7 +8,7 @@ ms.topic: quickstart
 ms.service: iot-dps
 services: iot-dps 
 manager: philmea
-ms.custom: mvc
+ms.custom:  [mvc, amqp, mqtt]
 #Customer intent: As a new IoT developer, I want simulate a TPM device using the C SDK so that I can learn how secure provisioning works.
 ---
 
@@ -218,7 +218,7 @@ If you plan to continue working on and exploring the device client sample, do no
 
 ## Next steps
 
-In this quickstart, you’ve created a TPM simulated device on your machine and provisioned it to your IoT hub using the IoT Hub Device Provisioning Service. To learn how to enroll your TPM device programmatically, continue to the quickstart for programmatic enrollment of a TPM device. 
+In this quickstart, you've created a TPM simulated device on your machine and provisioned it to your IoT hub using the IoT Hub Device Provisioning Service. To learn how to enroll your TPM device programmatically, continue to the quickstart for programmatic enrollment of a TPM device. 
 
 > [!div class="nextstepaction"]
 > [Azure quickstart - Enroll TPM device to Azure IoT Hub Device Provisioning Service](quick-enroll-device-tpm-java.md)

articles/iot-dps/use-hsm-with-sdk.md

@@ -7,7 +7,7 @@ ms.date: 03/30/2018
 ms.topic: conceptual
 ms.service: iot-dps
 services: iot-dps 
-ms.custom: mvc
+ms.custom:  [mvc, amqp]
 ---
 # How to use different attestation mechanisms with Device Provisioning Service Client SDK for C
 

articles/iot-edge/how-to-configure-proxy-support.md

@@ -7,6 +7,7 @@ ms.date: 3/10/2020
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
+ms.custom:  amqp
 ---
 
 # Configure an IoT Edge device to communicate through a proxy server

articles/iot-edge/how-to-connect-downstream-device.md

@@ -8,6 +8,7 @@ ms.date: 12/08/2019
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
+ms.custom:  [amqp, mqtt]
 ---
 
 # Connect a downstream device to an Azure IoT Edge gateway

articles/iot-edge/how-to-create-transparent-gateway.md

@@ -8,6 +8,7 @@ ms.date: 04/03/2020
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
+ms.custom:  [amqp, mqtt]
 ---
 
 # Configure an IoT Edge device to act as a transparent gateway