Merge pull request #267940 from dominicbetts/central-freshness

IoT Central: Freshness and curation

Author: v-dirichards

articles/iot-central/.openpublishing.redirection.iot-central.json

@@ -1389,6 +1389,21 @@
       "source_path_from_root": "/articles/iot-central/core/troubleshoot-connection.md",
       "redirect_url": "/azure/iot-central/core/troubleshooting",
       "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/core/howto-manage-dashboards-with-rest-api.md",
+      "redirect_url": "/azure/iot-central/core/howto-manage-iot-central-with-rest-api",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/core/concepts-faq-apaas-paas.md",
+      "redirect_url": "/azure/iot-central/core/howto-migrate-to-iot-hub",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/core/tutorial-industrial-end-to-end.md",
+      "redirect_url": "/azure/iot/iot-introduction",
+      "redirect_document_id": false
     }
   ]
 }

articles/iot-central/TOC.yml

@@ -33,8 +33,6 @@
       items:
       - name: Create a rule
         href: core/tutorial-create-telemetry-rules.md
-      - name: Explore an Azure IoT Central industrial scenario
-        href: core/tutorial-industrial-end-to-end.md
       - name: Explore the IoT Central APIs
         href: core/tutorial-use-rest-api.md
     - name: Create industry specific demo apps
@@ -110,8 +108,7 @@
       href: core/concepts-faq-scalability-availability.md
     - name: What are IoT Central's scale limits?
       href: core/concepts-quotas-limits.md
-    - name: How do I move between aPaaS and PaaS solutions?
-      href: core/concepts-faq-apaas-paas.md
+
 - name: How-to guides
   items:
     - name: Create an application
@@ -209,8 +206,6 @@
           href: core/howto-manage-jobs-with-rest-api.md
         - name: Manage applications
           href: core/howto-manage-iot-central-with-rest-api.md
-        - name: Manage dashboards  
-          href: core/howto-manage-dashboards-with-rest-api.md
         - name: File upload
           href: core/howto-upload-file-rest-api.md
 
@@ -270,8 +265,6 @@
       href: https://devices.cloudrail.com/documentation?service=AzureIoTCentral#azureiotcentral1
     - name: Ignition
       href: https://docs.chariot.io/display/CLD80/Publishing+Data+to+Azure+IoT+Central
-    - name: Omnio
-      href: https://www.omnio.net/contact
 
   - name: Azure IoT services
     items:

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

@@ -1,9 +1,9 @@
 ---
-title: Architectural concepts in Azure IoT Central
+title: Azure IoT Central solution architecture
 description: This article introduces key IoT Central architectural concepts such as device management, security, integration, and extensibility.
 author: dominicbetts
 ms.author: dobett
-ms.date: 11/28/2022
+ms.date: 03/04/2024
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -60,7 +60,7 @@ A device can use properties to report its state, such as whether a valve is open
 
 IoT Central can also control devices by calling commands on the device. For example, instructing a device to download and install a firmware update.
 
-The telemetry, properties, and commands that a device implements are collectively known as the device capabilities. You define these capabilities in a model that's shared between the device and the IoT Central application. In IoT Central, this model is part of the device template that defines a specific type of device. To learn more, see [Assign a device to a device template](concepts-device-templates.md#assign-a-device-to-a-device-template).
+The telemetry, properties, and commands that a device implements are collectively known as the device capabilities. You define these capabilities in a model that the device and the IoT Central application share. In IoT Central, this model is part of the device template that defines a specific type of device. To learn more, see [Assign a device to a device template](concepts-device-templates.md#assign-a-device-to-a-device-template).
 
 The [device implementation](tutorial-connect-device.md) should follow the [IoT Plug and Play conventions](../../iot/concepts-convention.md) to ensure that it can communicate with IoT Central. For more information, see the various language [SDKs and samples](../../iot-develop/about-iot-sdks.md).
 
@@ -70,7 +70,7 @@ Devices connect to IoT Central using one the supported protocols: [MQTT, AMQP, o
 
 Local gateway devices are useful in several scenarios, such as:
 
-- Devices can't connect directly to IoT Central because they can't connect to the internet. For example, you may have a collection of Bluetooth enabled occupancy sensors that need to connect through a gateway device.
+- Devices can't connect directly to IoT Central because they can't connect to the internet. For example, you might have a collection of Bluetooth enabled occupancy sensors that need to connect through a gateway device.
 - The quantity of data generated by your devices is high. To reduce costs, combine or aggregate the data in a local gateway before you send it to your IoT Central application.
 - Your solution requires fast responses to anomalies in the data. You can run rules on a gateway device that identify anomalies and take an action locally without the need to send data to your IoT Central application.
 
@@ -80,22 +80,21 @@ Gateway devices typically require more processing power than a standalone device
 
 Although IoT Central has built-in analytics features, you can export data to other services and applications.
 
-[Transformations](howto-transform-data-internally.md) in an IoT Central data export definition let you manipulate the format and structure of the device data before it's exported to a destination.
+[Transformations](howto-transform-data-internally.md) in an IoT Central data export definition let you manipulate the format and structure of the device data before exporting it to a destination.
 
 Reasons to export data include:
 
 ### Storage and analysis
 
-For long-term storage and control over archiving and retention policies, you can [continuously export your data](howto-export-to-blob-storage.md).
- to other storage destinations. Use of separate storage also lets you use other analytics tools to derive insights and view the data in your solution.
+For long-term storage and control over archiving and retention policies, you can [continuously export your data](howto-export-to-blob-storage.md) to other storage destinations. The use of a separate storage service outside of IoT Central lets you use other analytics tools to derive insights from the data in your solution.
 
 ### Business automation
 
 [Rules](howto-configure-rules-advanced.md) in IoT Central let your trigger external actions, such as to send an email or fire an event, in response to conditions within IoT Central. For example, you can notify an engineer if the ambient temperature for a device reaches a threshold.
 
 ### Additional computation
 
-You may need to [transform or do computations](howto-transform-data.md) on your data before it can be used either in IoT Central or another service. For example, you could add local weather information to the location data reported by a delivery truck.
+You might need to [transform or do computations](howto-transform-data.md) on your data before it can be used either in IoT Central or another service. For example, you could add local weather information to the location data reported by a delivery truck.
 
 ## Extend with REST API
 
@@ -104,4 +103,3 @@ Build integrations that let other applications and services manage your applicat
 ## Next steps
 
 Now that you've learned about the architecture of Azure IoT Central, the suggested next step is to learn about [device connectivity](overview-iot-central-developer.md) in Azure IoT Central.
-

articles/iot-central/core/concepts-device-authentication.md

@@ -3,7 +3,7 @@ title: Device authentication in Azure IoT Central
 description: This article introduces key IoT Central device authentication concepts such as enrollment groups, shared access signatures, and X.509 certificates.
 author: dominicbetts
 ms.author: dobett
-ms.date: 10/28/2022
+ms.date: 03/01/2024
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -31,17 +31,17 @@ This article describes the following device authentication options:
 
 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).
 
-An X.509 enrollment group contains a root or intermediate X.509 certificate. Devices can authenticate if they have a valid leaf certificate that's derived from the root or intermediate certificate.
+An X.509 enrollment group contains a root or intermediate X.509 certificate. Devices can authenticate if they have a valid leaf certificate derived from the root or intermediate certificate.
 
 To connect a device with an X.509 certificate to your application:
 
 1. Create an _enrollment group_ that uses the **Certificates (X.509)** attestation type.
 1. Add and verify an intermediate or root X.509 certificate in the enrollment group.
 1. Generate a leaf certificate from the root or intermediate certificate in the enrollment group. Install the leaf certificate on the device for it to use when it connects to your application.
 
-Each enrollment group should use a unique X.509 certificate. IoT Central does not support using the same X.509 certificate across multiple enrollment groups.
+Each enrollment group should use a unique X.509 certificate. IoT Central doesn't support using the same X.509 certificate across multiple enrollment groups.
 
-To learn more, see [How to connect devices with X.509 certificates](how-to-connect-devices-x509.md)
+To learn more, see [How to connect devices with X.509 certificates](how-to-connect-devices-x509.md).
 
 ### For testing purposes only
 
@@ -56,7 +56,7 @@ In a production environment, use certificates from your certificate provider. Fo
 
 ## SAS enrollment group
 
-A SAS enrollment group contains group-level SAS keys. Devices can authenticate if they have a valid SAS token that's derived from a group-level SAS key.
+A SAS enrollment group contains group-level SAS keys. Devices can authenticate if they have a valid SAS token derived from a group-level SAS key.
 
 To connect a device with device SAS token to your application:
 
@@ -73,11 +73,11 @@ To connect a device with device SAS token to your application:
 > [!NOTE]
 > To use existing SAS keys in your enrollment groups, disable the **Auto generate keys** toggle and manually enter your SAS keys.
 
-If you use the default **SAS-IoT-Devices** enrollment group, IoT Central generates the individual device keys for you. To access these keys, select **Connect** on the device details page. This page displays the **ID Scope**, **Device ID**, **Primary key**, and **Secondary key** that you use in your device code. This page also displays a QR code the contains the same data.
+If you use the default **SAS-IoT-Devices** enrollment group, IoT Central generates the individual device keys for you. To access these keys, select **Connect** on the device details page. This page displays the **ID Scope**, **Device ID**, **Primary key**, and **Secondary key** that you use in your device code. This page also displays a QR code that contains the same data.
 
 ## Individual enrollment
 
-Typically, devices connect by using credentials derived from an enrollment group X.509 certificate or SAS key. However, if your devices each have their own credentials, you can use individual enrollments. An individual enrollment is an entry for a single device that's allowed to connect. Individual enrollments can use either X.509 leaf certificates or SAS tokens (from a physical or virtual trusted platform module) as attestation mechanisms. For more information, see [DPS individual enrollment](../../iot-dps/concepts-service.md#individual-enrollment).
+Typically, devices connect by using credentials derived from an enrollment group X.509 certificate or SAS key. However, if your devices each have their own credentials, you can use individual enrollments. An individual enrollment is an entry for a single device allowing it to connect. Individual enrollments can use either X.509 leaf certificates or SAS tokens (from a physical or virtual trusted platform module) as attestation mechanisms. For more information, see [DPS individual enrollment](../../iot-dps/concepts-service.md#individual-enrollment).
 
 > [!NOTE]
 > When you create an individual enrollment for a device, it takes precedence over the default enrollment group options in your IoT Central application.

articles/iot-central/core/concepts-faq-apaas-paas.md

@@ -3,7 +3,7 @@ title: Scalability and high availability
 description: This article describes how IoT Central automatically scales to handle more devices, its high availability disaster recovery capabilities.
 author: dominicbetts
 ms.author: dobett
-ms.date: 03/21/2023
+ms.date: 03/04/2024
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central

articles/iot-central/core/concepts-faq-scalability-availability.md

@@ -3,7 +3,7 @@ title: Industrial IoT patterns with Azure IoT Central
 description: This article introduces common Industrial IoT patterns that you can implement using Azure IoT Central
 author: dominicbetts
 ms.author: dobett
-ms.date: 11/28/2022
+ms.date: 03/01/2024
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -23,6 +23,8 @@ IoT Central lets you evaluate your IIoT scenario by using the following built-in
 
 By using the Azure IoT platform, IoT Central lets you evaluate solutions that are scalable and secure.
 
+To set up a sample to evaluate a solution, see [Ingest Industrial Data with Azure IoT Central and Calculate OEE](https://github.com/Azure-Samples/iotc-solution-builder).
+
 ## Connect your industrial assets
 
 Operational technology (OT) is the hardware and software that monitors and controls the equipment and infrastructure in industrial facilities. There are four ways to connect your industrial assets to Azure IoT Central:

articles/iot-central/core/concepts-iiot-architecture.md

@@ -3,7 +3,7 @@ title: Azure IoT Edge and Azure IoT Central
 description: Understand how to use Azure IoT Edge with an IoT Central application including the different gateway patterns and IoT Edge management capabilities.
 author: dominicbetts
 ms.author: dobett
-ms.date: 10/11/2022
+ms.date: 03/04/2024
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -52,7 +52,7 @@ IoT Central enables the following capabilities to for IoT Edge devices:
 An IoT Edge device can be:
 
 * A standalone device composed of custom modules.
-* A *gateway device*, with downstream devices connecting to it. A gateway device may include custom modules.
+* A *gateway device*, with downstream devices connecting to it. A gateway device can include custom modules.
 
 ## IoT Edge devices and IoT Central