Choose IoT provider is not an IoT provider in that it does not have it’s own hub. This might be confusing if you’ve selected as your option of IoT hub. But the fact is, if you have signed up for our free offer, you are using our Azure IoT hub. is about Device Management, and provide services such as patching, updating, deployment, remote debugging, tracking etc. However, once everything is deployed, -Messages are transmitted to and from YOUR hub without any interference from currently supports 4 different IoT hubs:

The last option is only valid for trial, and should not be considered for production environments.

Connecting the Hub

Your choice of provider will require different input when setting up your Organization. If you for instance prefer Microsoft Azure IoT you’ll be prompted to provide a Connection string. The connection string is used for accessing your Azure IoT Hub to manage your devices and nodes. You can find the connection string in the Azure portal by selecting your IoT Hub -> Settings -> Shared access policies.

If you have an AWS IoT Hub, you’ll be asked to provide AccessKeyId, SecretAccessKey and Region. You can find these settings by navigating to the AWS portal and click on your account -> My Security Credentials and expand the Access Keys (Access Key ID and Secret Access Key).

Authentication and Security

When you create a node in, that node will be created as a Device (Azure IoT) or Thing (AWS IoT) in your IoT Hub. This is accomplished through integration between and the provider of your choice, using with the AccessKey or Shared Secret you provided in previous step.

When Nodes logs in for the first time, keys and certificates are generated by and sent to the Node using an encrypted channel.

The AccessKey or Connection string provided when connected your organization is stored encrypted in the Azure Key Vault.  Private keys and Certificates generated for Nodes are NEVER STORED OR SAVED IN MICROSERVICEBUS.COM OR RELATED SERVICES.