Microsoft’s Azure Sphere May 2025 Services update introduces key features to enhance security and migration. Users can now pause or re-enable Legacy access, changes expired certificate downloads, and block devices from receiving certificates—streamlining transition to Azure Sphere Integrated before Legacy retires in 2027. Unique :

Azure Sphere May 2025 Services Release: What’s New?
Microsoft just dropped the Azure Sphere May 2025 Services update, focusing on improving security and easing migration. Unlike typical releases, this update doesn’t include OS or SDK changes. Instead, it targets the Azure Sphere Services layer with three key improvements.
Pause and Resume Legacy Access for Smooth Migration
One of the biggest highlights is the ability to pause or re-enable Azure Sphere (Legacy) tenant operations directly from the Azure portal. This feature is a game-changer for organizations transitioning to Azure Sphere (Integrated), especially since Legacy support retires on September 27, 2027.
By pausing Legacy access, users can confidently verify that no legacy use cases remain. If needed, they can temporarily re-enable Legacy to handle any last-minute migrations. Microsoft recommends pausing Legacy once it’s no longer needed to boost security.
“Once you know that Legacy is no longer needed, we recommend you should pause Legacy to avoid any operations via that interface.”
Expired Certificate Downloads Are No Longer Allowed
Another important update changes how expired tenant and catalog certificates are handled. Users can no longer download expired certificates from Azure Sphere services. However, metadata remains visible in certificate lists.
This change won’t affect production environments because expired certificates are already out of use. Requests for expired certificates now return a “null” or “not found” response across the Legacy CLI, Integrated CLI, and Azure portal.
Block Devices from Receiving Azure Sphere Certificates
Security-conscious users will appreciate the new ability to block devices from obtaining Azure Sphere-issued device certificates. This is especially useful if a device is lost, stolen, or decommissioned.
Blocking a device prevents it from being trusted by services like Azure IoT Hub, which rely on Azure Sphere certificates for authentication. To activate this feature, customers must contact Microsoft support via [email protected].
“Customers may now block devices from receiving device certificates from Azure Sphere via a support request.”
Why This Release Matters
This update is all about tightening security and simplifying the migration path from Legacy Azure Sphere to the Integrated platform. By pausing Legacy access, blocking compromised devices, and tightening certificate handling, Microsoft helps organizations future-proof their IoT deployments.
For tech teams managing Azure Sphere environments, these changes offer better control and peace of mind ahead of the Legacy retirement deadline.
From the New blog articles in Microsoft Community Hub