This repository contains both IoT device SDKs and IoT service SDKs. Device SDKs enable you connect client devices to Azure IoT Hub. Service SDKs enable you to manage your IoT Hub service instance.

The Microsoft Azure IoT device SDK for .NET contain code that facilitate building devices and applications that connect to and are managed by Azure IoT Hub services.

Devices and data sources in an IoT solution can range from a simple network-connected sensor to a powerful, standalone computing device. Devices may have limited processing capability, memory, communication bandwidth, and communication protocol support. The IoT device SDKs enable you to implement client applications for a wide variety of devices.

Each language SDK includes sample code and documentation in addition to the library code. The API reference documentation is here.

Visit Azure IoT Dev Center to learn more about developing applications for Azure IoT.

Azure IoT device SDKs can be used with a broad range of OS platforms and devices. The minimum requirements are for the device platform to support the following:

• Being capable of establishing an IP connection: only IP-capable devices can communicate directly with Azure IoT Hub.
• Support TLS: required to establish a secure communication channel with Azure IoT Hub.
• Support SHA-256: necessary to generate the secure token for authenticating the device with the service.
• Have a Real Time Clock or implement code to connect to an NTP server: necessary for both establishing the TLS connection and generating the secure token for authentication.
• Having at least 64KB of RAM: the memory footprint of the SDK depends on the SDK and protocol used as well as the platform targeted. The smallest footprint is achieved using the C SDK targeting microcontrollers.

You can find an exhaustive list of the OS platforms the various SDKs have been tested against in the Azure Certified for IoT device catalog. Note that you might still be able to use the SDKs on OS and hardware platforms that are not listed on this page: all the SDKs are open sourced and designed to be portable. If you have suggestions, feedback or issues to report, refer to the Contribution and Support sections below.

Whithin the repository, you can find various types of simple samples that can help you get started. Below is a complete list of all these simple samples. In addition to these simple samples, you can find a long list of getting started guides that describe all the steps necessary to run the simple samples on a wide variety of devices and platforms. And if you are looking for end to end samples that show how to do simple analytics and processing of the data generated by your device using Azure services such as Stream Analytics, Big Data, Machine Learning and others, check out our E2E samples gallery.

• C# device SDK:
  • Simple .NET sample using AMQP: Shows how to connect to IoT Hub and send and receive raw messages using the AMQP protocol.
  • Simple .NET sample using HTTP: Shows how to connect to IoT Hub and send and receive raw messages using the HTTP protocol.
  • Simple .NET sample using MQTT: Shows how to connect to IoT Hub and send and receive raw messages using the MQTT protocol.
  • Simple UWP C++ sample: Shows how to connect to IoT Hub and send and receive raw messages in a C++ UWP (Universal Windows Platform) application.
  • Simple UWP JS sample: Shows how to connect to IoT Hub and send and receive raw messages in a JavaScript UWP application.
  • Simple UWP C# sample: Shows how to connect to IoT Hub and send and receive raw messages in a C# UWP application.
  • Simple .NET Micro Framework 4.3 sample: Shows how to connect to IoT Hub and send and receive raw messages from a device running .NET Micro Framework 4.3.
  • Simple .NET Micro Framework 4.4 sample: Shows how to connect to IoT Hub and send and receive raw messages from a device running .NET Micro Framework 4.4.

If you encounter any bugs, have suggestions for new features or if you would like to become an active contributor to this project please follow the instructions provided in the contribution guidelines.

If you are having issues using one of the packages or using the Azure IoT Hub service that go beyond simple bug fixes or help requests that would be dealt within the issues section of this project, the Microsoft Customer Support team will try and help out on a best effort basis. To engage Microsoft support, you can create a support ticket directly from the Azure portal. Escalated support requests for Azure IoT Hub SDKs development questions will only be available Monday thru Friday during normal coverage hours of 6 a.m. to 6 p.m. PST. Here is what you can expect Microsoft Support to be able to help with:

• Client SDKs issues: If you are trying to compile and run the libraries on a supported platform, the Support team will be able to assist with troubleshooting or questions related to compiler issues and communications to and from the IoT Hub. They will also try to assist with questions related to porting to an unsupported platform, but will be limited in how much assistance can be provided. The team will be limited with trouble-shooting the hardware device itself or drivers and or specific properties on that device.
• IoT Hub / Connectivity Issues: Communication from the device client to the Azure IoT Hub service and communication from the Azure IoT Hub service to the client. Or any other issues specifically related to the Azure IoT Hub.
• Portal Issues: Issues related to the portal, that includes access, security, dashboard, devices, Alarms, Usage, Settings and Actions.
• REST/API Issues: Using the IoT Hub REST/APIs that are documented in the documentation.

In addition to the language SDKs, this repository (azure-iot-sdks) contains the following folders:

This folder contains various build scripts to build the libraries.

This folder contains the following documents that are relevant to all the language SDKs:

• Set up IoT Hub describes how to configure your Azure IoT Hub service.
• Manage IoT Hub describes how to provision devices in your Azure IoT Hub service.
• FAQ contains frequently asked questions about the SDKs and libraries.
• Azure Certified for IoT device catalog.

The project offers a Long Term Support (LTS) version to allow users that do not need the latest features to be shielded from unwanted changes.

A new LTS version will be created every 6 months. The lifetime of an LTS branch is currently planned for one year. LTS branches receive all bug fixes that fall in one of these categories:

• security bugfixes
• critical bugfixes (crashes, memory leaks, etc.)

No new features or improvements will be picked up in an LTS branch.

LTS branches are named lts_mm_yyyy, where mm and yyyy are the month and year when the branch was created. An example of such a branch is lts_07_2017.

Below is a table showing the mapping of the LTS branches to the packages released

• ¹ All scheduled dates are subject to change by the Azure IoT SDK team.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.