Skip to content
Azure Client Tools
C++ C# C Batchfile
Branch: master
Clone or download
mohandatla Merge pull request #53 from ms-iot/minorfix
Update the default plug-ins data path and update correct command names
Latest commit b9277f0 Aug 22, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE GA staged changes. Apr 23, 2019
code Update the default plug-ins data path and update correct command names Aug 22, 2019
deps Update Azure CSDK to release 2019_07_01 Aug 8, 2019
docs Release update for 2.0.0.5 Aug 19, 2019
downloads Update zip files Aug 22, 2019
scripts Update the default plug-ins data path and update correct command names Aug 22, 2019
.gitattributes Add VS extensions to the crlf list. May 17, 2019
.gitignore
.gitmodules Update Azure CSDK to release 2019_07_01 Aug 8, 2019
LICENSE Initial Population. Jan 9, 2019
README.md Doc update: remove "public preview". May 1, 2019

README.md

Azure Client Tools

Overview

The Azure Client Tools is a collection of open-source libraries and executables that enable OEMs to rapidly build a device provisioning and management client that can be managed remotely through various Azure IoT services.

The code shared on this repo can be used as-is, or if desired, the OEM is free to modify or extend it to meet their specific needs.

Below is an overview of what each tool offers and links for more details if needed.

Azure IoT Device Agent

The Azure IoT Device Agent is a service that enables the remote management of various platform components through Azure IoT Hub. It can be easily extended to enable more platform or OEM's components to be remotely managed too.

For more details, visit the Azure IoT Device Agent page.

DPS Client APIs

The DPS Client APIs are a set of C APIs that allow a device client to provision a device with an Azure IoT Hub identity using the Azure Device Provisioning Service.

These APIs enable the creation of custom DPS clients or the integration of such functionality into other existing components on the system.

Note that this repo provides the Azure IoT Device Agent, which has an integrated DPS client and can be used as-is without writing any new code (i.e. without having to learn the DPS Client APIs). Only consider writing your own DPS client if the Device Agent provisioning does not meet your needs.

For more details, visit the DPS Client API Documentation page.

Limpet

Limpet.exe allows local processess to use TPM for storing azure connection strings, retrieve SAS tokens, register the device with IoTHub using azure DPS service and many more.

For more details, visit the Limpet page.

You can’t perform that action at this time.