Does this tool connect to my Azure account?

No. This tool runs entirely in your browser and generates configuration JSON that you can copy and paste into your infrastructure-as-code templates, CLI commands, or cloud console. It never connects to any cloud account or sends data externally.

Are the generated configurations production-ready?

The tool produces syntactically valid configurations based on current Azure service specifications. Always review generated configs against your organization security policies and test in a non-production environment before deploying.

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...

About This Tool

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.

When to Use This Tool

•Generating azure iot hub configurations for new infrastructure deployments.
•Validating existing configurations against best practices before applying changes.
•Learning Azure service configuration patterns through interactive examples.
•Accelerating infrastructure-as-code development by producing correct JSON/YAML starting points.

Frequently Asked Questions

Does this tool connect to my Azure account?: No. This tool runs entirely in your browser and generates configuration JSON that you can copy and paste into your infrastructure-as-code templates, CLI commands, or cloud console. It never connects to any cloud account or sends data externally.
Are the generated configurations production-ready?: The tool produces syntactically valid configurations based on current Azure service specifications. Always review generated configs against your organization security policies and test in a non-production environment before deploying.

Related Learning Guides

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

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.