Don’t let the complexity of pricing an IoT solution get in the way. Experience the flexibility and simplicity of multiple pricing plans to choose from to meet your evolving needs.
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.
Azure Germany is available to customers and partners who have already purchased this, doing business in the European Union (EU), the European Free Trade Association (EFTA), and in the United Kingdom (UK). It provides data residency in Germany with additional levels of control and data protection. You can also sign up for a free Azure trial.
New customers can explore the benefits of IoT Central with a free 7-day trial.
|Pricing Tier||Standard Tier 1||Standard Tier 2|
|Use Case||For devices sending a few messages per hour||For devices sending a message every few minutes|
|Price per device||$- per Month||$- per Month|
|Monthly device message allocation*||5,000 messages||30,000 messages|
|Included free quantities per IoT Central application||2 free devices (10,000 included messages)||2 free devices (60,000 included messages)|
|Overage pricing beyond the monthly message allocation1||$- per 1K messages||$- per 1K messages|
The first 2 active devices within an IoT Central application are not charged, as long as their message volume does not exceed 10,000 (Standard Tier 1 plan) or 60,000 (Standard Tier 2 plan) per month. Message volumes greater than those thresholds will incur overage charges. Beyond that the device pricing is prorated on a monthly basis. For each hour during the billing period the highest number of active devices are counted and billed.
If a customer uses Azure IoT Central and enrolls in the Standard Tier 1 plan, connecting 100 devices, each sending 6,000 messages, the customer will be billed as listed below.
$- for the first 2 devices
The next 98 devices are billed (100 devices - 2 free devices) * ($- per device/month) = $-
Each device also incurs monthly overage charges billed at $- per message sent in excess of the earned monthly allocation.
In this example, 1,000 messages were sent by each device beyond the allocation (100 devices * 1,000 messages) * $- per message = $-
Total cost for the month is the sum of per device and overage charges
$- + $- = $-
A device that is registered and has completed the initial connection to Azure IoT Central is an active device and is counted for the purposes of billing. If a device has been registered but has not completed an initial connection it is not counted for the purposes of billing. If a device is no longer in use, it must be explicitly removed to prevent it from being counted for billing.
It depends on whether how you have provisioned your gateway and downstream devices in Azure IoT Central.
If both gateway device and downstream device(s) are provisioned in Azure IoT Central, per device pricing, message limits and overages apply individually for the gateway device and downstream device(s).
If you choose to only provision a gateway device in IoT Central, both gateway messages and downstream device(s) messages are represented aggregated as gateway device messages. Message limits and overages apply.
Any communication back and forward between the device and the cloud counts as a message - including telemetry, cloud-to-device, and device-to-cloud (including twin read and update) communication. Exploration of historical device data will not incur additional charges.
When a customer exceeds the shared monthly message allocation, they are charged $- per message. This equates to $- per 1 million messages.
Message allocation is earned hourly based on the SKU selected and the number of devices.
Messages Allocation Example
If a customer enrolls an Azure IoT Central application in the Standard Tier 1 plan, every hour 7 messages (5,000 messages / 730 hours per month) are earned for use during the billing period. A billing period in this example is one month.
Earned messages can be used by any device in the application.
Earned messages can be used during any hour in the billing after being earned.
Earned messages must be used in the current billing period and do not carry over to subsequent billing periods.
We will prorate the cost based on when you add the device. For example, you will be billed $- for a device that exists for the entire month and $- for a device that is added halfway through the month.
Users can create an Azure IoT Central trial without an Azure Subscription. A user can have only one active trial at a time. The trial allows users to add up to 5 devices (real or simulated) and lasts for 7 days after activation. During this trial period, customers can explore many of the features of Azure IoT Central. Some external data integrations require an Azure subscription and some threshold limitations may apply. Users will not be able to create more devices upon reaching the trial limit of 5 devices or the end of the 7-day trial period. The data of the trial application is not retained after the end of the trial period. At any time during the trial, users can attach the trial app to their Azure subscription to remove these limitations and will be billed based using the pricing described above.
Customers transitioning from a trial will have by default Standard Tier 2 pricing. To change pricing tiers, see our documentation.
Yes, you can change the pricing plan for an Azure IoT Central application at any time. For guidance on how to change plans, please see our documentation.
Message quotas are shared across the devices in your IoT Central application but are not shared across other applications or across Azure subscriptions.
Data is retained on a rolling 30-day basis and customers can continuously export their data using the export feature in IoT Central.
Customers control the user access to the application via in-product Role Based Access. Azure IoT Central users can add up to 200 users to an application.
Estimate your monthly costs for Azure services
Review Azure pricing frequently asked questions
Learn more about Azure IoT Central
Review technical tutorials, videos, and more resources