Does your Azure IoT (Edge Ubuntu) device survive the Baltimore certificate migration?

Microsoft is still using the Baltimore certificate for its IoT services. This certificate is used for TLS communication with the IoT Hub and other IoT-related Azure services.

This is done by choice, to give users more time to migrate their devices if they are not (yet) able to support the new DigiCert Global Root G2 certificate automatically.

This year, starting next month, Microsoft will start the migration.

Check out this timeline:

This has been postponed a number of times already. It’s now time to act!

If both your Azure edge devices and Azure IoT edge devices are running Ubuntu, here are some pointers to test your devices.

Advertentie

Azure IoT Community, unified edge event with Microsoft Nederland

Finally, after more than two years of absence due to the global pandemic, the Dutch Azure IoT Community is offering another event related to Azure IoT Topics.

This time, our location sponsor is Microsoft and the event is hosted at their HQ in The Netherlands, near Schiphol.

The Microsoft Technology Center is hosting a Hybrid Computing Event with the Azure IoT Community focusing on Edge and IoT.

We have 25 physical spots available and of course, people are welcome online after registration.

FutureTech event in 2023 (Dutch)

Op 15 maart 2023 zal wederom het FutureTech event plaatsvinden in de Jaarbeurs te Utrecht.

Net als voorgaande jaren zullen er meerdere track naast elkaar aangeboden worden rond Microsoft technologie zoals edge AI, computer vision, decision intelligence, machine learning, VR & AR en IoT.

Exploring Azure Digital Twins Graph history

Update: the historical data export functionality now also exports twin lifecycle information. This means a part of the custom logic seen below is now part of the default export.

As seen in previous posts, Azure Digital Twins shows the current state of any twin in the Azure Digital Twins graph.

This current state is a combination of multiple items:

• twin name and model
• twin properties updates based on telemetry and/or business rules related to that telemetry
• twin properties updates based on predictions towards the future
• twin properties updates based on historical data

Azure Digital Twins also offers to store historical Twin property data. That historical data is made available using Azure Data Explorer, part of the data history connection, as explained in my previous post.

There, twin data can also be compared with twin graph knowledge using the ADX Kusto plugin for querying the ADT graph.

Still, that accompanying plugin is missing something. We have no historical knowledge of the graph itself including models and how these changed over time!

If we want this information, we need to be creative.

Can we add the missing pieces?

Let’s check out how we can explore the ADT graph history…