How to upgrade to Azure Device Update Agent 1.1.0 or later when using the azure-iot-freertos-middleware

Question

How to upgrade to Azure Device Update Agent 1.1.0 or later when using the azure-iot-freertos-middleware

Florian Humblot 5

According to the new docs on root key rotations, it is recommended to use the update agent v1.1

It's strongly recommended to adopt Device Update Agent version 1.1.0 or later, which will automatically obtain all future root keys for your devices as needed, including during a revocation event. If you are unable to adopt Device Update Agent version 1.1.0 or later, plan to update your devices to add the new root key once available as quickly as possible before August 26, 2025, so two valid root keys will be available on your devices after the August 26 rotation.

The current azure-iot-middleware-freertos uses update agent v1.0:

in libraries\azure-sdk-for-c\sdk\inc\azure\iot\az_iot_adu_client.h

#define AZ_IOT_ADU_CLIENT_AGENT_VERSION "DU;agent/1.0.0"

What's the upgrade path to start using the new update agent so that we are future-proofed for key rotations? I created an issue on the Github repository but that hasn't received any attention after a month.

https://github.com/Azure/azure-iot-middleware-freertos/issues/333

Manas Mohanty 5,940 Reputation points Microsoft External Staff Moderator

2025-04-02T15:20:46.2966667+00:00

Hi Florian Humblot

We have escalated this issue with the Azure RTOS Product team and get back to you with more feedback and updates.

Could you update the document link here on the "new docs on root key rotations" mentioning > > "It's strongly recommended to adopt Device Update Agent version 1.1.0 or later, which will automatically obtain all future root keys for your devices as needed, including during a revocation event....."

(it is not routing to any doc URL by clicking)

Thank you.
Florian Humblot 5 Reputation points

2025-04-02T15:31:54.6766667+00:00

@Manas Mohanty I've updated the link :)

1 answer

Your answer

Manas Mohanty 5,940 Reputation points Microsoft External Staff Moderator

2025-04-02T15:20:46.2966667+00:00

Hi Florian Humblot

We have escalated this issue with the Azure RTOS Product team and get back to you with more feedback and updates.

Could you update the document link here on the "new docs on root key rotations" mentioning > > "It's strongly recommended to adopt Device Update Agent version 1.1.0 or later, which will automatically obtain all future root keys for your devices as needed, including during a revocation event....."

(it is not routing to any doc URL by clicking)

Thank you.
Florian Humblot 5 Reputation points

2025-04-02T15:31:54.6766667+00:00

@Manas Mohanty I've updated the link :)

Answer 1

LeelaRajeshSayana-MSFT 17,766 Moderator

@Florian Humblot We have checked this issue with the product team, and they informed that have a plan for updating the ADU root keys referenced by Azure IoT Middleware for FreeRTOS and its samples. They are planning to roll out the changes probably within a month. We are not sure what the changes are going to be at this state. Keep tabs on the source code repository and check for updates after a month. We will update this thread with more information once the changes have rolled out.

If you have any further query, do let us know. Thank you

Update

The product team confirmed that the updating the ADU clients to comply with the new key rotation has not been rolled out yet. They will reprioritize this task and for the time being, the only update we had was in our documentation to point where the keys could be obtained.

Please refer to the details in step 6 of documentation - How to use ADU Client that will guide you further.

If it answers your query, please do click Accept Answer and Yes, as it might be beneficial to other community members reading this thread.

Florian Humblot 5 Reputation points

2025-06-10T08:29:55.47+00:00
@LeelaRajeshSayana-MSFT It's been more than a month now, and the Device Update Agent has received a second version bump (1.2), but the sdk-for-c and the azure-iot-middleware-freertos both have no updates to speak of.

Tickets:

https://github.com/Azure/azure-sdk-for-c/issues/3101

https://github.com/Azure/azure-iot-middleware-freertos/issues/333

with no response either.

Can you share a timeline or at least have someone react to the issues?
LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator

2025-06-24T14:38:18.9366667+00:00

@Florian Humblot The product team confirmed that the updating the ADU clients to comply with the new key rotation has not been rolled out yet. They will reprioritize this task and for the time being, the only update we had was in our documentation to point where the keys could be obtained.

Please refer to the details in step 6 of documentation - How to use ADU Client that will guide you further.

I have updated my initial response on the thread with the same findings. Please let me know if you have any additional questions on this. If the response answers your question, kindly mark it as Accepted Answer as it might help other community members

Share via

How to upgrade to Azure Device Update Agent 1.1.0 or later when using the azure-iot-freertos-middleware

1 answer

Your answer