Hey, how could I be notified whenever is possible to provision devices automatically via API or some other way that won't involve the UI nor the AZ CLI?
Hey. You could leverage Bicep to automate things like described in this article: medium.com/@alonfliess/article-three-of-five-automate-the-creation-of-the-azure-event-grid-mqtt-broker-and-clients-9d27fc240184 It's leveraging the Azure CLI, but allows you to script the creation of new clients.
@@obloch yes! Definetly that might work. The thing here is that in the project I'm working it might create thousands of devices at once from the webapi client. So... A possible solution might be to export a list of the created devices and then provision them in event grid. Do you have any better idea? Oh, and is there any timeline to have the ability to create clients via api?
@pcervello, I am sure Microsoft will have some interesting new features released and announced at the upcoming Ignite event next month that will fill in the blanks they have in their story. For example, in Azure IoT Operations, there is a preview of a Device Registry Service which doesn't (yet?) tie into the Device Provisioning Service and at the same time DPS doesn't (yet?) support provisioning devices for the EG MQTT Broker. Let's see what they come up with at Ignite
Hey, how could I be notified whenever is possible to provision devices automatically via API or some other way that won't involve the UI nor the AZ CLI?
Hey. You could leverage Bicep to automate things like described in this article: medium.com/@alonfliess/article-three-of-five-automate-the-creation-of-the-azure-event-grid-mqtt-broker-and-clients-9d27fc240184
It's leveraging the Azure CLI, but allows you to script the creation of new clients.
@@obloch yes! Definetly that might work. The thing here is that in the project I'm working it might create thousands of devices at once from the webapi client.
So... A possible solution might be to export a list of the created devices and then provision them in event grid.
Do you have any better idea?
Oh, and is there any timeline to have the ability to create clients via api?
@pcervello, I am sure Microsoft will have some interesting new features released and announced at the upcoming Ignite event next month that will fill in the blanks they have in their story. For example, in Azure IoT Operations, there is a preview of a Device Registry Service which doesn't (yet?) tie into the Device Provisioning Service and at the same time DPS doesn't (yet?) support provisioning devices for the EG MQTT Broker. Let's see what they come up with at Ignite
You mentioned "custom authentication", does this mean that we will be getting username/password support in Event Grid?
Yes. This will be supported via Functions. Like BYOF.
@@Seth-IoT Great, thanks for the news.