Merge pull request #93095 from chrissie926/master

Update concepts-device.md

Author: PRMerger10

articles/iot-dps/concepts-device.md

@@ -39,7 +39,7 @@ Device secrets may also be stored in software (memory), but it is a less secure
 
 ## Registration ID
 
-The registration ID is used to uniquely identify a device in the Device Provisioning Service. The registration ID must be unique in the provisioning service [ID scope](#id-scope). Each device must have a registration ID. The registration ID is alphanumeric, lowercase, and may contain hyphens.
+The registration ID is used to uniquely identify a device in the Device Provisioning Service. The device ID must be unique in the provisioning service [ID scope](#id-scope). Each device must have a registration ID. The registration ID is alphanumeric, case insensitive, and may contain special characters including colon, period, underscore and hyphen.
 
 * In the case of TPM, the registration ID is provided by the TPM itself.
 * In the case of X.509-based attestation, the registration ID is provided as the subject name of the certificate.

articles/iot-edge/how-to-auto-provision-simulated-device-windows.md

@@ -15,6 +15,8 @@ ms.custom: seodec18
 
 Azure IoT Edge devices can be auto-provisioned using the [Device Provisioning Service](../iot-dps/index.yml) just like devices that are not edge-enabled. If you're unfamiliar with the process of auto-provisioning, review the [auto-provisioning concepts](../iot-dps/concepts-auto-provisioning.md) before continuing.
 
+DPS supports symmetric key attestation for IoT Edge devices in both individual enrollment and group enrollment. For group enrollment, if you check “is IoT Edge device” option to be true in symmetric key attestation, all the devices that are registered under that enrollment group will be marked as IoT Edge devices. 
+
 This article shows you how to test auto-provisioning on a simulated IoT Edge device with the following steps:
 
 * Create an instance of IoT Hub Device Provisioning Service (DPS).