On 20 March 2026, Microsoft publicly announced that the Azure Sphere service is retiring and will stop supporting customer application, OS, bug and security updates, along with DAA certificate issuance, on 31 July 2031. This date will also mark the end of extended support for the MT3620 microcontroller.
Why is this happening?
Azure Sphere pioneered secure IoT connectivity, combining bespoke hardware, a secure Linux-based OS, and a cloud-based security service, elevating industry standards for microcontroller security. As the IoT landscape advances, customers are now able to access secure microcontrollers from a wide range of silicon vendors and pair these with Microsoft next-generation solutions for greater flexibility and scalability.
Key dates to be aware of
- Through 31 July 2031, Azure Sphere devices will continue to operate as they do today. After this date, devices will no longer receive application or OS updates, bug fixes, or security patches.
- After 31 July 2031, The Azure Sphere Service, including Device Attestation and Authentication (DAA), will be retired, which will affect device authentication and connectivity to Azure IoT and other upstream services.
- On 31 July 2026, the MT3620 silicon will become end-of-life, as announced by the silicon manufacturer.
These timelines are intentionally long to allow for thoughtful planning and validation.
What this means for your solutions
- Existing devices can continue running throughout the support period without interruption.
- Solutions that need to operate beyond the retirement timeframe will require updated hardware designs using alternative silicon.
- Customers with OEM license agreements will receive formal notice regarding support timelines. If additional production is required ahead of 2031, there will be a final opportunity by 31 July 2026 to renew existing agreements.
Planning ahead
Many customers are already using this period to refresh device designs, align future hardware roadmaps, and evaluate modern Azure IoT services for connectivity, identity, and device management. Microsoft and our partners are available to support you as you assess options and plan forward.
Recommended action
- Plan for hardware redesign to replace MT3620 silicon in future product iterations.
- Consider PSA/SESIP Level 3+, or similar, certified silicon as a guideline for silicon with similar security properties.
- Express any required purchasing intent and OEM license renewals via Avnet by 31 July 2026, if additional production is needed.
- Evaluate alternative IoT solutions, including:
- Azure IoT Hub with Azure Device Registry (ADR) and X.509 Certificate Management for Device Identity and Fleet Management.
- Azure IoT Hub for Device Connectivity and Data Ingestion.
- Device Update for Azure IoT Hub for Firmware Updates.
- Microcontrollers with a PSA Certified Attestation API, or similar, for integration into your chosen Attestation solution.
- FIPS 140-3 compliant crypto libraries for trustworthy At-rest and In-transit Data Encryption.
You can find further information about alternative Azure IoT services at the Azure IoT Documentation and Azure IoT solutions pages.
Help and support
If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and need technical help, create a support request.
