Merge pull request #192045 from kgremban/mar17-protocolgateway

Add redirect note and NOINDEX protocol gateway; remove links to article

Author: denrea

articles/iot-hub/iot-hub-amqp-support.md

@@ -370,5 +370,5 @@ To learn more about the AMQP Protocol, see the [AMQP v1.0 specification](https:/
 To learn more about IoT Hub messaging, see:
 
 * [Cloud-to-device messages](./iot-hub-devguide-messages-c2d.md)
-* [Support for additional protocols](iot-hub-protocol-gateway.md)
+* [Support for additional protocols](../iot-edge/iot-edge-as-gateway.md)
 * [Support for the Message Queuing Telemetry Transport (MQTT) Protocol](./iot-hub-mqtt-support.md)

articles/iot-hub/iot-hub-dev-guide-sas.md

@@ -382,8 +382,7 @@ For a device/module to connect to your hub, you must still add it to the IoT Hub
 
 ### Comparison with a custom gateway
 
-The token service pattern is the recommended way to implement a custom identity registry/authentication scheme with IoT Hub. This pattern is recommended because IoT Hub continues to handle most of the solution traffic. However, if the custom authentication scheme is so intertwined with the protocol, you may require a *custom gateway* to process all the traffic. An example of such a scenario is using [Transport Layer Security (TLS) and pre-shared keys (PSKs)](https://tools.ietf.org/html/rfc4279). For more information, see the [protocol gateway](iot-hub-protocol-gateway.md) article.
-
+The token service pattern is the recommended way to implement a custom identity registry/authentication scheme with IoT Hub. This pattern is recommended because IoT Hub continues to handle most of the solution traffic. However, if the custom authentication scheme is so intertwined with the protocol, you may require a *custom gateway* to process all the traffic. An example of such a scenario is using [Transport Layer Security (TLS) and pre-shared keys (PSKs)](https://tools.ietf.org/html/rfc4279). For more information, see [How an IoT Edge device can be used as a gateway](../iot-edge/iot-edge-as-gateway.md).
 
 ## Additional reference material
 

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

@@ -431,18 +431,14 @@ To respond, the device sends a message with a valid JSON or empty body to the to
 
 For more information, see the [Direct method developer's guide](iot-hub-devguide-direct-methods.md).
 
-## Additional considerations
-
-As a final consideration, if you need to customize the MQTT protocol behavior on the cloud side, you should review the [Azure IoT protocol gateway](iot-hub-protocol-gateway.md). This software enables you to deploy a high-performance custom protocol gateway that interfaces directly with IoT Hub. The Azure IoT protocol gateway enables you to customize the device protocol to accommodate brownfield MQTT deployments or other custom protocols. This approach does require, however, that you run and operate a custom protocol gateway.
-
 ## Next steps
 
 To learn more about the MQTT protocol, see the [MQTT documentation](https://mqtt.org/).
 
 To learn more about planning your IoT Hub deployment, see:
 
 * [Azure Certified for IoT device catalog](https://devicecatalog.azure.com/)
-* [Support additional protocols](iot-hub-protocol-gateway.md)
+* [Support additional protocols](../iot-edge/iot-edge-as-gateway.md)
 * [Compare with Event Hubs](iot-hub-compare-event-hubs.md)
 * [Scaling, HA, and DR](iot-hub-scaling.md)
 

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

@@ -7,14 +7,20 @@ ms.author: kgremban
 ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
-ms.date: 08/19/2021
+ms.date: 03/17/2022
 ms.custom: [amqp, mqtt, 'Role: Cloud Development', 'Role: IoT Device']
+ROBOTS: NOINDEX
 ---
 
 # Support additional protocols for IoT Hub
 
 Azure IoT Hub natively supports communication over the MQTT, AMQP, and HTTPS protocols. In some cases, devices or field gateways might not be able to use one of these standard protocols and require protocol adaptation. In such cases, you can use a custom gateway. A custom gateway enables protocol adaptation for IoT Hub endpoints by bridging the traffic to and from IoT Hub. You can use the [Azure IoT protocol gateway](https://github.com/Azure/azure-iot-protocol-gateway/blob/master/README.md) as a custom gateway to enable protocol adaptation for IoT Hub.
 
+>[!NOTE]
+>The Azure IoT protocol gateway is no longer the recommended method for protocol adaptation. Instead, consider using Azure IoT Edge as a gateway.
+>
+>For more information, see [How an IoT Edge device can be used as a gateway](../iot-edge/iot-edge-as-gateway.md).
+
 ## Azure IoT protocol gateway
 
 The Azure IoT protocol gateway is a framework for protocol adaptation that is designed for high-scale, bidirectional device communication with IoT Hub. The protocol gateway is a pass-through component that accepts device connections over a specific protocol. It bridges the traffic to IoT Hub over AMQP 1.0.
@@ -31,14 +37,4 @@ For flexibility, the Azure IoT protocol gateway and MQTT implementation are prov
 
 To learn more about the Azure IoT protocol gateway and how to use and deploy it as part of your IoT solution, see:
 
-* [Azure IoT protocol gateway repository on GitHub](https://github.com/Azure/azure-iot-protocol-gateway/blob/master/README.md)
-
-* [Azure IoT protocol gateway developer guide](https://github.com/Azure/azure-iot-protocol-gateway/blob/master/docs/DeveloperGuide.md)
-
-To learn more about planning your IoT Hub deployment, see:
-
-* [Compare with Event Hubs](iot-hub-compare-event-hubs.md)
-
-* [Scaling, high availability, and disaster recovery](iot-hub-scaling.md)
-
-* [IoT Hub developer guide](iot-hub-devguide.md)
+* [Azure IoT protocol gateway repository on GitHub](https://github.com/Azure/azure-iot-protocol-gateway/blob/master/README.md)