Azure IoT Hub Config Builder

ServerlessAzure

Build IoT Hub route and endpoint configs with message routing, custom endpoints, enrichments, and file upload settings.

Azure IoT Hub Configuration

Build IoT Hub route and endpoint configs with message routing, custom endpoints (Event Hub, Service Bus, Storage), enrichments, and file upload.

Required Fields

iotHubNameresourceGroupsku.nameroutesroutes[0].nameroutes[0].sourceroutes[0].endpointName

{
  "iotHubName": "iot-contoso-prod",
  "resourceGroup": "rg-iot",
  "location": "eastus2",
  "sku": {
    "name": "S2",
    "capacity": 2
  },
  "properties": {
    "eventHubEndpoints": {
      "events": {
        "retentionTimeInDays": 7,
        "partitionCount": 4
      }
    },
    "cloudToDevice": {
      "maxDeliveryCount": 10,
      "defaultTtlAsIso8601": "PT1H",
      "feedback": {
        "lockDurationAsIso8601": "PT60S",
        "ttlAsIso8601": "PT1H",
        "maxDeliveryCount": 10
      }
    },
    "messagingEndpoints": {
      "fileNotifications": {
        "lockDurationAsIso8601": "PT1M",
        "ttlAsIso8601": "PT1H",
        "maxDeliveryCount": 10
      }
    }
  },
  "routes": [
    {
      "name": "telemetry-to-eventhub",
      "source": "DeviceMessages",
      "condition": "$body.messageType = 'telemetry'",
      "endpointName": "eh-telemetry",
      "isEnabled": true
    },
    {
      "name": "alerts-to-servicebus",
      "source": "DeviceMessages",
      "condition": "$body.severity = 'critical' OR $body.severity = 'warning'",
      "endpointName": "sb-alerts",
      "isEnabled": true
    },
    {
      "name": "lifecycle-events",
      "source": "DeviceLifecycleEvents",
      "condition": "true",
      "endpointName": "eh-lifecycle",
      "isEnabled": true
    },
    {
      "name": "twin-changes-to-storage",
      "source": "TwinChangeEvents",
      "condition": "true",
      "endpointName": "storage-twin-changes",
      "isEnabled": true
    }
  ],
  "customEndpoints": [
    {
      "name": "eh-telemetry",
      "type": "EventHub",
      "connectionString": "Endpoint=sb://evhns-contoso-iot.servicebus.windows.net/;SharedAccessKeyName=send;SharedAccessKey=<key>;EntityPath=telemetry",
      "resourceGroup": "rg-iot"
    },
    {
      "name": "sb-alerts",
      "type": "ServiceBusQueue",
      "connectionString": "Endpoint=sb://sbns-contoso-iot.servicebus.windows.net/;SharedAccessKeyName=send;SharedAccessKey=<key>;EntityPath=iot-alerts"
    },
    {
      "name": "storage-twin-changes",
      "type": "StorageContainer",
      "connectionString": "DefaultEndpointsProtocol=https;AccountName=stcontosoiot;...",
      "containerName": "twin-changes",
      "encoding": "JSON",
      "fileNameFormat": "{iothub}/{partition}/{YYYY}/{MM}/{DD}/{HH}/{mm}",
      "batchFrequencyInSeconds": 300,
      "maxChunkSizeInBytes": 314572800
    }
  ],
  "enrichments": [
    {
      "key": "tenantId",
      "value": "$twin.tags.tenantId",
      "endpointNames": ["eh-telemetry", "sb-alerts"]
    },
    {
      "key": "deviceLocation",
      "value": "$twin.tags.location",
      "endpointNames": ["eh-telemetry"]
    }
  ],
  "fileUpload": {
    "storageAccountName": "stcontosoiotfiles",
    "containerName": "device-uploads",
    "sasTtlAsIso8601": "PT1H",
    "notifications": true
  },
  "tags": {
    "environment": "production",
    "platform": "iot"
  }
}

Generated Output

Output will appear here...

How It Helps

Build IoT Hub route and endpoint configs with message routing, custom endpoints, enrichments, and file upload settings. This tool helps Azure engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.

Things Engineers Ask

Does this IoT Hub config builder consider the RBAC role needed to apply the configuration?

No — generating a IoT Hub configuration is independent of the role required to apply it. Apply the output with a principal that has the documented permissions for that service. For least-privilege scoping, Azure's built-in roles and the Privileged Identity Management 'just enough access' workflows give you a starting point.

Can I use this IoT Hub config builder for Azure Government or sovereign clouds?

Most IoT Hub primitives behave the same across commercial, Government, and other sovereign Azure clouds, but the endpoints, available regions, and a handful of services differ. The output is portable in terms of resource shape; you must verify service availability and adjust endpoints when targeting a sovereign cloud.

Practical Applications

1Designing a IoT Hub configuration for a new Azure workload where the team wants the spec reviewed before any portal click happens.
2Drafting a IoT Hub change for an Azure Bicep or Terraform module before raising the pull request, so reviewers can see intent in plain text.
3Comparing two candidate IoT Hub layouts side by side to pick the one with the cleaner permission boundary.
4Working out a IoT Hub configuration during incident response, when the on-call needs a corrected version applied within minutes.

Related Learning Guides

Functions Hosting Plans22 min read
Service Bus vs Event Grid vs Event Hubs24 min read

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.