Merge pull request #221762 from timlt/new-overview

Updates for shift to IoT Hub

Author: JamesJBarnett

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

@@ -424,6 +424,11 @@
       "source_path_from_root": "/articles/iot-pnp/overview-iot-plug-and-play-current-release.md",
       "redirect_url": "/azure/iot-develop/overview-iot-plug-and-play",
       "redirect_document_id": false
-    }  
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/concepts-overview-connection-options.md",
+      "redirect_url": "/azure/iot-develop/about-iot-develop",
+      "redirect_document_id": false      
+    }
   ]
 }

articles/iot-develop/TOC.yml

@@ -6,6 +6,8 @@
     href: about-iot-develop.md
   - name: Which SDK should I use?
     href: about-iot-sdks.md
+  - name: Get started with IoT device development
+    href: about-getting-started-device-development.md
 - name: Quickstarts
   expanded: true
   items:
@@ -47,8 +49,6 @@
       href: tutorial-migrate-device-to-module.md
 - name: Concepts
   items:
-  - name: Connection options for device developers
-    href: concepts-overview-connection-options.md
   - name: C SDK and Embedded C SDK usage scenarios
     href: concepts-using-c-sdk-and-embedded-c-sdk.md    
   - name: Overview of device types

articles/iot-develop/about-getting-started-device-development.md

@@ -0,0 +1,49 @@
+---
+title: Overview of getting started with Azure IoT device development
+description: Learn how to get started with Azure IoT device development quickstarts. 
+author: timlt
+ms.author: timlt
+ms.service: iot-develop
+ms.topic: overview
+ms.date: 12/15/2022
+ms.custom: engagement-fy23
+---
+
+# Get started with Azure IoT device development
+
+This article shows how to quickly get started with Azure IoT device development. As a prerequisite, see the introductory articles [What is Azure IoT device and application development?](about-iot-develop.md) and [Overview of Azure IoT Device SDKs](about-iot-sdks.md).  These articles summarize key development options, tools, and SDKs available to device developers. 
+
+In this article, you'll select from a set of device quickstarts to get started with hands-on development.
+
+## Quickstarts for general devices
+To start using the Azure IoT device SDKs to connect general, unconstrained MPU devices to Azure IoT, see the following articles.  These quickstarts provide simulators and don't require you to have a physical device.
+
+Each quickstart shows how to set up a code sample and tools, run a temperature controller sample, and connect it to Azure. After the device is connected, you perform several common operations. 
+
+|Quickstart|Device SDK|
+|-|-|
+|[Send telemetry from a device to Azure IoT Hub (C)](quickstart-send-telemetry-iot-hub.md?pivots=programming-language-ansi-c)|[Azure IoT C SDK](https://github.com/Azure/azure-iot-sdk-c)|
+|[Send telemetry from a device to Azure IoT Hub (C#)](quickstart-send-telemetry-iot-hub.md?pivots=programming-language-csharp)|[Azure IoT SDK for .NET](https://github.com/Azure/azure-iot-sdk-csharp)|
+|[Send telemetry from a device to Azure IoT Hub (Node.js)](quickstart-send-telemetry-iot-hub.md?pivots=programming-language-nodejs)|[Azure IoT Node.js SDK](https://github.com/Azure/azure-iot-sdk-node)|
+|[Send telemetry from a device to Azure IoT Hub (Python)](quickstart-send-telemetry-iot-hub.md?pivots=programming-language-python)|[Azure IoT Python SDK](https://github.com/Azure/azure-iot-sdk-python)|
+|[Send telemetry from a device to Azure IoT Hub (Java)](quickstart-send-telemetry-iot-hub.md?pivots=programming-language-java)|[Azure IoT SDK for Java](https://github.com/Azure/azure-iot-sdk-java)|
+
+## Quickstarts for embedded devices
+To start using the Azure IoT embedded device SDKs to connect embedded, resource-constrained MCU devices to Azure IoT, see the following articles.  These quickstarts require you to have one of the listed devices. 
+
+Each quickstart shows how to set up a code sample and tools, flash the device, and connect it to Azure. After the device is connected, you perform several common operations. 
+
+|Quickstart|Device|Embedded device SDK|
+|-|-|-|
+|[Quickstart: Connect a Microchip ATSAME54-XPro Evaluation kit to IoT Hub](quickstart-devkit-microchip-atsame54-xpro-iot-hub.md)|Microchip ATSAME54-XPro|Azure RTOS middleware|
+|[Quickstart: Connect an STMicroelectronics B-L475E-IOT01A Discovery kit to IoT Hub](quickstart-devkit-stm-b-l475e-iot-hub.md)|STMicroelectronics L475E-IOT01A|Azure RTOS middleware|
+|[Connect an MXCHIP AZ3166 devkit to IoT Hub](quickstart-devkit-mxchip-az3166-iot-hub.md)|MXCHIP AZ3166|Azure RTOS middleware|
+|[Quickstart: Connect an ESPRESSIF ESP32-Azure IoT Kit to IoT Central](quickstart-devkit-espressif-esp32-freertos.md)|ESPRESSIF ESP32|FreeRTOS middleware|
+|[Quickstart: Connect an STMicroelectronics B-L475E-IOT01A Discovery kit to Azure IoT Central](quickstart-devkit-stm-b-l475e-freertos.md)|STMicroelectronics L475E-IOT01A|FreeRTOS middleware|
+
+## Next steps
+To learn more about working with the IoT device SDKs and developing for general devices, see the following tutorial.
+- [Build a device solution for IoT Hub](set-up-environment.md)
+
+To learn more about working with the IoT C SDK and embedded C SDK for embedded devices, see the following article.
+- [C SDK and Embedded C SDK usage scenarios](concepts-using-c-sdk-and-embedded-c-sdk.md)

articles/iot-develop/about-iot-develop.md

@@ -1,35 +1,37 @@
 ---
 title: Introduction to Azure IoT device and application development
 description: Learn how to use Azure IoT to do embedded device development and build device-enabled cloud applications.
-author: ryanwinter
-ms.author: rywinter
+author: timlt
+ms.author: timlt
 ms.service: iot-develop
 ms.topic: overview
-ms.date: 10/07/2022
-ms.custom: engagement-fy23
+ms.date: 12/15/2022
 ---
 
 # What is Azure IoT device and application development?
 
 Azure IoT is a collection of managed and platform services that connect, monitor, and control your IoT devices. Azure IoT offers developers a comprehensive set of options. Your options include device platforms, supporting cloud services, SDKs, and tools for building device-enabled cloud applications.
 
-This article overviews several key considerations for developers who are getting started with Azure IoT. These concepts will orient you, as an IoT device developer, to your Azure IoT options and how to begin. Specifically, the article overviews these concepts:
-- [Understanding device development roles](#device-development-roles)
+This article overviews several key considerations for developers who are getting started with Azure IoT. These concepts will orient you, as an IoT device developer, to your Azure IoT options and how to begin. 
+- [Understanding device development paths](#device-development-paths)
 - [Choosing your hardware](#choosing-your-hardware)
 - [Choosing an SDK](#choosing-an-sdk)
-- [Selecting connection options](#selecting-connection-options)
+- [Selecting a service to connect device](#selecting-a-service)
+- [Tools to connect and manage devices](#tools-to-connect-and-manage-devices)
 
-## Device development roles
-This article discusses two common roles that you can observe among device developers. As used here, a role is a collection of related development tasks. It's useful to understand what type of development role you're currently working in. Your role impacts many development choices you make.
+## Device development paths
+This article discusses two common device development paths. Each path includes a set of related development options and tasks.  
 
-* **Device application development:** Aligns with modern development practices, targets many of the higher-order languages, and executes on a general-purpose operating system such as Windows or Linux.
+* **Device application development:** Aligns with modern development practices, targets many of the higher-order languages, and executes on a general-purpose operating system such as Windows or Linux. 
+    > [!NOTE]
+    > If your device is able to run a general-purpose operating system, we recommend following the [Device application development](#device-application-development) path. It provides a richer set of development options.
 
 * **Embedded device development:** Describes development targeting resource constrained devices. A resource constrained device will often be used to reduce per unit costs, power consumption, or device size. These devices have direct control over the hardware platform they execute on.
 
 ### Device application development
 Device application developers are adapting existing devices to connect to the cloud and integrate into their IoT solutions. These devices can support higher-order languages, such as C# or Python, and often support a robust general purpose operating system such as Windows or Linux. Common target devices include PCs, Containers, Raspberry Pis, and mobile devices. 
 
-Rather than develop constrained devices at scale, these developers focus on enabling a specific IoT scenario required by their cloud solution. Some of these developers will also work on constrained devices for their cloud solution. For developers working with resource constrained devices, see [Embedded Device Development](#embedded-device-development) path below.
+Rather than develop constrained devices at scale, device application developers focus on enabling a specific IoT scenario required by their cloud solution. Some developers will also work on constrained devices for their cloud solution. For developers working with resource constrained devices, see the [Embedded Device Development](#embedded-device-development) path.
 
 > [!IMPORTANT]
 > See the [Device SDKs](about-iot-sdks.md#device-sdks) to get started.
@@ -39,35 +41,53 @@ Embedded development targets constrained devices that have limited memory and pr
 
 Embedded devices typically use a real-time operating system (RTOS), or no operating system at all. Embedded devices have full control over their hardware, due to the lack of a general purpose operating system. That fact makes embedded devices a good choice for real-time systems.
 
-The current embedded SDKs target the **C** language. The embedded SDKs provide either no operating system, or Azure RTOS support. They are designed with embedded targets in mind. The design considerations include the need for a minimal footprint, and a non-memory allocating design.
+The current embedded SDKs target the **C** language. The embedded SDKs provide either no operating system, or Azure RTOS support. They're designed with embedded targets in mind. The design considerations include the need for a minimal footprint, and a non-memory allocating design.
 
 If your device is able to run a general-purpose operating system, we recommend following the [Device Application Development](#device-application-development) path. It provides a richer set of development options.
 
 > [!IMPORTANT]
 > See the [Embedded device SDKs](about-iot-sdks.md#embedded-device-sdks) to get started.
 
 ## Choosing your hardware
-Azure IoT devices are the basic building blocks of an IoT solution and are responsible for observing and interacting with their environment. There are many different types of IoT devices, and it's helpful to understand the kinds of devices that exist and how these can impact your development process.
+Azure IoT devices are the basic building blocks of an IoT solution and are responsible for observing and interacting with their environment. There are many different types of IoT devices, and it's helpful to understand the kinds of devices that exist and how they can affect your development process.
 
 For more information on the difference between devices types covered in this article, read [About IoT Device Types](concepts-iot-device-types.md).
 
 ## Choosing an SDK
-As an Azure IoT device developer, you have a diverse set of device SDKs, and Azure service SDKs, to help you build device-enabled cloud applications. The SDKs will streamline your development effort and simplify much of the complexity of connecting and managing devices. 
+As an Azure IoT device developer, you have a diverse set of device SDKs, and Azure service SDKs, to help you build device-enabled cloud applications. The SDKs streamline your development effort and simplify much of the complexity of connecting and managing devices. 
 
-As indicated in the [Device development roles](#device-development-roles) section, there are three kinds of IoT SDKs for device development:
-- Embedded device SDKs (for constrained devices)
-- Device SDKs (for using higher order languages to connect existing devices to IoT applications)
+There are three sets of IoT SDKs for device development:
+- Device SDKs (for using higher order languages to connect existing general purpose devices to IoT applications)
+- Embedded device SDKs (for connecting resource constrained devices to IoT applications)
 - Service SDKs (for building Azure IoT solutions that connect devices to services)
 
 To learn more about choosing an Azure IoT device or service SDK, see [Overview of Azure IoT Device SDKs](about-iot-sdks.md).
 
-## Selecting connection options
-An important step in the development process is choosing the set of options you will use to connect and manage your devices. There are two critical aspects to consider:
-- Choosing an IoT application platform to host your devices. For Azure IoT, this means choosing IoT Hub or IoT Central.
-- Choosing developer tools to help you connect, manage, and monitor devices.
+## Selecting a service
+A key step in the development process is selecting a service to connect your devices to. There are two primary Azure IoT service options for connecting and managing devices: IoT Hub, and IoT Central. 
+
+- [Azure IoT Hub](../iot-hub/about-iot-hub.md). You can use Iot Hub to host IoT applications and connect devices. IoT Hub is a platform-as-a-service (PaaS) application that acts as a central message hub for bi-directional communication between IoT applications and connected devices. It's a platform-as-a-service (PaaS) application that scales to support millions of devices. In general, IoT Hub offers the greatest control and customization over your application design. It also offers the most developer tool options for working with the service, at the cost of some increase in development and management complexity.
+- [Azure IoT Central](../iot-central/core/overview-iot-central.md). IoT Central is designed to simplify the process of working with IoT solutions.  You can use it as a proof of concept to evaluate your IoT solutions. IoT Central is a software-as-a-service (SaaS) application that provides a web UI to simplify the tasks of creating applications, and connecting and managing devices. IoT Central uses IoT Hub to create and manage applications, but keeps most details transparent to the user. 
+
+## Tools to connect and manage devices
+
+After you have selected devices and a device SDK to use, you have several options of developer tools. You can use these tools to connect your device to IoT Hub, and manage them. The following table summarizes common tool options. 
+
+|Tool  |Documentation  |Description  |
+|---------|---------|---------|
+|Azure portal     | [Create an IoT hub with Azure portal](../iot-hub/iot-hub-create-through-portal.md) | Browser-based portal for IoT Hub and devices. Also works with other Azure resources including IoT Central. |
+|Azure IoT Explorer     | [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer#azure-iot-explorer-preview) | Can't create IoT hubs. Connects to an existing IoT hub to manage devices. Often used with CLI or Portal.|
+|Azure CLI     | [Create an IoT hub with CLI](../iot-hub/iot-hub-create-using-cli.md) | Command-line interface for creating and managing IoT applications. |
+|Azure PowerShell     | [Create an IoT hub with PowerShell](../iot-hub/iot-hub-create-using-powershell.md) | PowerShell interface for creating and managing IoT applications |
+|Azure IoT Tools for VS Code  | [Create an IoT hub with Tools for VS Code](../iot-hub/iot-hub-create-use-iot-toolkit.md) | VS Code extension for IoT Hub applications. |
+
+> [!NOTE]
+> In addition to the previously listed tools, you can programmatically create and manage IoT applications by using REST API's, Azure SDKs, or Azure Resource Manager templates. Learn more in the [IoT Hub](../iot-hub/about-iot-hub.md) service documentation.
 
-To learn more about selecting an application platform and tools, see [Overview: Connection options for Azure IoT device developers](concepts-overview-connection-options.md).
 
 ## Next steps
-Select one of the embedded development or application development quickstart series that is most relevant to your development role. These articles demonstrate the basics of creating an Azure IoT application to host devices, using an SDK, connecting a device, and sending telemetry.  
-- [Azure IoT Device Development](index.yml)
+To learn more about device SDKs you can use to connect devices to Azure IoT, see the following article.
+- [Overview of Azure IoT Device SDKs](about-iot-sdks.md)
+
+To get started with hands-on device development, select a device development quickstart that is relevant to the devices you're using. The following article overviews the available quickstarts.  Each quickstart shows how to create an Azure IoT application to host devices, use an SDK, connect a device, and send telemetry.  
+- [Get started with Azure IoT device development](about-getting-started-device-development.md)