Important Notice

All SDKs have now been moved in their own repositories (see links below). We are not accepting pull-requests on this repository anymore.

This repository serves as a landing page for all Azure IoT SDKs, each being maintained in their own repository, including sample code and documentation. Visit this page to learn more about Azure IoT SDKs.

Visit http://azure.com/iotdev to learn more about developing applications for Azure IoT.

The Microsoft Azure IoT Device SDKs:

• Azure IoT Device SDK for C written in ANSI C (C99) for portability and broad platform compatibility. There are two device client libraries for C, the low-level iothub_ll_client and the iothub_client (threaded).
• Azure IoT Device SDK for Python
• Azure IoT Device SDK for Node.js
• Azure IoT Device SDK for Java
• Azure IoT Device SDK for .NET

The Microsoft Azure IoT Service SDKs:

• Azure IoT Service SDK for C written in ANSI C (C99) for portability and broad platform compatibility. There are two service client libraries for C, the low-level iothub_messaging_ll and iothub_messaging.
• Azure IoT Service SDK for Python
• Azure IoT Service SDK for Node.js
• Azure IoT Service SDK for Java
• Azure IoT Service SDK for .NET

See individual repositories for details.

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.

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 guideline for the corresponding repo.

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 the individual SDKs repositories, 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.

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.

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.)

Please see each language repo for details.