You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|**Validation**| Device supports easy input of target DPS ID scope ownership without needing to recompile the embedded code. Microsoft provides the [portal workflow](https://certify.azure.com) to execute the tests to validate that the device supports DPS **1.** User must select one of the attestation methods (X.509, TPM and SAS key) **2.** Depending on the attestation method, user needs to take corresponding action such as **a)** Upload X.509 cert to AICS managed DPS scope **b)** Implement SAS key or endorsement key into the device |
49
+
|**Validation**| Device supports easy input of target DPS ID scope ownership. Microsoft provides the [portal workflow](https://certify.azure.com) to execute the tests to validate that the device supports DPS **1.** User must select one of the attestation methods (X.509, TPM and SAS key) **2.** Depending on the attestation method, user needs to take corresponding action such as **a)** Upload X.509 cert to AICS managed DPS scope **b)** Implement SAS key or endorsement key into the device |
50
50
|**Resources**|[Device provisioning service overview](../iot-dps/about-iot-dps.md)|
51
51
52
52
**[If implemented] Cloud to device: The purpose of test is to make sure messages can be sent from cloud to devices**
|**Validation**| Device must send any telemetry schemas to IoT Hub. Microsoft provides the [portal workflow](https://certify.azure.com) to execute the tests. Device twin property (if implemented) **1.** AICS validates the read/write-able property in device twin JSON **2.** User has to specify the JSON payload to be changed **3.** AICS validates the specified desired properties sent from IoT Hub and ACK message received by the device |
83
83
|**Resources**|**a)**[Certification steps](./overview.md) (has all the additional resources) **b)**[Use device twins with IoT Hub](../iot-hub/iot-hub-devguide-device-twins.md)|
84
+
85
+
**[Required] Limit Recompile: The purpose of this policy ensures devices by default should not need users to re-compile code to deploy the device.**
|**Validation**| To simplify device configuration for users, we require all devices can be configured to connect to Azure without the need to recompile and deploy device source code. This includes DPS information, such as Scope ID, which should be set as configuration settings and not compiled. However, if your device contains certain secure hardware or if there are extenuating circumstances in which the user will expect to compile and deploy code, contact the certification team to request an exception review. |
94
+
|**Resources**|**a)**[Device provisioning service overview](../iot-dps/about-iot-dps.md)**b)**[Sample config file for DPS ID Scope transfer](https://github.com/Azure/azure-iot-sdk-c/tree/public-preview-pnp/serializer/samples/devicetwin_simplesample)|
Copy file name to clipboardExpand all lines: articles/certification/program-requirements-pnp.md
+3-13Lines changed: 3 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,9 @@ IoT Plug and Play Preview enables solution builders to integrate smart devices w
20
20
Promise of IoT Plug and Play certification are:
21
21
22
22
1. Defined device models and interfaces are compliant with the [Digital Twin Definition Language](https://github.com/Azure/opendigitaltwins-dtdl)
23
-
2.Secure provisioning and easy transfer of ID scope ownership in Device Provisioning Services
24
-
3.Easy integration with Azure IoT based solutions using the [Digital Twin APIs](../iot-pnp/concepts-digital-twin.md) : Azure IoT Hub and Azure IoT Central
25
-
4.Validated product truth on certified devices
23
+
1.Easy integration with Azure IoT based solutions using the [Digital Twin APIs](../iot-pnp/concepts-digital-twin.md) : Azure IoT Hub and Azure IoT Central
24
+
1.Validated product truth on certified devices
25
+
1.Meets all requirements of [Azure Certified Device](./program-requirements-azure-certified-device.md)
26
26
27
27
## Requirements
28
28
@@ -37,16 +37,6 @@ Promise of IoT Plug and Play certification are:
37
37
|**Validation**| Device must send any telemetry schemas to IoT Hub. Microsoft provides the [portal workflow](https://certify.azure.com) to execute the tests. Device to cloud (required): **1.** Validates that the device can send message to AICS managed IoT Hub **2.** User must specify the number and frequency of messages. **3.** AICS validates the telemetry is received by the Hub instance |
38
38
|**Resources**|[Certification steps](./overview.md) (has all the additional resources) |
39
39
40
-
**[Required] DPS: The purpose of test is to check the device implements and supports IoT Hub Device Provisioning Service with one of the three attestation methods**
|**Validation**| Device must implement easy transfer of DPS ID Scope ownership without needing to recompile the embedded code. Microsoft provides the [portal workflow](https://certify.azure.com) to execute the tests to validate that the device supports DPS **1.** User must select one of the attestation methods (X.509, TPM and SAS key) **2.** Depending on the attestation method, user needs to take corresponding action such as **a)** Upload X.509 cert to AICS managed DPS scope **b)** Implement SAS key or endorsement key into the device |
49
-
|**Resources**|**a)**[Device provisioning service overview](../iot-dps/about-iot-dps.md), **b)**[Sample config file for DPS ID Scope transfer](https://github.com/Azure/azure-iot-sdk-c/tree/public-preview-pnp/serializer/samples/devicetwin_simplesample)|
50
40
51
41
**[Required] DTDL v2: The purpose of test to ensure defined device models and interfaces are compliant with the Digital Twins Definition Language v2.**
0 commit comments