| title | description | author | ms.author | ms.topic | ms.date | ms.custom | ms.service |
|---|---|---|---|---|---|---|---|
Edge Managed Certification Requirements |
Edge Managed Certification Requirements |
cbroad |
cbroad |
conceptual |
03/15/2021 |
Edge Managed Certification Requirements |
certification |
This document outlines the device specific capabilities that will be represented in the Azure Certified Device catalog. A capability is singular device attribute that may describe the device.
Edge Managed certification, an incremental certification beyond the baseline Azure Certified Device certification. Edge Managed focuses on device management standards for Azure connected devices and validates the IoT Edge runtime compatibility for module deployment and management. (Previously, this program was identified as the IoT Edge certification program.)
Edge Managed certification validates IoT Edge runtime compatibility for module deployment and management. This program provides confidence in the management of Azure connected IoT devices.
The Edge Managed certification requires that all requirements from the Azure Certified Device baseline program.
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
| Name | AzureReady.DPS |
|---|---|
| Target Availability | Available now |
| Applies To | Any device |
| OS | Agnostic |
| Validation Type | Automated |
| Validation | AICS validates the device code support DPS. 1. User has to 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. 3. Then, user will hit ‘Connect’ button to connect to AICS managed IoT Hub via DPS |
| Resources | |
| Azure Recommended: | N/A |
Edge runtime exists: The purpose of test is to make sure the device contains IoT Edge runtime ($edgehub and $edgeagent) are functioning correctly.
| Name | EdgeManaged.EdgeRT |
|---|---|
| Target Availability | Available now |
| Applies To | IoT Edge device |
| OS | Tier1 and Tier2 OS |
| Validation Type | Automated |
| Validation | AICS validates the deploy-ability of the installed IoT Edge RT. 1. User needs to specify specific OS (OS not on the list of Tier1/2 are not accepted) 2. AICS generates its config.yaml and deploys canonical simulated temp sensor edge module 3. AICS validates that docker compatible container subsystem (Moby) is installed on the device 4. Test result is determined based on successful deployment of the simulated temp sensor edge module and functionality of docker compatible container subsystem |
| Resources | a) AICS blog, b) Certification steps (has all the additional resources), c) Requirements |
| Azure Recommended: | N/A |
IoT Edge easy setup: The purpose of test is to make sure IoT Edge device is easy to set up and validates IoT Edge runtime is preinstalled during physical device validation
| Name | EdgeManaged.PhysicalDevice |
|---|---|
| Target Availability | Available now (currently on hold due to COVID-19) |
| Applies To | IoT Edge device |
| OS | Tier1 and Tier2 OS |
| Validation Type | Manual / Lab Verified |
| Validation | OEM must ship the physical device to IoT administration (HCL). HCL performs manual validation on the physical device to check: 1. EdgeRT is using Moby subsystem (allowed redistribution version). Not docker 2. Pick the latest edge module to validate ability to deploy edge. |
| Resources | a) AICS blog, b) Certification steps , c) Requirements |
| Azure Recommended: | N/A |