Automatically deploy (layered) deployments to Azure IoT hub using Infrastructure as code (IaC). Because it makes your IoT hub deployments repeatable and more consistent.
How to create an Azure IoT hub with Bicep. But what is Bicep anyway and why should we use it. In this article, I will explain about Bicep and we will create a simple Bicep example to deploy an IoT hub.
At some point in your IoT project, you will need to create or update the modules of the IoT edge devices. When more and more devices are added, it becomes impossible to deploy the configurations by hand. In this article I explain the different possibilities for automatic deployments and I will walk you through the steps.
Azure Data Explorer is a fast and powerful Azure service for analyzing real-time data. Let’s see how to create a dashboard and make it available for users who may not be familiar with Kusto.
Unexpected Azure Storage Account transactions caused by Azure Function BlobTrigger, how to identify the problem and how to solve it.
How to save costs with azure automation account runbooks. In this showcase we added an Azure Automation Runbook to remove the Bastion Service every night. This will reduce the costs up to almost 140 euro per month.
Entity Framework is known for its capability of object based development, maintainability and for reducing development time and cost. I added Entity Framework within an Azure Function App demo project.
High quality data is necessary to create reliable business insights, but how do you evaluate this for Azure Stream Analytics? In my latest article, I will explain how this can be done by creating test cases for Stream Analytics.
When developing an IoT solution, the connected devices are not always available from the start. An ideal solution for this is to temporarily simulate a device.
Also, a simulated device is ideal for test work. Since we control the simulated device ourselves, we can explore boundary-value, for example.
In this article I will go further into what is needed and how to make a simulated device.
© 2024 Wilko van de Velde