Azure RTOS Pricing and Features: Embedded Real-Time Operating System
Azure RTOS (now Eclipse ThreadX) is an embedded real-time operating system designed for deeply constrained IoT devices with as little as 2 KB of RAM. Originally known as ThreadX, this RTOS powers over 12 billion device deployments worldwide across consumer electronics, industrial automation, medical devices, and automotive systems. Microsoft acquired ThreadX in 2019 and contributed it to the Eclipse Foundation in 2023, making it freely available under a permissive open-source license. EPC Group advises enterprise clients on IoT device strategy, including RTOS selection and Azure cloud integration for embedded device fleets.
Overview of Azure RTOS (Eclipse ThreadX)
Azure RTOS is a comprehensive embedded development suite that includes the ThreadX real-time kernel and a set of middleware components for networking, file systems, USB, and GUI. The RTOS is optimized for microcontroller-based devices (MCU) running ARM Cortex-M, RISC-V, and other embedded processors that require deterministic, real-time response times measured in microseconds.
Unlike Linux-based embedded solutions, Azure RTOS has an extremely small memory footprint (starting at 2 KB ROM, 1 KB RAM for the kernel), fast boot times (microseconds), and deterministic scheduling that guarantees worst-case response times. This makes it suitable for safety-critical applications in medical devices, automotive systems, and industrial control where predictable timing is a hard requirement.
Important update: In November 2023, Microsoft contributed Azure RTOS to the Eclipse Foundation, where it is now maintained as Eclipse ThreadX. The technology is functionally identical, and existing deployments continue to operate. EPC Group helps clients navigate this transition and plan their embedded device strategy accordingly.
- ThreadX kernel: Preemptive, priority-based real-time scheduler with picokernel architecture
- NetX Duo: Dual IPv4/IPv6 TCP/IP networking stack optimized for embedded devices
- FileX: FAT-compatible embedded file system for flash and SD card storage
- GUIX: Embedded GUI framework for touchscreen and display devices
- USBX: USB host and device stack for USB connectivity
- LevelX: Flash wear-leveling for NAND and NOR flash memory
Key Features
- Picokernel architecture: Minimal kernel footprint with sub-microsecond context switching
- Deterministic scheduling: Guaranteed worst-case response times for real-time applications
- Preemption-threshold: Unique scheduling mechanism that reduces context switches while maintaining responsiveness
- Event chaining: Automatic notification of thread state changes without polling
- Memory pools: Block and byte memory allocation with deterministic performance
- Timer services: Hardware-independent software timers with callback functions
- Safety certifications: IEC 61508 SIL 4, IEC 62304 Class C, ISO 26262 ASIL D, EN 50128 SIL 4
- Secure communication: TLS/DTLS support via NetX Secure for encrypted device communication
- Azure IoT middleware: Built-in Azure IoT Hub client for cloud connectivity from constrained devices
- Wide MCU support: Runs on ARM Cortex-M, ARM Cortex-A, RISC-V, Renesas, Microchip, and other MCU families
Pricing
Azure RTOS (Eclipse ThreadX) is now fully open-source and free to use, removing all licensing barriers for embedded device development.
Open Source (Eclipse ThreadX)
- Free under the MIT license (no per-device royalties)
- Full source code available on GitHub
- Community support through Eclipse Foundation
- No usage restrictions for commercial products
Commercial Support
- Commercial support available through Eclipse Foundation partners
- Safety-certified versions with documentation packages available from certified vendors
- MCU vendor BSPs (Board Support Packages) included with many development kits
Azure Cloud Connectivity Costs
- Azure IoT Hub pricing applies when connecting ThreadX devices to Azure
- Azure Device Provisioning Service: Free for IoT Hub-connected devices
- Azure Device Update: Approximately $0.005 per device per month for OTA updates
Enterprise Use Cases
- Medical devices: FDA-regulated devices requiring IEC 62304 certification with deterministic real-time performance
- Industrial automation: PLC controllers, motor drives, and sensor nodes requiring sub-millisecond response times
- Automotive: ADAS components, infotainment systems, and vehicle control modules requiring ISO 26262 compliance
- Consumer electronics: Wearables, smart home devices, and connected appliances with constrained hardware budgets
- Building automation: HVAC controllers, lighting systems, and access control devices on BACnet/IP networks
- Energy and utilities: Smart meters, grid sensors, and power distribution controllers with long lifecycle requirements
Integration with Azure Services
- Azure IoT Hub: Built-in IoT Hub client in the Azure IoT middleware for cloud telemetry and device management
- Azure Device Provisioning Service: Zero-touch device provisioning with X.509 certificates or TPM attestation
- Azure Device Update: Over-the-air firmware updates for deployed ThreadX devices
- Azure Defender for IoT: Security monitoring agent for detecting threats on constrained devices
- Azure IoT Central: Managed cloud interface for monitoring and managing ThreadX device fleets
- Azure Sphere: Companion security service for internet-connected MCU devices
Best Practices for Enterprise Deployments
- Select the right MCU: Profile your application's RAM, ROM, CPU, and peripheral requirements before choosing hardware
- Use vendor BSPs: Start with the MCU vendor's Board Support Package to accelerate hardware bring-up
- Plan for safety certification: If targeting medical or automotive markets, budget for safety certification from the project start
- Implement secure boot: Use hardware root of trust (TPM or secure element) for verified boot and firmware authentication
- Design for OTA updates: Architect firmware with A/B partitions to support reliable over-the-air updates with rollback
- Use TLS for all communications: Configure NetX Secure for encrypted communication with Azure IoT Hub
- Monitor device fleet health: Use Azure IoT Hub device twins and reported properties for centralized fleet monitoring
- Document your RTOS configuration: Track thread priorities, stack sizes, and timer configurations for maintainability
Why Choose EPC Group for Embedded IoT Strategy
With 28+ years of enterprise Microsoft consulting, EPC Group helps organizations design end-to-end IoT solutions that span from embedded devices running Azure RTOS/ThreadX to cloud analytics in Azure. Our team advises on RTOS selection, Azure IoT architecture design, device security strategy, and fleet management at scale.
We specialize in regulated industries where safety certification (IEC 62304, ISO 26262), security compliance (HIPAA for medical IoT, NIST for government), and long device lifecycles are critical requirements. Our approach connects device-level engineering decisions to enterprise cloud architecture for a coherent, manageable IoT ecosystem.
Ready to Build Your IoT Device Strategy?
Contact our IoT architects for a free consultation on your embedded device and cloud integration requirements. We will assess your hardware platform, recommend the optimal RTOS configuration, and design the Azure cloud architecture for your device fleet.
Frequently Asked Questions
Is Azure RTOS the same as Eclipse ThreadX?
Yes. In November 2023, Microsoft contributed Azure RTOS to the Eclipse Foundation, where it was renamed Eclipse ThreadX. The codebase, architecture, and functionality remain the same. Existing deployments continue to work, and the open-source community now maintains and evolves the project under the Eclipse umbrella with a permissive MIT license.
How does Azure RTOS compare to FreeRTOS?
Both are real-time operating systems for microcontrollers. ThreadX has a smaller kernel footprint (2 KB ROM vs. approximately 5–10 KB for FreeRTOS), offers unique scheduling features like preemption-threshold, and has extensive safety certifications (IEC 61508, IEC 62304, ISO 26262). FreeRTOS has a larger community and AWS IoT integration. Choose ThreadX when you need safety certification or minimal footprint; choose FreeRTOS for AWS-centric IoT or broader community ecosystem.
What microcontrollers support Azure RTOS?
Azure RTOS/ThreadX supports a wide range of MCU families including ARM Cortex-M (M0, M0+, M3, M4, M7, M23, M33, M55), ARM Cortex-A, RISC-V, Renesas RX/RA, Microchip PIC32/SAM, NXP i.MX RT, STMicroelectronics STM32, and many others. Most MCU vendors include ThreadX BSPs with their development kits and IDEs.
Can Azure RTOS devices connect to Azure IoT Hub?
Yes. The Azure IoT middleware for ThreadX provides a native IoT Hub client library optimized for constrained devices. It supports device-to-cloud telemetry, cloud-to-device commands, device twins, direct methods, and device provisioning. The middleware uses NetX Duo for TCP/IP and NetX Secure for TLS encryption, providing end-to-end secure connectivity from MCU to cloud.
Is Azure RTOS suitable for medical devices?
Yes. Azure RTOS/ThreadX holds IEC 62304 Class C safety certification, which is the highest classification for medical device software. This certification, combined with deterministic real-time performance and extensive documentation, makes it suitable for Class II and Class III medical devices regulated by the FDA. EPC Group advises medical device companies on embedded software strategy and Azure cloud integration for connected medical devices.