Connect, monitor and manage billions of IoT assets
Connect, monitor and control millions of IoT assets running on a broad set of operating systems and protocols to jumpstart your Internet of Things project with the IoT Hub. Enhance security of your IoT solutions by using per-device authentication to communicate with devices with the appropriate credentials. Securely establish reliable, bi-directional communication with these assets, even if they are intermittently connected, to analyse incoming telemetry, synchronise device management workflows and send commands and notifications as needed.
Explore pricing options
Apply filters to customize pricing options to your needs.
Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft, date of purchase, and the currency exchange rate. Prices are calculated based on US dollars and converted using London closing spot rates that are captured in the two business days prior to the last business day of the previous month end. If the two business days prior to the end of the month autumn on a bank holiday in major markets, the rate setting day is generally the day immediately preceding the two business days. This rate applies to all transactions during the forthcoming month. Sign in to the Azure pricing calculator to see pricing based on your current programme/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. See frequently asked questions about Azure pricing.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment or directly through a pay-as-you-go online subscription.
Important—The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment or directly through a pay-as-you-go online subscription.
Important—The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
Basic tier
Edition Type | Price per IoT Hub unit (per month) | Total number of messages/day per IoT Hub unit | Message meter size |
---|---|---|---|
B1 | $- | 4,00,000 | 4 KB |
B2 | $- | 60,00,000 | 4 KB |
B3 | $- | 30,00,00,000 | 4 KB |
Standard tier
Edition Type | Price per IoT Hub unit (per month) | Total number of messages/day per IoT Hub unit | Message meter size |
---|---|---|---|
Free | Free | 8,000 | 0.5 KB |
S1 | $- | 4,00,000 | 4 KB |
S2 | $- | 60,00,000 | 4 KB |
S3 | $- | 30,00,00,000 | 4 KB |
For more information about the capabilities supported in the basic and standard tiers, please see how to choose the right IoT hub tier.
For guidance on pricing, please visit IoT Hub pricing guidance.
Feature | Basic | Standard / Free |
---|---|---|
Device-to-cloud telemetry | ||
Per-device identity | ||
Message Routing, Event Grid Integration | ||
HTTP, AMQP, MQTT Protocols | ||
DPS Support | ||
Monitoring and diagnostics | ||
Device StreamsPREVIEW | ||
Cloud-to-device messaging | ||
Device Management, Device Twin, Module Twin | ||
IoT Edge |
Azure IoT Hub Device Provisioning Service
The Azure IoT Hub Device Provisioning Service enables zero-touch provisioning to the right IoT Hub without requiring human intervention, allowing customers to provision millions of devices in a secure and scalable manner. It enables device lifecycle support and important capabilities, that together with IoT Hub device management, helps customers address all stages of IoT device lifecycle.
Tier | Price |
---|---|
S1 | General Availability Price: $- per 1,000 operations |
Device Update for IoT Hub
Device Update for IoT Hub is a service that enables you to deploy over-the-air updates (OTA) for your IoT devices to help keep IoT devices up to date and secure
Price per Tenant | Price per Device | |
---|---|---|
Standard | $- per month | $- per month |
We offer the capability to test the Device Update service, customers can activate up to 10 devices for free to experience all service benefits. A full list of limitations for the test SKU can be found here.
The Tenant or a Device Update instance is a logical container that contains updates and deployments associated with a specific IoT Hub. A Device Update instance maps 1:1 with an IoT Hub. You can have 1 or more Device Update instances within a given Azure subscription.
Azure Security Center for IoT
For pricing details, see the Azure Security Center pricing page under resource type "IoT Devices".
Azure pricing and purchasing options
Connect with us directly
Get a walkthrough of Azure pricing. Understand pricing for your cloud solution, learn about cost optimisation and request a custom proposal.
Talk to a sales specialistSee ways to purchase
Purchase Azure services through the Azure website, a Microsoft representative or an Azure partner.
Explore your optionsAdditional resources
Azure IoT Hub
Learn more about Azure IoT Hub features and capabilities.
Pricing calculator
Estimate your expected monthly costs for using any combination of Azure products.
SLA
Review the Service Level Agreement for Azure IoT Hub.
Documentation
Review technical tutorials, videos and more Azure IoT Hub resources.
Frequently asked questions
-
The IoT Hub Free Edition is intended to encourage proof of concept projects. It enables you to transmit up to a total of 8,000 messages per day and register up to 500 device identities. The device identity limit is only present for the Free Edition.
-
IoT Hub unit represents a single IoT Hub. Number of units depends on number of messages required for your IoT solution. For example, each unit of S1 or B1 IoT Hub can handle 400,000 messages a day.
-
Please review guidance for more information.
-
Every tier has daily message limit after which you will experience throttling. Please check throttling documentation for more details. If your need change, you can adjust the units within IoT Hub. You can also change the unit type within a tier (e.g.: from S1 to S2) or upgrade to a higher tier (e.g.: B1 to S2). If you anticipate using more than 200 units of the IoT Hub S1 S2 SKU’s and IoT Hub B1 B2 SKU’s or more than 10 units of the IoT Hub B3 or S3 please contact Microsoft Support.
-
The maximum message size for messages sent from a device to the cloud is 256 KB. These messages are metered in 4 KB blocks for the paid tiers so for instance if the device sends a 16 KB message via the paid tiers it will be billed as 4 messages. The messages sent by devices connected via the free edition are metered in 0.5 KB blocks. For instance, if the device sends a 16 KB message via the IoT Hub free tier it will be billed as 32 messages.
The maximum message size for message sent from the cloud to a device is 64 KB and is metered in 4-KB blocks for the paid tiers so, for instance, an 8-KB message sent via paid tiers would be billed as two messages. The messages sent using the free edition are metered in 0.5-KB blocks. For instance, an 8-KB message sent via the IoT Hub free tier will be billed as 16 messages.
-
Only the messages which initiate a new upload and provide notification of a completed upload count against the daily allotment of messages. Customers must provide their own storage account and pay for storage. There is no separate charge for file upload. For example, in a typical file upload scenario, there are only two messages—the message that indicates that a file upload has been initiated and the message that indicates that a file upload has been completed. Customers can choose to send additional data in the status description during notifications of a failed upload. Refer to the IoT Hub documentation for additional details about the file upload feature.
-
The file upload functionality of IoT Hub follows the upload limits that Azure Storage has in place.
-
Device twins contain device state information (metadata, configurations and conditions) and are stored as JSON documents. Twins can be modified by your cloud and device applications and support a rich query language. Device twins are the fundamental primitive of IoT Hub Device Management and can be accessed through several operations such as read, write and queries. In addition, a device twin is shared between different device management components, basically with no isolation between components. With the introduction of module identity and module twin, an IoT developer can work separately without having others access his or her twin content. Each component on the device can work in isolation.
-
Twin reads, writes and queries are available only on standard tier and are metered in 4-KB chunks regardless of the size of the returned twin, the size of update and the size of query result, respectively. For instance, reading a 8-KB twin is billed as two messages, updating a twin with a 12-KB payload is billed as three messages, querying twins for a 16-KB result is billed as four messages. Twin reads, writes and queries for the free tier is metered at 0.5 KB.
-
Direct methods is available only on standard tier and are request-response communications initiated by the cloud. The cloud receives an immediate response from the device. Both requests and responses can be at most 8 KB and are metered in 4-KB blocks for the paid tiers (i.e. S1, S2, and S3) so, for instance, an 8 KB request sent via the S1, S2, or S3 tiers would be billed as two messages. The requests sent using the free tier are metered in 0.5-KB blocks. For instance, an 8-KB message sent via the IoT Hub free tier will be billed as 16 messages.
-
Jobs allow to start or schedule the execution of twin writes and direct methods on large sets of devices. Jobs operations are not billed, but the resulting twin writes and method invocations are billed as explained above
-
The consumption of IoT Hub units is measured on a daily basis and the billing is generated on a monthly basis. Customers are billed based on the number of IoT Hub units that have been consumed during the month.
-
You can choose to increase the number of IoT Hub units purchased at any time. If you sign up for the service mid-month, your monthly bill will be pro-rated based on the number of days remaining in the month. (For the purpose of the IoT Hub service, a month is defined as 31 days). If you increase the number of units of IoT Hub mid-month, your monthly bill will be based on the number of units available for each day during the month.
-
Yes, you can reduce the number of units from the Settings page at any point. The changes will take effect by the following day and be reflected on your bill at the end of the month.
-
No, you cannot switch from Free to one of the paid editions. The free edition is meant to test out proof-of-concept solutions only.
-
The IoT Hub subscription can be cancelled from the Azure Management Portal.
-
Device management features are included as part of IoT Hub. Device management messages are measured like any other telemetry message in IoT Hub.
-
IoT Hub Device Provisioning Service is billed by the number of operations. Operations include device registrations and re-registrations; operations also include service-side changes such as adding enrollment list entries, updating enrollment list entries and get/query operations. Every six months of inactivity on a given enrollment entry will incur a "keep-alive" operation.
-
Yes, you have to take the action of explicitly switching from one paid edition to another. The device identity and all messages are carried over to the new edition. If a customer wants to move from a higher tier to a lower tier, for instance from S2 to S1 and they have consumed more messages than S1 allows per day, then for that day the customer is billed at S2 and the customer is billed at the S1 rate starting the next day.
-
Yes, you have to take the action of explicitly switching from one paid edition to another. The device identity and all messages are carried over to the new edition. If a customer wants to move from a higher tier to a lower tier, for instance from B2 to B1, and they have consumed more messages than B1 allows per day, then for that day the customer is billed at B2, and the customer is billed at the B1 rate starting the next day.
-
Yes, you can upgrade from basic to standard tier via Azure Portal, but you cannot downgrade from standard to basic tier. To move from standard to basic you will have to create a new basic tier IoT Hub and need to re-register your devices to that IoT hub.
Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.
Get free cloud services and a $200 credit to explore Azure for 30 days.