Merge pull request #219623 from dominicbetts/central-messaging-updates

IoT Central: update IoT Central messaging

Author: 19BMG00

.openpublishing.publish.config.json

@@ -950,6 +950,7 @@
     "articles/iot-accelerators/.openpublishing.redirection.iot-accelerators.json",
     "articles/iot-develop/.openpublishing.redirection.iot-develop.json",
     "articles/iot-edge/.openpublishing.redirection.iot-edge.json",
+    "articles/iot-fundamentals/.openpublishing.redirection.iot-fundamentals.json",
     "articles/mariadb/.openpublishing.redirection.mariadb.json",
     "articles/marketplace/.openpublishing.redirection.marketplace.json",
     "articles/mysql/.openpublishing.redirection.mysql.json",

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

@@ -1344,6 +1344,11 @@
       "source_path_from_root": "/articles/iot-central/core/howto-migrate.md",
       "redirect_url": "/azure/iot-central/core/overview-iot-central/",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/core/concepts-faq-start-iot-central.md",
+      "redirect_url": "/azure/iot-central/core/overview-iot-central/",
+      "redirect_document_id": false
     }
   ]
 }

articles/iot-central/TOC.yml

@@ -8,8 +8,6 @@
     href: core/overview-iot-central-tour.md
   - name: Tour of the API
     href: core/overview-iot-central-api-tour.md
-  - name: What's new?
-    href: https://azure.microsoft.com/updates/?status=nowavailable&updateType=features&category=iot&query=azure%20iot%20central
 - name: Quickstarts
   expanded: true
   items:
@@ -113,8 +111,6 @@
     - name: FAQ
       href: core/howto-faq.yml
       items:
-      - name: Why should I start with IoT Central?
-        href: core/concepts-faq-start-iot-central.md
       - name: How do I extend IoT Central?
         href: core/concepts-faq-extend.md
       - name: How does IoT Central scale and enable HADR?

articles/iot-central/core/concepts-architecture.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: 06/03/2022
+ms.date: 11/28/2022
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -12,7 +12,7 @@ ms.custom: [iot-central-frontdoor]
 
 # Azure IoT Central architecture
 
-IoT Central is a ready-made environment for IoT solution development. It's an application platform as a service (aPaaS) IoT solution and its primary interface is a web UI. There's also a [REST API](#extend-with-rest-api) that lets you interact with your application programmatically.
+IoT Central is a ready-made environment that lets you quickly evaluate your IoT scenario. It's an application platform as a service (aPaaS) IoT solution and its primary interface is a web UI. There's also a [REST API](#extend-with-rest-api) that lets you interact with your application programmatically.
 
 This article provides an overview of the key elements in an IoT Central solution architecture.
 
@@ -104,3 +104,4 @@ 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-faq-apaas-paas.md

@@ -3,20 +3,19 @@ title: Move from IoT Central to a PaaS solution | Microsoft Docs
 description: How do I move between aPaaS and PaaS solution approaches?
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/09/2022
+ms.date: 11/28/2022
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
-
 ---
 
 # How do I move between aPaaS and PaaS solutions?
 
-When you begin your IoT journey, start with Azure IoT Central. IoT Central is the Microsoft application platform as a service (aPaaS) IoT offering. IoT Central is the fastest and easiest way to get started using Azure IoT. However, if you require a high level of customization, you can move from IoT Central and go lower in the stack with the Azure IoT platform as a service (PaaS) services. Use the *IoT Central migrator tool* to migrate devices seamlessly from IoT Central to a custom PaaS solution that uses the Device Provisioning Service (DPS) and IoT Hub service.
+IoT Central is the fastest and easiest way to evaluate your IoT scenario. You can use the *IoT Central migrator tool* to migrate devices seamlessly from IoT Central to a platform as a service (PaaS) solution that uses IoT Hub and the Device Provisioning Service (DPS).
 
 ## Move devices with the IoT Central migrator tool
 
-Use the migrator tool to move devices with no downtime from IoT Central to your own DPS instance. In a PaaS solution, you link a DPS instance to your IoT hub. The migrator tool disconnects devices from IoT Central and connects them to your PaaS solution. From this point forward, new devices are created in your IoT hub. Old device registrations remain in IoT Central so that you can fall back to IoT Central just if something goes wrong.
+Use the migrator tool to move devices with no downtime from IoT Central to your own DPS instance. In a PaaS solution, you link a DPS instance to your IoT hub. The migrator tool disconnects devices from IoT Central and connects them to your PaaS solution. From this point forward, new devices are created in your IoT hub.
 
 Download the [migrator tool from GitHub](https://github.com/Azure/iotc-migrator).
 
@@ -37,19 +36,18 @@ Minimize business impact by following these steps:
 
 - When you've migrated all the devices to the PaaS solution and fully exported your data from IoT Central, you can remove the devices from the IoT Central solution.
 
-After the migration, devices aren't automatically deleted from the IoT Central application so that you can fail them back from your PaaS solution. These devices continue to be billed as IoT Central charges for all provisioned devices in the application. When you remove these devices from the IoT Central application, they're no longer be billed. Eventually, remove the IoT Central application.
+After the migration, devices aren't automatically deleted from the IoT Central application. These devices continue to be billed as IoT Central charges for all provisioned devices in the application. When you remove these devices from the IoT Central application, you're no longer billed for them. Eventually, remove the IoT Central application.
 
 ## Firmware best practices
 
 So that you can seamlessly migrate devices from your IoT Central applications to PaaS solution, follow these guidelines:
 
-- The device must be an IoT Plug and Play device that uses a [Digital Twins Definition Language (DTDL) V2](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md) model. IoT Central requires all devices to have a DTDL model. This simplifies the interoperability between an IoT PaaS solution and IoT Central.
+- The device must be an IoT Plug and Play device that uses a [Digital Twins Definition Language (DTDL) V2](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md) model. IoT Central requires all devices to have a DTDL model. These models simplify the interoperability between an IoT PaaS solution and IoT Central.
 
 - The device must follow the [IoT Central data formats for telemetry, property, and commands](concepts-telemetry-properties-commands.md).
 
-- IoT Central uses the DPS to provision the devices. The PaaS solution must also use DPS to  provision the devices.
-
-- The updateable DPS pattern ensures that the device can move seamlessly between IoT Central applications and the PaaS solution without any downtime.
+- IoT Central uses the DPS to provision the devices. The PaaS solution must also use DPS to provision the devices.
+- The updatable DPS pattern ensures that the device can move seamlessly between IoT Central applications and the PaaS solution without any downtime.
 
 ## Move existing data out of IoT Central
 
@@ -58,3 +56,4 @@ You can configure IoT Central to continuously export telemetry and property valu
 ## Next steps  
 
 Now that you've learned about moving from aPaaS to PaaS solutions, a suggested next step is to explore the [IoT Central migrator tool](https://github.com/Azure/iotc-migrator).
+

articles/iot-central/core/concepts-faq-start-iot-central.md

@@ -3,26 +3,25 @@ title: Industrial IoT patterns with Azure IoT Central | Microsoft Docs
 description: This article introduces common Industrial IoT patterns that you can implement using Azure IoT Central
 author: dominicbetts
 ms.author: dobett
-ms.date: 04/27/2022
+ms.date: 11/28/2022
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
-
 ---
 
 # Industrial IoT (IIoT) architecture patterns with Azure IoT Central
 
-:::image type="content" source="media/concepts-iiot-architecture/industrial-iot-architecture.svg" alt-text="Diagram of high-level industrial I O T architecture." border="false":::
+:::image type="content" source="media/concepts-iiot-architecture/industrial-iot-architecture.svg" alt-text="Diagram of high-level industrial IoT architecture." border="false":::
 
-IoT Central enables you to implement your IIoT scenario by using the following built-in capabilities:
+IoT Central lets you evaluate your IIoT scenario by using the following built-in capabilities:
 
 - Connect industrial assets either directly or through a gateway device
 - Collect data at scale from your industrial assets
 - Manage your connected industrial assets in bulk using jobs
 - Model and organize the data from your industrial assets and use the built-in analytics and monitoring capabilities
 - Integrate and extend your solution by connecting to first and third party applications and services
 
-IoT Central enables you to build highly available, scalable, and secure solutions.
+By using the Azure IoT platform, IoT Central lets you evaluate solutions that are scalable and secure.
 
 ## Connect your industrial assets
 
@@ -138,3 +137,4 @@ Industrial networks are crucial to the working of a manufacturing facility. With
 ## Next steps
 
 Now that you've learned about IIoT architecture patterns with 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-iiot-architecture.md

@@ -69,7 +69,7 @@ When you configure a data export in your IoT Central application, you can choose
 IoT Central currently uses [system-assigned managed identities](../../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types). To create the managed identity for your application, you use either the Azure portal or the REST API.
 
 > [!NOTE]
-> You can only add a managed identity to an IoT Central application that was created in a region. All new applications are created in a region. To learn more, see [Updates](https://azure.microsoft.com/updates/azure-iot-central-new-and-updated-features-august-2021/).
+> You can only add a managed identity to an IoT Central application that was created in a region. All new applications are created in a region.
 
 When you configure a managed identity, the configuration includes a *scope* and a *role*:
 

articles/iot-central/core/howto-manage-iot-central-from-portal.md

@@ -90,7 +90,7 @@ Use the following payload to change the display name and enable the system assig
 ```
 
 > [!NOTE]
-> You can only add a managed identity to an IoT Central application that was created in a region. All new applications are created in a region. To learn more, see [Updates](https://azure.microsoft.com/updates/azure-iot-central-new-and-updated-features-august-2021/).
+> You can only add a managed identity to an IoT Central application that was created in a region. All new applications are created in a region.
 
 ## Delete an IoT Central application