Merge pull request #199908 from v-dmankowitz/trends

Trends

Author: PRMerger-2

articles/defender-for-iot/organizations/how-to-create-trends-and-statistics-reports.md

@@ -50,7 +50,7 @@ Protocol dissection | Displays a pie chart that provides you with a look at the
 Active TCP connections | Displays a chart that shows the number of active TCP connections in the system.
 Incident by type | Displays a pie chart that shows the number of incidents by type. This is the number of alerts generated by each engine over a predefined time period.
 Devices by vendor | Displays a pie chart that shows the number of devices by vendor. The number of devices for a specific vendor is proportional to the size of that device’s vendor part of the disk relative to other device vendors.
-Number of devices per VLAN | Displays a pie chart that shows the number of discovered devices per VLAN. The size of each slice of the pie is proportional to the number of discovered devices relative to the other slices. Each VLAN appears with the VLAN tag assigned by the sensor or name that you have manually added.
+Number of devices per VLAN | Displays a pie chart that shows the number of discovered devices per VLAN. The size of each slice of the pie is proportional to the number of discovered devices relative to the other slices. Each VLAN appears with the VLAN tag assigned by the sensor or name that you've manually added.
 Top bandwidth by VLAN | Displays the bandwidth consumption by VLAN. By default, the widget shows five VLANs with the highest bandwidth usage. You can filter the data by the period presented in the widget. Select the down arrow to show more results.
 
 

articles/defender-for-iot/organizations/how-to-install-software.md

@@ -185,7 +185,7 @@ This procedure describes how to add a secondary NIC if you've already installed
 
 ### Find your port
 
-If you are having trouble locating the physical port on your device, you can use the following command to find your port:
+If you're having trouble locating the physical port on your device, you can use the following command to find your port:
 
 ```bash
 sudo ethtool -p <port value> <time-in-seconds>

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

@@ -9,15 +9,15 @@ ms.topic: how-to
 
 Your Defender for IoT deployment is managed through your Microsoft Defender for IoT account subscriptions. You can onboard, edit, and offboard your subscriptions to Defender for IoT in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started).
 
-For each subscription, you will be asked to define a number of *committed devices*. Committed devices are the approximate number of devices that will be monitored in your enterprise. 
+For each subscription, you'll be asked to define a number of *committed devices*. Committed devices are the approximate number of devices that will be monitored in your enterprise. 
 
 > [!NOTE]
 > If you've come to this page because you are a [former CyberX customer](https://blogs.microsoft.com/blog/2020/06/22/microsoft-acquires-cyberx-to-accelerate-and-secure-customers-iot-deployments) and have questions about your account, reach out to your account manager for guidance.
 
 
 ## Subscription billing
 
-You are billed based on the number of committed devices associated with each subscription.
+You're billed based on the number of committed devices associated with each subscription.
 
 The billing cycle for Microsoft Defender for IoT follows a calendar month. Changes you make to committed devices during the  month are implemented one hour after confirming your update, and are reflected in your monthly bill. Subscription *offboarding* also takes effect one hour after confirming the offboard.
 
@@ -76,11 +76,11 @@ This section describes how to onboard a subscription.
 
 1. Select **Subscribe**.
 1. Confirm your subscription.
-1. If you have not done so already, onboard a sensor or Set up a sensor.
+1. If you haven't done so already, onboard a sensor or Set up a sensor.
 
 ## Update committed devices in a subscription
 
-You may need to update your subscription with more committed devices, or more fewer committed devices. More devices may require monitoring if, for example, you are increasing existing site coverage, discovered more devices than expected or there are network changes such as adding switches.
+You may need to update your subscription with more committed devices, or fewer committed devices. More devices may require monitoring if, for example, you are increasing existing site coverage, discovered more devices than expected or there are network changes such as adding switches.
 
 **To update a subscription:**
 1. Go to [Defender for IoT: Getting started](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started) in the Azure portal.

articles/defender-for-iot/organizations/how-to-manage-the-alert-event.md

@@ -209,8 +209,8 @@ Users working with alerts on the Defender for IoT portal on Azure should underst
  Parameter | Description
 |--|--|
 | **Alert Exclusion rules**|  Alert *Exclusion rules* defined in the on-premises management console impact the alerts triggered by managed sensors. As a result, the alerts excluded by these rules also won't be displayed in the Alerts page on the portal. For more information, see [Create alert exclusion rules](how-to-work-with-alerts-on-premises-management-console.md#create-alert-exclusion-rules).
-| **Managing alerts on your sensor**  | If you change the status of an alert, or learn or mute an alert on a sensor, the changes are not updated in the Defender for IoT Alerts page on the portal. This means that this alert will stay open on the portal. However another alert  won't be triggered from sensor for this activity.
-| **Managing alerts in the portal Alerts page** | Changing the status of an alert on the Azure portal, Alerts page or changing the alert severity on the portal, does not impact the alert status or severity in on-premises sensors.
+| **Managing alerts on your sensor**  | If you change the status of an alert, or learn or mute an alert on a sensor, the changes are not updated in the Defender for IoT Alerts page on the portal. This means that this alert will stay open on the portal. However another alert  won't be triggered from the sensor for this activity.
+| **Managing alerts in the portal Alerts page** | Changing the status of an alert on the Azure portal, Alerts page or changing the alert severity on the portal, doesn't impact the alert status or severity in on-premises sensors.
 
 ## Next steps
 

articles/defender-for-iot/organizations/how-to-set-up-snmp-mib-monitoring.md

@@ -1,7 +1,7 @@
 ---
 title: Set up SNMP MIB monitoring
 description: You can perform sensor health monitoring by using SNMP. The sensor responds to SNMP queries sent from an authorized monitoring server.
-ms.date: 01/31/2022
+ms.date: 05/31/2022
 ms.topic: how-to
 ---
 
@@ -35,7 +35,7 @@ Note that:
 
 ## Prerequisites for AES and 3-DES Encryption Support for SNMP Version 3
 - The network management station (NMS) must support Simple Network Management Protocol (SNMP) Version 3 to be able to use this feature.
-- It is important to understand the SNMP architecture and the terminology of the architecture to understand the security model used and how the security model interacts with the other subsystems in the architecture.
+- It's important to understand the SNMP architecture and the terminology of the architecture to understand the security model used and how the security model interacts with the other subsystems in the architecture.
 - Before you begin configuring SNMP monitoring, you need to open the port UDP 161 in the firewall.
 
 
@@ -50,7 +50,7 @@ Note that:
 
         | Parameter | Description |
         |--|--|
-        | **Username** | The SNMP username can contain up to 32 characters and include any combination of alphanumeric characters (uppercase letters, lowercase letters, and numbers). Spaces are not allowed. <br /> <br />The username for the SNMP v3 authentication must be configured on the system and on the SNMP server. |
+        | **Username** | The SNMP username can contain up to 32 characters and include any combination of alphanumeric characters (uppercase letters, lowercase letters, and numbers). Spaces aren't allowed. <br /> <br />The username for the SNMP v3 authentication must be configured on the system and on the SNMP server. |
         | **Password** | Enter a case-sensitive authentication password. The authentication password can contain 8 to 12 characters and include any combination of alphanumeric characters (uppercase letters, lowercase letters, and numbers). <br /> <br/>The username for the SNMP v3 authentication must be configured on the system and on the SNMP server. |
         | **Auth Type** | Select MD5 or SHA-1. |
         | **Encryption** | Select DES (56 bit key size)<sup>[1](#1)</sup> or AES (AES 128 bits supported)<sup>[2](#2)</sup>. |