What is Azure IoT Central?

IoT Central is an IoT application platform that reduces the burden and cost of developing, managing, and maintaining enterprise-grade IoT solutions. Choosing to build with IoT Central gives you the opportunity to focus time, money, and energy on transforming your business with IoT data, rather than just maintaining and updating a complex and continually evolving IoT infrastructure.

The web UI lets you monitor device conditions, create rules, and manage millions of devices and their data throughout their life cycle. Furthermore, it enables you to act on device insights by extending IoT intelligence into line-of-business applications.

This article outlines, for IoT Central:

  • The typical personas associated with a project.
  • How to create your application.
  • How to connect your devices to your application
  • How to manage your application.
  • Azure IoT Edge capabilities in IoT Central.
  • How to connect your Azure IoT Edge runtime powered devices to your application.


The IoT Central documentation refers to four personas who interact with an IoT Central application:

Create your IoT Central application

As a solution builder, you use IoT Central to create a custom, cloud-hosted IoT solution for your organization. A custom IoT solution typically consists of:

  • A cloud-based application that receives telemetry from your devices and enables you to manage those devices.
  • Multiple devices running custom code connected to your cloud-based application.

You can quickly deploy a new IoT Central application and then customize it to your specific requirements in your browser. You can start with a generic application template or with one of the industry-focused application templates for Retail, Energy, Government, or Healthcare.

As a solution builder, you use the web-based tools to create a device template for the devices that connect to your application. A device template is the blueprint that defines the characteristics and behavior of a type of device such as the:

  • Telemetry it sends.
  • Business properties that an operator can modify.
  • Device properties that are set by a device and are read-only in the application.
  • Properties, that an operator sets, that determine the behavior of the device.

This device template includes:

  • A device capability model that describes the capabilities a device should implement such as the telemetry it sends and the properties it reports.
  • Cloud properties that aren't stored on the device.
  • Customizations, dashboards, and forms that are part of your IoT Central application.

Create device templates

As a solution builder, you have several options for creating device templates:

  • Design the device template in IoT Central and then implement its device capability model in your device code.
  • Create a device capability model using Visual Studio code and publish the model to a repository. Implement your device code from the model, and connect your device to your IoT Central application. IoT Central finds the device capability model from the repository and creates a simple device template for you.
  • Create a device capability model using Visual Studio code. Implement your device code from the model. Manually import the device capability model into your IoT Central application and then add any cloud properties, customizations, and dashboards your IoT Central application needs.

As a solution builder, you can use IoT Central to generate code for test devices to validate your device templates.

If you're a device developer, see IoT Central device development overview for an introduction to implementing devices that use these device templates.

Customize the UI

As a solution builder, you can also customize the IoT Central application UI for the operators who are responsible for the day-to-day use of the application. Customizations that a solution builder can make include:

  • Defining the layout of properties and settings on a device template.
  • Configuring custom dashboards to help operators discover insights and resolve issues faster.
  • Configuring custom analytics to explore time series data from your connected devices.

Manage your devices

As an operator, you use the IoT Central application to manage the devices in your IoT Central solution. Operators do tasks such as:

  • Monitoring the devices connected to the application.
  • Troubleshooting and remediating issues with devices.
  • Provisioning new devices.

As a solution builder, you can define custom rules and actions that operate over data streaming from connected devices. An operator can enable or disable these rules at the device level to control and automate tasks within the application.

With any IoT solution designed to operate at scale, a structured approach to device management is important. It's not enough just to connect your devices to the cloud, you need to keep your devices connected and healthy. An operator can use the following IoT Central capabilities to manage your devices throughout the application life cycle:


Built-in dashboards provide a customizable UI to monitor device health and telemetry. Start with a pre-built dashboard in an application template or create your own dashboards tailored to the needs of your operators. You can share dashboards with all users in your application, or keep them private.

Rules and actions

Build custom rules based on device state and telemetry to identify devices in need of attention. Configure actions to notify the right people and ensure corrective measures are taken in a timely fashion.


Jobs let you apply single or bulk updates to devices by setting properties or calling commands.

Integrate with other services

As an application platform, IoT Central lets you transform your IoT data into the business insights that drive actionable outcomes. Rules, data export, and the public REST API are examples of how you can integrate IoT Central with line-of-business applications:

How IoT Central can transform your IoT data

You can generate business insights, such as determining machine efficiency trends or predicting future energy usage on a factory floor, by building custom analytics pipelines to process telemetry from your devices and store the results. Configure data exports in your IoT Central application to export telemetry, device property changes, and device template changes to other services where you can analyze, store, and visualize the data with your preferred tools.

Build custom IoT solutions and integrations with the REST APIs

Build IoT solutions such as:

  • Mobile companion apps that can remotely set up and control devices.
  • Custom integrations that enable existing line-of-business applications to interact with your IoT devices and data.
  • Device management applications for device modeling, onboarding, management, and data access.

Administer your application

IoT Central applications are fully hosted by Microsoft, which reduces the administration overhead of managing your applications. Administrators manage access to your application with user roles and permissions.


You can create IoT Central application using a 7-day free trial, or use a standard pricing plan.

  • Applications you create using the free plan are free for seven days and support up to five devices. You can convert them to use a standard pricing plan at any time before they expire.
  • Applications you create using the standard plan are billed on a per device basis, you can choose either Standard 1 or Standard 2 pricing plan with the first two devices being free. Learn more about IoT Central pricing.


Each Azure subscription has default quotas that could impact the scope of your IoT solution. Currently, IoT Central limits the number of applications you can deploy in a subscription to 10. If you need to increase this limit, contact Microsoft support.

Known issues

  • Continuous data export doesn't support the Avro format (incompatibility).
  • GeoJSON isn't currently supported.
  • Map tile isn't currently supported.
  • Array schema types aren't supported.
  • Only the C device SDK and the Node.js device and service SDKs are supported.
  • IoT Central is currently available in the United States, Europe, Asia Pacific, Australia, United Kingdom, and Japan locations.
  • You cannot use the Custom application (legacy) application template in the United Kingdom and Japan locations.
  • Device capability models must have all the interfaces defined inline in the same file.

Next steps

Now that you have an overview of IoT Central, here are some suggested next steps:

If you're a device developer and want to dive into some code, the suggested next step is to Create and connect a client application to your Azure IoT Central application.