Merge pull request #179118 from ElazarK/glosary-addition

added device inventory

Author: PRMerger18

articles/defender-for-iot/device-builders/references-defender-for-iot-glossary.md

@@ -1,7 +1,7 @@
 ---
 title: Defender for IoT glossary for device builder
 description: The glossary provides a brief description of important Defender for IoT platform terms and concepts.
-ms.date: 05/27/2021
+ms.date: 11/09/2021
 ms.topic: article
 ---
 
@@ -23,6 +23,7 @@ This glossary provides a brief description of important terms and concepts for t
 |--|--|--|
 | **Device twins** | Device twins are JSON documents that store device state information including metadata, configurations, and conditions. | [Module Twin](#m) <br /> <br />[Defender-IoT-micro-agent twin](#s) |
 | **Defender-IoT-micro-agent twin** `(DB)` | The Defender-IoT-micro-agent twin holds all of the information that is relevant to device security, for each specific device in your solution. | [Device twin](#d) <br /> <br />[Module Twin](#m) |
+| **Device inventory** | Defender for IoT identifies, and classifies devices as a single unique network device in the inventory for: <br><br> - Standalone IT, OT, and IoT devices with 1 or multiple NICs. <br><br> - Devices composed of multiple backplane components. This includes all racks, slots, and modules. <br><br> - Devices that act as network infrastructure. For example, switches, and routers with multiple NICs. <br><br> - Public internet IP addresses, multicast groups, and broadcast groups are not considered inventory devices. <br><br>Devices that have been inactive for more than 60 days are classified as inactive Inventory devices.|
 
 ## E