Add Windows support for group enrollment; add release asset table

Author: kgremban

articles/iot-edge/how-to-auto-provision-x509-certs.md

@@ -5,7 +5,7 @@ author: kgremban
 manager: philmea
 ms.author: kgremban
 ms.reviewer: kevindaw
-ms.date: 03/02/2020
+ms.date: 03/06/2020
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
@@ -27,7 +27,6 @@ Using X.509 certificates as an attestation mechanism is an excellent way to scal
 
 * An active IoT Hub.
 * A physical or virtual device to be the IoT Edge device.
-  * Currently, group enrollment for IoT Edge is only supported for Linux devices.
 * The latest version of [Git](https://git-scm.com/download/) installed.
 * An instance of the IoT Hub Device Provisioning Service in Azure, linked to your IoT hub.
   * If you don't have a Device Provisioning Service instance, follow the instructions in [Set up the IoT Hub DPS](../iot-dps/quick-setup-auto-provision.md).
@@ -108,9 +107,6 @@ Now that an enrollment exists for this device, the IoT Edge runtime can automati
 
 Use your generated certificates and keys to create a group enrollment in DPS for multiple IoT Edge devices. Group enrollments use an intermediate or root CA certificate from the certificate chain of trust used to generate the individual device identity certificates.
 
->[!NOTE]
->Currently, group enrollment is only supported for IoT Edge on Linux devices.
-
 If you're looking to provision a single IoT Edge device instead, follow the steps in the previous section, [Create a DPS individual enrollment](#create-a-dps-individual-enrollment).
 
 When you create an enrollment in DPS, you have the opportunity to declare an **Initial Device Twin State**. In the device twin, you can set tags to group devices by any metric you need in your solution, like region, environment, location, or device type. These tags are used to create [automatic deployments](how-to-deploy-monitor.md).

articles/iot-edge/support.md

@@ -4,7 +4,7 @@ description: Learn which operating systems can run the Azure IoT Edge daemon and
 author: kgremban
 manager: philmea
 ms.author: kgremban
-ms.date: 08/13/2019
+ms.date: 03/06/2020
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
@@ -20,7 +20,7 @@ If you experience problems while using the Azure IoT Edge service, there are sev
 
 **Microsoft Customer Support team** – Users who have a [support plan](https://azure.microsoft.com/support/plans/) can engage the Microsoft Customer Support team by creating a support ticket directly from the [Azure portal](https://ms.portal.azure.com/signin/index/?feature.settingsportalinstance=mpac).
 
-**Feature requests** – The Azure IoT Edge product tracks feature requests via the product’s [User Voice page](https://feedback.azure.com/forums/907045-azure-iot-edge).
+**Feature requests** – The Azure IoT Edge product tracks feature requests via the product's [User Voice page](https://feedback.azure.com/forums/907045-azure-iot-edge).
 
 ## Container engines
 
@@ -92,6 +92,28 @@ The systems listed in the following table are considered compatible with Azure I
 sudo apt-get install libssl1.0.2
 ```
 
+## Releases
+
+IoT Edge release assets and release notes are available on the [azure-iotedge releases](https://github.com/Azure/azure-iotedge/releases) page. This section reflects information from those release notes to help you visualize the components of each version more easily.
+
+IoT Edge components can be installed or updated individually, and are backwards compatible with components from older versions. The following table lists the components included in each release:
+
+| Release   | Security daemon  | Edge hub<br>Edge agent | Libiothsm | Moby  |
+| --------- | ---------------- | ---------------------- | --------- | ----- |
+| **1.0.9** | 1.0.9            | 1.0.9                  | 1.0.9     |       |
+| **1.0.8** | 1.0.8            | 1.0.8.5<br>1.0.8.4<br>1.0.8.3<br>1.0.8.2<br>1.0.8.1<br>1.0.8 | 1.0.8 | 3.0.6 |
+| **1.0.7** | 1.0.7.1<br>1.0.7 | 1.0.7.1<br>1.0.7       | 1.0.7.1<br>1.0.7 | 3.0.5<br>3.0.4 (ARMv7hl, CentOS) |
+| **1.0.6** | 1.0.6.1<br>1.0.6 | 1.0.6.1<br>1.0.6       | 1.0.6.1<br>1.0.6 |  |
+| **1.0.5** | 1.0.5            | 1.0.5                  | 1.0.5     | 3.0.2 |
+
+IoT Edge uses the Microsoft.Azure.Device.Client SDK. For more information, see the [Azure IoT C# SDK GitHub repo](https://github.com/Azure/azure-iot-sdk-csharp) or the [Azure SDK for .NET reference content](https://docs.microsoft.com/dotnet/api/overview/azure/iot/client?view=azure-dotnet). The following list shows the version of the client SDK that each release is tested against:
+
+* **IoT Edge 1.0.9**: Client SDK 1.21.1
+* **IoT Edge 1.0.8**: Client SDK 1.20.3
+* **IoT Edge 1.0.7**: Client SDK 1.20.1
+* **IoT Edge 1.0.6**: Client SDK 1.17.1
+* **IoT Edge 1.0.5**: Client SDK 1.17.1
+
 ## Virtual Machines
 
 Azure IoT Edge can be run in virtual machines. Using a virtual machine as an IoT Edge device is common when customers want to augment existing infrastructure with edge intelligence. The family of the host VM OS must match the family of the guest OS used inside a module's container. This requirement is the same as when Azure IoT Edge is run directly on a device. Azure IoT Edge is agnostic of the underlying virtualization technology and works in VMs powered by platforms like Hyper-V and vSphere.
@@ -109,7 +131,7 @@ Azure IoT Edge runs great on devices as small as a Raspberry Pi3 to server grade
 Experience while prototyping will help guide your final device selection. Questions you should consider include:
 
 * How many modules are in your workload?
-* How many layers do your modules’ containers share?
+* How many layers do your modules' containers share?
 * In what language are your modules written?
 * How much data will your modules be processing?
 * Do your modules need any specialized hardware for accelerating their workloads?