deprecating IoT Hub experience

Author: Shereen-Bhar

.openpublishing.redirection.defender-for-iot.json

@@ -653,6 +653,11 @@
             "source_path_from_root": "/articles/defender-for-iot/device-builders/concept-security-agent-authentication.md",
             "redirect_url": "/azure/defender-for-iot/device-builders/tutorial-standalone-agent-binary-installation",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/defender-for-iot/organizations/how-to-connect-sensor-by-proxy.md",
+            "redirect_url": "/azure/defender-for-iot/organizations/connect-sensors",
+            "redirect_document_id": false
         }
     ]
 }

articles/defender-for-iot/organizations/TOC.yml

@@ -206,8 +206,6 @@
       items:
       - name: Connect OT sensors to Defender for IoT
         href: connect-sensors.md
-      - name: Connect OT sensors with a proxy (legacy)
-        href: how-to-connect-sensor-by-proxy.md
     - name: Activate and set up your on-premises management console
       href: how-to-activate-and-set-up-your-on-premises-management-console.md
     - name: Add support for proprietary protocols

articles/defender-for-iot/organizations/how-to-connect-sensor-by-proxy.md

@@ -95,8 +95,6 @@ For more information, see the [Microsoft Defender for IoT for device builders do
 
 Defender for IoT routes all traffic from all European regions to the *West Europe* regional datacenter. It routes traffic from all remaining regions to the *East US* regional datacenter.
 
-If you're using Defender for IoT OT monitoring software earlier than [22.1](release-notes.md#versions-222x) and are connecting through your own IoT Hub, the IoT Hub supported regions are also relevant for your organization. For more information, see [IoT Hub supported regions](https://azure.microsoft.com/global-infrastructure/services/?products=iot-hub).
-
 ## Next steps
 
 > [!div class="nextstepaction"]