Concerning the parameters: Specifying the Event Hub compatible connection is required. Configuring the service connection string is optional. It is necessary for the following hooks:
In effect, everything that not only consumes information but accesses the devices in some way.
You can retrieve the service connection string for the IoT Hub with:
1
IOT_HUB_CONNECTION_STRING=$(az iot hub connection-string show \
2
--resource-group RESOURCE_GROUP_OF_IOT_HUB \
3
--subscription SUBSCRIPTION \
4
--hub-name NAME_OF_IOT_HUB \
5
--policy-name service
6
--query connectionString \
7
-o tsv)
Copied!
You can retrieve the Event Hub compatible endpoint connection string with:
1
IOT_HUB_EVENT_HUB_CONNECTION_STRING=$(az iot hub connection-string show \
2
--resource-group RESOURCE_GROUP_OF_IOT_HUB \
3
--subscription SUBSCRIPTION \
4
--hub-name NAME_OF_IOT_HUB \
5
--query connectionString \
6
--default-eventhub \
7
--policy-name service \
8
-o tsv)
Copied!
Replace RESOURCE_GROUP_OF_IOT_HUB with the resource group that your IoT Hub resides in. ReplaceNAME_OF_IOT_HUB with the name of the IoT Hub. Replace SUBSCRIPTION with your Azure Subscription.
Creating via Bicep (Azure Resource Manager)
Here is an example Bicep template that you can use to deploy a ux4iot instance.