Bilješka
Pristup ovoj stranici zahtijeva provjeru vjerodostojnosti. Možete pokušati da se prijavite ili promijenite direktorije.
Pristup ovoj stranici zahtijeva provjeru vjerodostojnosti. Možete pokušati promijeniti direktorije.
This article explains how to provision the standalone Microsoft Defender for IoT micro agent by using Azure IoT Hub Device Provisioning Service with X.509 certificate attestation. Follow this procedure to enroll a standalone device through DPS, create and configure a micro agent module, and verify that the agent connects successfully. If you're provisioning IoT Edge devices instead, see the Edge-device guidance linked below.
To learn how to configure the Microsoft Defender for IoT micro agent for Edge devices see Create and provision IoT Edge devices at scale
Note
Defender for IoT plans to retire the micro agent on June 1, 2027.
Prerequisites
Before you begin, make sure you have the following prerequisites:
An Azure account with an active subscription. For more information, see Create an Azure account.
An IoT hub.
Provision the device through DPS
Perform the following steps to provision the device through DPS:
In the Azure portal, go to your instance of the IoT Hub device provisioning service.
Under Settings, select Manage enrollments.
Select Add individual enrollment, and then complete the steps to configure the enrollment:
- In the Mechanism field, select X.509 at the identity attestation Mechanism and choose your CA.
Navigate into your destination IoT Hub.
Create a Defender for IoT micro agent module twin issued by the same X.509 certificate used for the DPS enrollment.
Configure the micro agent to use the created module (note that the device does not have to exist yet).
Navigate back to DPS and provision the device through DPS.
Navigate to the configured device in the destination IoT Hub.
Create a new module for the device issued by the same CA certificate used for the DPS enrollment.
Run the micro agent that you configured to use the created module to confirm it connects to the device.
Note
While you don't need the device to exist before configuring the agent when using this procedure, you do need to know the device name in advance in order to issue the certificate for the final module correctly.