Merge pull request #93158 from MicrosoftDocs/release-ignite-iotcentral-refresh

Merge the IoT Central release branch to master

Author: huypub

.openpublishing.redirection.json

@@ -36168,6 +36168,46 @@
       "redirect_url": "/azure/key-vault/vs-key-vault-add-connected-service",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/iot-central/core/howto-create-event-rules-pnp.md",
+      "redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-central/core/howto-create-telemetry-rules-pnp.md",
+      "redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-central/core/tutorial-configure-rules-pnp.md",
+      "redirect_url": "/azure/iot-central/core/tutorial-create-telemetry-rules",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-central/core/tutorial-monitor-devices-pnp.md",
+      "redirect_url": "/azure/iot-central/core/quick-monitor-devices-pnp",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-central/tutorial-add-device-pnp.md",
+      "redirect_url": "/azure/iot-central/quick-create-pnp-device-pnp",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-central/tutorial-define-device-type-pnp.md",
+      "redirect_url": "/azure/iot-central/quick-create-pnp-device-pnp",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-central/howto-export-data-blob-storage-pnp.md",
+      "redirect_url": "/azure/iot-central/howto-export-data-pnp",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-central/howto-export-data-event-hubs-service-bus-pnp.md",
+      "redirect_url": "/azure/iot-central/howto-export-data-pnp",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/iot-central/howto-generate-connection-string.md",
       "redirect_url": "/azure/iot-central",

articles/iot-accelerators/iot-accelerators-arduino-iot-devkit-az3166-devkit-remote-monitoring-v2.md

@@ -124,4 +124,4 @@ Now that you've learned how to connect a DevKit device to your Remote Monitoring
 
 * [Azure IoT solution accelerators overview](https://docs.microsoft.com/azure/iot-accelerators/)
 * [Customize the UI](iot-accelerators-remote-monitoring-customize.md)
-* [Connect IoT DevKit to your Azure IoT Central application](../iot-central/howto-connect-devkit.md)
+* [Connect IoT DevKit to your Azure IoT Central application](../iot-central/core/howto-connect-devkit.md)

articles/iot-central-pnp/breadcrumb/toc.yml

@@ -6,6 +6,10 @@
     tocHref: /azure/iot-fundamentals/
     topicHref: /azure/iot-fundamentals/index
     items: 
-    - name: IoT Central (preview features) 
+    - name: IoT Central
       tocHref: /azure/iot-central/
-      topicHref: /azure/iot-central/index-pnp?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json
+      topicHref: /azure/iot-central/
+      items:
+      - name: IoT Central core (preview features) 
+        tocHref: /azure/iot-central/
+        topicHref: /azure/iot-central/index?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json

articles/iot-central-pnp/toc.yml

@@ -7,7 +7,9 @@
   - name: IoT Solution options
     href: overview-iot-options.md
   - name: Tour of the UI
-    href: overview-iot-central-tour.md
+    href: overview-iot-central-tour.md    
+  - name: Stay connected
+    href: concepts-stay-connected.md
 - name: Quickstarts
   expanded: true
   items:
@@ -31,6 +33,8 @@
     href: concepts-architecture.md
   - name: Connectivity
     href: concepts-connectivity.md
+  - name: What are application templates?
+    href: concepts-app-templates.md
 - name: How-to guides
   items:
   - name : Connect devices
@@ -47,6 +51,8 @@
         href: howto-connect-windowsiotcore.md
       - name: Prepare and connect a SensorTile.box device
         href: howto-connect-sensortile.md
+      - name: Prepare and connect a RuuviTag device
+        href: howto-connect-ruuvi-pnp.md?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json
       - name: Monitor device connectivity using command line
         href: howto-use-iotc-explorer.md
   - name: Manage devices
@@ -108,8 +114,8 @@
         href: howto-customize-ui.md  
       - name: Prepare and upload image
         href: howto-prepare-images.md
-      - name: Configure application dashboard
-        href: howto-configure-homepage.md
+      - name: Add tiles to your dashboard
+        href: howto-add-tiles-to-your-dashboard.md
       - name: Use dashboard tiles
         href: howto-use-tiles.md
       - name: Use application templates
@@ -124,8 +130,8 @@
         href: howto-create-and-manage-applications-csp.md
   - name : Personalization
     items:
-      - name: Create personal dashboards
-        href: howto-personalize-dashboard.md
+      - name: Create Azure IoT Central personal dashboards
+        href: howto-create-personal-dashboards.md
       - name: Manage your preferences
         href: howto-manage-preferences.md
       - name: Toggle live chat

articles/iot-central/TOC.yml renamed to articles/iot-central/core/TOC.yml

@@ -0,0 +1,47 @@
+---
+title: What are application templates in Azure IoT Central | Microsoft Docs
+description: Azure IoT Central application templates allow you to jump in to IoT solution development.
+author: philmea
+ms.author: philmea
+ms.date: 10/25/2019
+ms.topic: conceptual
+ms.service: iot-central
+services: iot-central
+---
+
+# What are application templates?
+
+Application templates in Azure IoT Central are a tool to help solution builders kickstart their IoT solution development. You can use app templates for everything from getting a feel for what is possible, to fully customizing and white labeling your application for resale to your customers.
+
+Application templates consist of:
+
+- Sample operator dashboards
+- Sample device templates
+- Simulated devices producing real-time data
+- Pre-configured rules and jobs
+- Rich documentation including tutorials and how-tos
+
+## Industry focused app templates
+
+Azure IoT Central is an industry agnostic application platform. Application templates are industry focused examples available for these industries today, with more to come in the future:
+
+- [Retail](../retail/overview-iot-central-retail-pnp.md)
+  - Connected logistics
+  - Digital distribution center
+  - In-store analytics - condition monitoring
+  - In-store analytics - checkout
+  - Smart Inventory Management
+- [Energy](../energy/overview-iot-central-energy.md)
+  - Connected Logistics
+  - Smart meter monitoring
+  - Solar panel monitoring
+- [Government](../government/overview-iot-central-government.md)
+  - Connected waste management
+  - Water consumption monitoring
+  - Water quality monitoring
+- [Healthcare](../healthcare/overview-iot-central-healthcare.md).
+  - Continuous patient monitoring
+
+## Next steps
+
+Now that you know what IoT Central application templates are, get started by [creating an IoT Central Application](quick-deploy-iot-central-pnp.md).

articles/iot-central/core/concepts-app-templates.md

@@ -3,7 +3,7 @@ title: Architectural concepts in Azure IoT Central | Microsoft Docs
 description: This article introduces key concepts relating the architecture of Azure IoT Central
 author: dominicbetts
 ms.author: dobett
-ms.date: 05/31/2019
+ms.date: 10/15/2019
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -12,7 +12,7 @@ manager: philmea
 
 # Azure IoT Central architecture (preview features)
 
-[!INCLUDE [iot-central-pnp-original](../../includes/iot-central-pnp-original-note.md)]
+[!INCLUDE [iot-central-pnp-original](../../../includes/iot-central-pnp-original-note.md)]
 
 This article provides an overview of the Microsoft Azure IoT Central architecture.
 
@@ -68,7 +68,7 @@ In an Azure IoT Central application, device templates define the behavior and ca
 
 In an IoT Central Preview application device template:
 
-- **Device capability models** specify the capabilities of a device such as the telemetry it sends, the properties that define the device state, and the commands the device responds to. Device capabilities are organized into one or more interfaces. For more information about device capability models, see the the [IoT Plug and Play](../iot-pnp/overview-iot-plug-and-play.md) documentation.
+- **Device capability models** specify the capabilities of a device such as the telemetry it sends, the properties that define the device state, and the commands the device responds to. Device capabilities are organized into one or more interfaces. For more information about device capability models, see the [IoT Plug and Play](../../iot-pnp/overview-iot-plug-and-play.md) documentation.
 - **Cloud properties** specify the properties IoT Central stores for a device. These properties are only stored in IoT Central and are never sent to a device.
 - **Views** specify the dashboards and forms the builder creates to let the operator monitor and manage the devices.
 - **Customizations** let the builder override some of the definitions in the device capability model to make them more relevant to the IoT Central application.
@@ -77,7 +77,7 @@ An application can have one or more simulated and real devices based on each dev
 
 ## Data export
 
-In an Azure IoT Central application, you can [continuously export your data](howto-export-data-event-hubs-service-bus-pnp.md?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json) to your own Azure Event Hubs, and Azure Service Bus instances. You can also periodically export your data to your Azure Blob storage account. IoT Central can export measurements, devices, and device templates.
+In an Azure IoT Central application, you can [continuously export your data](howto-export-data-pnp.md?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json) to your own Azure Event Hubs and Azure Service Bus instances. You can also periodically export your data to your Azure Blob storage account. IoT Central can export measurements, devices, and device templates.
 
 ## Batch device updates
 

articles/iot-central/concepts-architecture-pnp.md renamed to articles/iot-central/core/concepts-architecture-pnp.md

@@ -12,7 +12,7 @@ manager: philmea
 
 # Azure IoT Central architecture
 
-[!INCLUDE [iot-central-original-pnp](../../includes/iot-central-original-pnp-note.md)]
+[!INCLUDE [iot-central-original-pnp](../../../includes/iot-central-original-pnp-note.md)]
 
 This article provides an overview of the Microsoft Azure IoT Central architecture.
 

articles/iot-central/concepts-architecture.md renamed to articles/iot-central/core/concepts-architecture.md

@@ -12,7 +12,7 @@ manager: philmea
 
 # Device connectivity in Azure IoT Central (preview features)
 
-[!INCLUDE [iot-central-pnp-original](../../includes/iot-central-pnp-original-note.md)]
+[!INCLUDE [iot-central-pnp-original](../../../includes/iot-central-pnp-original-note.md)]
 
 This article introduces key concepts relating to device connectivity in Microsoft Azure IoT Central.
 
@@ -33,7 +33,7 @@ This article describes the following use cases:
 - [Connect devices at scale using SAS](#connect-devices-at-scale-using-sas)
 - [Connect devices at scale using X.509 certificates](#connect-devices-using-x509-certificates) this is the recommended approach for production environments.
 - [Connect without first registering devices](#connect-without-registering-devices)
-- [Connect devices using IoT Plug and Play features](howto-connect-pnp-device-pnp.md?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json)
+- [Connect devices using IoT Plug and Play features](#connect-devices-with-iot-plug-and-play)
 
 ## Connect a single device
 
@@ -61,7 +61,7 @@ Use the connection information from the export file in your device code to enabl
 
 ## Connect devices using X.509 certificates
 
-In a production environment, using X.509 certificates is the recommended device authentication mechanism for IoT Central. To learn more, see [Device Authentication using X.509 CA Certificates](../iot-hub/iot-hub-x509ca-overview.md).
+In a production environment, using X.509 certificates is the recommended device authentication mechanism for IoT Central. To learn more, see [Device Authentication using X.509 CA Certificates](../../iot-hub/iot-hub-x509ca-overview.md).
 
 The following steps describe how to connect devices to IoT Central using X.509 certificates:
 
@@ -140,6 +140,20 @@ The following steps describe this process in more detail. The steps differ sligh
 
 1. The connected device initially shows up as **Unassociated** on the **Devices** page. The device provisioning status is **Registered**. **Migrate** the device to the appropriate device template and approve the device to connect to your IoT Central application. The device can then retrieve a connection string from IoT Hub and start sending data. Device provisioning is now complete and the provisioning status is now **Provisioned**.
 
+## Individual enrollment based device connectivity
+
+For customers connecting devices that have authentication credentials that are per device individual enrollment is the option. An individual enrollment is an entry for a single device that may connect. Individual enrollments may use either X.509 leaf certificates or SAS tokens (from a physical or virtual TPM) as attestation mechanisms. The device ID (aka registration ID) in an individual enrollment is alphanumeric, lowercase, and may contain hyphens.Learn more on Individual enrollments [here](https://docs.microsoft.com/azure/iot-dps/concepts-service#individual-enrollment).
+
+> [!NOTE]
+> When you create an Individual enrollment for a device it takes precedence over the default Group enrollment based attestations (SAS, X509) in your app.
+
+### Creating individual enrollments
+IoT Central supports the following attestation mechanisms
+
+1. **Symmetric key attestation:** Symmetric key attestation is a simple approach to authenticating a device with a Device Provisioning Service instance. To create an individual enrollment with Symmetric keys; open the Connect dialog, select Individual Enrollment and Mechanism “SAS” and input the Primary and Secondary keys. SAS keys must be base64 encoded. Here is the [link](https://github.com/Azure-Samples/azure-iot-samples-csharp/tree/master/provisioning/Samples/device/SymmetricKeySample) to code samples to help write your device code to provision devices using Symmetric keys and individual enrollments.
+1. **X.509 certificates:** X.509 certificates as the title suggests is a cert based attestation mechanism, an excellent way to scale production. To create an individual enrollment with Symmetric keys select Individual Enrollment and Mechanism “X.509” and upload the primary and secondary certificates and save to create the enrollment. Here is the [link](https://github.com/Azure-Samples/azure-iot-samples-csharp/tree/master/provisioning/Samples/device/X509Sample) to code samples to help write your device code to provision devices using X509. Device certificates used with an [Individual enrollment](https://docs.microsoft.com/azure/iot-dps/concepts-service#individual-enrollment) entry have a requirement that the Subject Name must be set to the Device ID (aka registration ID) of the Individual Enrollment entry.
+1. **TPM attestation:** TPM stands for Trusted Platform Module and is a type of hardware security module (HSM) and is one of the most secure ways to connect your devices.  This article assumes you are using a discrete, firmware, or integrated TPM. Software emulated TPMs are well-suited for prototyping or testing, but they do not provide the same level of security as discrete, firmware, or integrated TPMs do. We do not recommend using software TPMs in production. To create an individual enrollment with Symmetric keys select Individual Enrollment and Mechanism “TPM” and input the endorsement keys to create the enrollment.For more information about types of TPMs, you can learn more about TPM attestation [here](https://docs.microsoft.com/azure/iot-dps/concepts-tpm-attestation). Here is the [link](https://github.com/Azure-Samples/azure-iot-samples-csharp/tree/master/provisioning/Samples/device/TpmSample) to code samples to help write your device code to provision devices using TPM. To create a TPM based attestation, type in the endorsement key and save.
+
 ## Connect devices with IoT Plug and Play
 
 One of the key features of IoT Plug and Play with IoT Central is the ability to associate device templates automatically on device connection. Along with device credentials, devices can now send the **CapabilityModelId** as part of the device registration call and IoT Central will discover and associate the device template. The discovery process follows the following order:
@@ -155,8 +169,6 @@ Below is the format of the additional payload the device would send during the D
           }
 ```
 
-To learn more about connecting an IoT Plug and Play device, see how to [Connect an IoT Plug and Play device](howto-connect-pnp-device-pnp.md?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json).
-
 > [!NOTE]
 > Note that the Auto-Approve option should be enabled for devices to automatically connect, discover the model and start sending data.
 
@@ -193,8 +205,8 @@ The Azure Device SDKs offer the easiest way for you implement your device code.
 
 All device communication with IoT Hub uses the following IoT Hub connectivity options:
 
-- [Device-to-cloud messaging](../iot-hub/iot-hub-devguide-messages-d2c.md)
-- [Device twins](../iot-hub/iot-hub-devguide-device-twins.md)
+- [Device-to-cloud messaging](../../iot-hub/iot-hub-devguide-messages-d2c.md)
+- [Device twins](../../iot-hub/iot-hub-devguide-device-twins.md)
 
 The following table summarizes how Azure IoT Central device features map on to IoT Hub features:
 
@@ -214,18 +226,17 @@ The Device SDKs support the following network protocols for connecting to an IoT
 - AMQP
 - HTTPS
 
-For information about these difference protocols and guidance on choosing one, see [Choose a communication protocol](../iot-hub/iot-hub-devguide-protocols.md).
+For information about these difference protocols and guidance on choosing one, see [Choose a communication protocol](../../iot-hub/iot-hub-devguide-protocols.md).
 
 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.
 
 ## Security
 
-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](../iot-hub/iot-hub-devguide-security.md).
+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](../../iot-hub/iot-hub-devguide-security.md).
 
 ## Next steps
 
 Now that you've learned about device connectivity in Azure IoT Central, here are the suggested next steps:
 
-- [Connect an IoT Plug and Play device](howto-connect-pnp-device-pnp.md?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json)
 - [Prepare and connect a DevKit device](howto-connect-devkit-pnp.md?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json)
 - [C SDK: Provisioning Device Client SDK](https://github.com/Azure/azure-iot-sdk-c/blob/master/provisioning_client/devdoc/using_provisioning_client.md)