Merge pull request #233351 from yoninalmsft/device-overage-warning

device overage warning

Author: v-shils

articles/defender-for-iot/organizations/billing.md

@@ -28,8 +28,30 @@ You're billed based on the number of committed devices associated with each subs
 
 [!INCLUDE [devices-inventoried](includes/devices-inventoried.md)]
 
-[Configure Windows Endpoint monitoring](configure-windows-endpoint-monitoring.md)
-[Configure DNS servers for reverse lookup resolution for OT monitoring](configure-reverse-dns-lookup.md)
+### Device coverage warning
+
+If the number of actual devices detected by Defender for IoT exceeds the number of committed devices currently listed on your subscription, a warning message will appear in Defender for IoT in the Azure portal. For example:
+
+:::image type="content" source="media/billing/device-coverage-warning.png" alt-text="Screenshot of the device coverage warning.":::
+
+This message indicates that you need to update the number of committed devices on the relevant subscription to match the actual number of devices being monitored.
+
+**To update the number of committed devices**:
+
+1. In the warning message, select **Get more device coverage**, which will open the pane to edit your plan for the relevant subscription.
+
+1. In the **Number of devices** field, update the number of committed devices to the actual number of devices being monitored by Defender for IoT for this subscription.
+
+    For example:
+
+    :::image type="content" source="media/billing/update-number-of-devices.png" alt-text="Screenshot of updating the number of committed devices on a subscription when there is a device coverage warning." lightbox="media/billing/update-number-of-devices.png":::
+
+1. Select **Next**.
+
+1. Select the **I accept the terms and conditions** option, and then select **Purchase**. Billing changes will be updated accordingly.  
+
+> [!NOTE]
+> This warning is a reminder for you to update the number of committed devices for your subscription, and does not affect Defender for IoT functionality.
 
 ## Billing cycles and changes in your plans
 

articles/defender-for-iot/organizations/faqs-ot.md

@@ -66,6 +66,10 @@ You can also use our [UI and CLI tools](how-to-troubleshoot-sensor.md#check-syst
 
 For more information, see [Troubleshoot the sensor](how-to-troubleshoot-sensor.md) and [Troubleshoot the on-premises management console](how-to-troubleshoot-on-premises-management-console.md).
 
+## I am seeing a warning that we have exceeded the maximum number of devices for the subscription. How do I resolve this?
+
+If the number of actual devices detected by Defender for IoT exceeds the number of committed devices currently listed on your subscription, a warning message will appear in Defender for IoT in the Azure portal, and you will need to update the number of committed devices on the relevant subscription. For more information, see [Defender for IoT committed devices](billing.md#defender-for-iot-committed-devices).
+
 ## Next steps
 
 - [Tutorial: Get started with Microsoft Defender for IoT for OT security](tutorial-onboarding.md)

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

@@ -80,7 +80,7 @@ Your new plan is listed under the relevant subscription in the **Plans** grid.
 
 Edit your Defender for IoT plans for OT networks if you need change your plan commitment or update the number of committed devices or sites.
 
-For example, you may have more devices that require monitoring if you're increasing existing site coverage, have discovered more devices than expected, or there are network changes such as adding switches.
+For example, you may have more devices that require monitoring if you're increasing existing site coverage, or there are network changes such as adding switches. If the number of actual devices detected by Defender for IoT exceeds the number of committed devices currently listed on your subscription, you may see a warning message reminding you to update the number of committed devices on the relevant subscription.
 
 **To edit a plan:**
 
@@ -94,7 +94,7 @@ For example, you may have more devices that require monitoring if you're increas
    - Update the number of [committed devices](#calculate-committed-devices-for-ot-monitoring)
    - Update the number of sites (annual commitments only)
 
-1. Select the **I accept the terms** option, and then select **Purchase**.
+1. Select the **I accept the terms and conditions** option, and then select **Purchase**.
 
 1. After any changes are made, make sure to reactivate your sensors. For more information, see [Reactivate an OT sensor](how-to-manage-sensors-on-the-cloud.md#reactivate-an-ot-sensor).