Skip to content

Commit 470e757

Browse files
committed
iot-central content
1 parent 4c75c10 commit 470e757

File tree

213 files changed

+4130
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

213 files changed

+4130
-0
lines changed

articles/iot-central/TOC.yml

+109
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,109 @@
1+
- name: Azure IoT Fundamentals
2+
href: /azure/iot-fundamentals
3+
- name: Azure IoT Central Documentation
4+
href: index.yml
5+
- name: Overview
6+
items:
7+
- name: What is Azure IoT Central
8+
href: overview-iot-central.md
9+
- name: IoT Solution options
10+
href: overview-iot-options.md
11+
- name: Tour of the UI
12+
href: overview-iot-central-tour.md
13+
- name: Quickstarts
14+
expanded: true
15+
items:
16+
- name: Create a new application
17+
href: quick-deploy-iot-central.md
18+
- name: Tutorials
19+
items:
20+
- name: Builder
21+
items:
22+
- name: 1 - Define a new device type
23+
href: tutorial-define-device-type.md
24+
- name: 2 - Configure rules
25+
href: tutorial-configure-rules.md
26+
- name: 3 - Customize the operator's view
27+
href: tutorial-customize-operator.md
28+
- name: Operator
29+
items:
30+
- name: 4 - Monitor your devices
31+
href: tutorial-monitor-devices.md
32+
- name: 5 - Add a device
33+
href: tutorial-add-device.md
34+
- name: Concepts
35+
items:
36+
- name: Architecture
37+
href: concepts-architecture.md
38+
- name: Connectivity
39+
href: concepts-connectivity.md
40+
- name: How-to guides
41+
items:
42+
- name : Adminstrator
43+
items:
44+
- name: Create an application
45+
href: howto-create-application.md
46+
- name: Administer your application
47+
href: howto-administer.md
48+
- name : Builder
49+
items:
50+
- name: Set up the device template
51+
href: howto-set-up-template.md
52+
- name: Version device template
53+
href: howto-version-devicetemplate.md
54+
- name: Create telemetry rule
55+
href: howto-create-telemetry-rules.md
56+
- name: Create an event rule
57+
href: howto-create-event-rules.md
58+
- name: Prepare and upload images
59+
href: howto-prepare-images.md
60+
- name : Operator
61+
items:
62+
- name: Manage your devices
63+
href: howto-manage-devices.md
64+
- name: Use device sets
65+
href: howto-use-device-sets.md
66+
- name: Create custom analytics
67+
href: howto-create-analytics.md
68+
- name : Device developer
69+
items:
70+
- name: Prepare and connect a Node.js (generic) application
71+
href: howto-connect-nodejs.md
72+
- name: Prepare and connect an MXChip IoT DevKit
73+
href: howto-connect-devkit.md
74+
- name: Prepare and connect a Raspberry Pi (Python)
75+
href: howto-connect-raspberry-pi-python.md
76+
- name: Prepare and connect a Raspberry Pi (C#)
77+
href: howto-connect-raspberry-pi-csharp.md
78+
- name: Prepare and connect a Windows IoT Core device
79+
href: howto-connect-windowsiotcore.md
80+
- name: Related
81+
items:
82+
- name: Solutions
83+
items:
84+
- name: IoT Suite Preconfigured Solutions
85+
href: /azure/iot-suite
86+
- name: IoT Central
87+
href: /microsoft-iot-central
88+
- name: Platform services
89+
items:
90+
- name: IoT Hub
91+
href: /azure/iot-hub
92+
- name: IoT Hub Device Provisioning Service
93+
href: /azure/iot-dps
94+
- name: Location Based Services
95+
href: /azure/location-based-services
96+
- name: Service SDKs
97+
href: /azure/iot-hub/iot-hub-devguide-sdks#azure-iot-service-sdks
98+
- name: Time Series Insights
99+
href: /azure/time-series-insights
100+
- name: Edge
101+
items:
102+
- name: IoT Edge
103+
href: /azure/iot-edge
104+
- name: IoT Device SDKs
105+
href: /azure/iot-hub/iot-hub-devguide-sdks#azure-iot-device-sdks
106+
- name: Resources
107+
items:
108+
- name: Stack Overflow
109+
href: https://stackoverflow.com/questions/tagged/azure-iot-central
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
1+
---
2+
# Mandatory fields. See more on aka.ms/skyeye/meta.
3+
title: Architectural concepts in Azure IoT Central | Microsoft Docs
4+
description: This article introduces key concepts relating the architecture of Azure IoT Central
5+
services: iot-central
6+
author: dominicbetts
7+
ms.author: dobett
8+
ms.date: 11/30/2017
9+
ms.topic: conceptual
10+
# Use only one of the following. Use ms.service for services, ms.prod for on-prem. Remove the # before the relevant field.
11+
ms.prod: microsoft-iot-central
12+
# product-name-from-white-list
13+
14+
# Optional fields. Don't forget to remove # if you need a field.
15+
# ms.custom: can-be-multiple-comma-separated
16+
# ms.devlang:devlang-from-white-list
17+
# ms.suite:
18+
# ms.tgt_pltfrm:
19+
# ms.reviewer:
20+
manager: timlt
21+
---
22+
23+
# Azure IoT Central architecture
24+
25+
This article provides an overview of the Microsoft Azure IoT Central architecture.
26+
27+
![Top-level architecture](media/concepts-architecture/architecture.png)
28+
29+
## Devices
30+
31+
Devices exchange data with your Azure IoT Central application. A device can:
32+
33+
- Send measurements such as telemetry.
34+
- Synchronize settings with your application.
35+
36+
In Azure IoT Central, the data that a device can exchange with your application is specified in a device template. For more information about device templates, see [Metadata management](#metadata-management).
37+
38+
To learn more about how devices connect to your Azure IoT Central application, see [Device connectivity](concepts-connectivity.md).
39+
40+
## Cloud gateway
41+
42+
Azure IoT Central uses Azure IoT Hub as a cloud gateway that enables device connectivity. IoT Hub enables:
43+
44+
- Data ingestion at scale in the cloud.
45+
- Device management.
46+
- Secure device connectivity.
47+
48+
To learn more about IoT Hub, see [Azure IoT Hub](https://docs.microsoft.com/azure/iot-hub/).
49+
50+
To learn more about device connectivity in Azure IoT Central, see [Device connectivity](concepts-connectivity.md).
51+
52+
## Data stores
53+
54+
Azure IoT Central stores application data in the cloud. Application data stored includes:
55+
56+
- Device templates.
57+
- Device identities.
58+
- Device metadata.
59+
- User and role data.
60+
61+
Azure IoT Central uses a time series store for the measurement data sent from your devices. Time series data from devices used by the analytics service.
62+
63+
## Analytics
64+
65+
The analytics service is responsible for generating the custom reporting data that the application displays. An operator can [customize the analytics](howto-create-analytics.md) displayed in the application. The analytics service is built on top of [Azure Time Series Insights](https://azure.microsoft.com/services/time-series-insights/) and processes the measurement data sent from your devices.
66+
67+
## Rules and actions
68+
69+
[Rules and actions](howto-create-telemetry-rules.md) work closely together to automate tasks within the application. A builder can define rules based on device telemetry such as the temperature exceeding a defined threshold. Azure IoT Central uses a stream processor to determine when the rule conditions are met. When a rule condition is met, it triggers an action defined by the builder. For example, an action can send an email to notify an engineer that the temperature in a device is too high.
70+
71+
## Metadata management
72+
73+
In an Azure IoT Central application, device templates define the behavior and capability of types of device. For example, a refrigerator device template specifies the telemetry a refrigerator sends to your application.
74+
75+
![Template architecture](media/concepts-architecture/template_architecture.png)
76+
77+
In a device template:
78+
79+
- **Measurements** specify the telemetry the device sends to the application.
80+
- **Settings** specify the configurations that an operator can set.
81+
- **Properties** specify metadata that an operator can set.
82+
- **Rules** automate behavior in the application based on data sent from a device.
83+
- **Dashboards** are customizable views of a device in the application.
84+
85+
An application can have one or more simulated and real devices based on each device template.
86+
87+
## RBAC
88+
89+
An [administrator can define access rules](howto-administer.md) for an Azure IoT Central application using the predefined roles. An administrator can assign users to roles that determine what areas of the application the user has access to.
90+
91+
## Security
92+
93+
Security features within Azure IoT Central include:
94+
95+
- Data is encrypted in transit and at rest.
96+
- Authentication is provided either by Azure Active Directory or Microsoft Account. Two-factor authentication is supported.
97+
- Full tenant isolation.
98+
- Device level security.
99+
100+
## UI shell
101+
102+
The UI shell is a modern, responsive, HTML5 browser-based application.
103+
104+
## Next steps
105+
106+
Now that you have learned about the architecture of Azure IoT Central, the suggested next step is to learn about [device connectivity](concepts-connectivity.md) in Azure IoT Central.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
---
2+
# Mandatory fields. See more on aka.ms/skyeye/meta.
3+
title: Device connectivity in Azure IoT Central | Microsoft Docs
4+
description: This article introduces key concepts relating to device connectivity in Azure IoT Central
5+
services: iot-central
6+
author: dominicbetts
7+
ms.author: dobett
8+
ms.date: 11/30/2017
9+
ms.topic: conceptual
10+
# Use only one of the following. Use ms.service for services, ms.prod for on-prem. Remove the # before the relevant field.
11+
ms.prod: microsoft-iot-central
12+
# product-name-from-white-list
13+
14+
# Optional fields. Don't forget to remove # if you need a field.
15+
# ms.custom: can-be-multiple-comma-separated
16+
# ms.devlang:devlang-from-white-list
17+
# ms.suite:
18+
# ms.tgt_pltfrm:
19+
# ms.reviewer:
20+
manager: timlt
21+
---
22+
23+
# Device connectivity in Azure IoT Central
24+
25+
This article introduces key concepts relating to device connectivity in Microsoft Azure IoT Central.
26+
27+
Every device that connects to your Azure IoT Central application, connects to the [endpoints](https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-endpoints) that are exposed by the IoT hub Azure IoT Central uses. IoT Hub enables scalable, secure, and reliable connections from your connected devices.
28+
29+
## SDK support
30+
31+
The Azure Device SDKs offer the easiest way for you implement the code on your devices that connects to your Azure IoT Central application. The following device SDKs are available:
32+
33+
- [Azure IoT SDK for C](https://github.com/azure/azure-iot-sdk-c)
34+
- [Azure IoT SDK for Python](https://github.com/azure/azure-iot-sdk-python)
35+
- [Azure IoT SDK for Node.js](https://github.com/azure/azure-iot-sdk-node)
36+
- [Azure IoT SDK for Java](https://github.com/azure/azure-iot-sdk-java)
37+
- [Azure IoT SDK for .NET](https://github.com/azure/azure-iot-sdk-csharp)
38+
39+
Each device connects using a unique connection string that identifies the device. A device can only connect to the IoT hub where it is registered. When you create a real device in your Azure IoT Central application, the application generates a connection string for you to use.
40+
41+
## SDK features and IoT Hub connectivity
42+
43+
All device communication with IoT Hub uses the following IoT Hub connectivity options:
44+
45+
- [Device-to-cloud messaging](https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-messages-d2c)
46+
- [Device twins](https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-device-twins)
47+
48+
The following table summarizes how Azure IoT Central device features map on to IoT Hub features:
49+
50+
| Azure IoT Central | Azure IoT Hub |
51+
| ----------- | ------- |
52+
| Measurement: Telemetry | Device-to-cloud messaging |
53+
| Device properties | Device twin reported properties |
54+
| Settings | Device twin desired and reported properties |
55+
56+
To learn more about using the Device SDKs, see one of the following articles for example code:
57+
58+
- [Connect a generic Node.js client to your Azure IoT Central application](howto-connect-nodejs.md)
59+
- [Connect a Raspberry Pi device to your Azure IoT Central application](howto-connect-raspberry-pi-python.md)
60+
- [Connect a DevDiv kit device to your Azure IoT Central application](howto-connect-devkit.md).
61+
62+
The following video presents an overview of how to connect a real device to Azure IoT Central:
63+
64+
>[!VIDEO https://channel9.msdn.com/Shows/Internet-of-Things-Show/Connect-real-devices-to-Microsoft-IoT-Central/Player]
65+
66+
## Protocols
67+
68+
The Device SDKs support the following network protocols for connecting to an IoT hub:
69+
70+
- MQTT
71+
- AMQP
72+
- HTTPS
73+
74+
For information about these difference protocols and guidance on choosing one, see [Choose a communication protocol](https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-protocols).
75+
76+
If your device can't use any of the supported protocols, you can use Azure IoT Edge to do protocol conversion. IoT Edge supports other intelligence-on-the-edge scenarios to offload processing to the edge from the Azure IoT Central application.
77+
78+
## Security
79+
80+
All data exchanged between devices and your Azure IoT Central is encrypted. IoT Hub authenticates every request from a device that connects to any of the device-facing IoT Hub endpoints. To avoid exchanging credentials over the wire, a device uses signed tokens to authenticate. For more information, see, [Control access to IoT Hub](https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-security).
81+
82+
> [!NOTE]
83+
> Currently, devices that connect to Azure IoT Central must use SAS tokens. X.509 certificates are not supported for devices that connect to Azure IoT Central.
84+
85+
## Next steps
86+
87+
Now that you have learned about device connectivity in Azure IoT Central, here are the suggested next steps:
88+
89+
- [Prepare and connect a DevKit device](howto-connect-devkit.md)
90+
- [Prepare and connect a Raspberry Pi](howto-connect-raspberry-pi-python.md)
91+
- [Connect a generic Node.js client to your Azure IoT Central application](howto-connect-nodejs.md)

0 commit comments

Comments
 (0)