Merge pull request #207672 from batamig/revert-207671-patch-229

Revert "clarifying eiot only"

Author: PRMerger16

articles/defender-for-iot/organizations/how-to-manage-subscriptions.md

@@ -63,7 +63,7 @@ We recommend making an initial estimate of your committed devices when onboardin
 
 1. Remove any devices that are *not* considered as committed devices by Defender for IoT.
 
-    **For Enterprise IoT networks**: If you are also a Defender for Endpoint customer, you can identify devices managed by Defender for Endpoint in the Defender for Endpoint **Device inventory** page. In the **Endpoints** tab, filter for devices by **Onboarding status**. For more information, see [Defender for Endpoint Device discovery overview](/microsoft-365/security/defender-endpoint/device-discovery).
+    If you are also a Defender for Endpoint customer, you can identify devices managed by Defender for Endpoint in the Defender for Endpoint **Device inventory** page. In the **Endpoints** tab, filter for devices by **Onboarding status**. For more information, see [Defender for Endpoint Device discovery overview](/microsoft-365/security/defender-endpoint/device-discovery).
 
 After you've set up your network sensor and have full visibility into all devices, you can [Edit a plan](#edit-a-plan-for-ot-networks) to update the number of committed devices as needed.