Skip to content

Commit 09af3f1

Browse files
authored
Merge pull request #89013 from nberdy/patch-6
Update concepts-service.md
2 parents ecdd48f + 9763c06 commit 09af3f1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/iot-dps/concepts-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Service concepts in Azure IoT Hub Device Provisioning Service | Microsoft
33
description: Describes service provisioning concepts specific to devices with the Device Provisioning Service and IoT Hub
44
author: nberdy
55
ms.author: nberdy
6-
ms.date: 04/04/2019
6+
ms.date: 09/18/2019
77
ms.topic: conceptual
88
ms.service: iot-dps
99
services: iot-dps
@@ -52,7 +52,7 @@ There are two types of enrollments supported by Device Provisioning Service:
5252

5353
### Enrollment group
5454

55-
An enrollment group is a group of devices that share a specific attestation mechanism. All devices in the enrollment group present X.509 certificates that have been signed by the same root or intermediate Certificate Authority (CA). Enrollment groups can only use the X.509 attestation mechanism. The enrollment group name and certificate name must be alphanumeric, lowercase, and may contain hyphens.
55+
An enrollment group is a group of devices that share a specific attestation mechanism. Enrollment groups support both X.509 as well as symmetric. All devices in the X.509 enrollment group present X.509 certificates that have been signed by the same root or intermediate Certificate Authority (CA). Each device in the symmetric key enrollment group present SAS tokens derived from the group symmetric key. The enrollment group name and certificate name must be alphanumeric, lowercase, and may contain hyphens.
5656

5757
> [!TIP]
5858
> We recommend using an enrollment group for a large number of devices that share a desired initial configuration, or for devices all going to the same tenant.

0 commit comments

Comments
 (0)