Merge pull request #265477 from timlt/combine-sdk

Combine SDK articles content

Author: v-regandowner

articles/iot/.openpublishing.redirection.iot.json

@@ -84,6 +84,11 @@
       "source_path_from_root": "/articles/iot/iot-security-best-practices.md",
       "redirect_url": "/azure/iot/iot-overview-security",
       "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/iot/iot-device-sdks-lifecycle-and-support.md",
+      "redirect_url": "/azure/iot/iot-sdks",
+      "redirect_document_id": false
     }
   ]
 }

articles/iot/TOC.yml

@@ -126,8 +126,6 @@ items:
       items:
       - name: Device and Service SDKs
         href: iot-sdks.md
-      - name: Device SDKs lifecycle and support
-        href: iot-device-sdks-lifecycle-and-support.md
     - name: Azure Certified for IoT device catalog
       href: https://catalog.azureiotsolutions.com/
     - name: Azure IoT Tools for VS Code

articles/iot/iot-device-sdks-lifecycle-and-support.md

@@ -20,7 +20,7 @@ The following tables list the various SDKs you can use to build IoT solutions.
 
 Use the device SDKs to develop code to run on IoT devices that connect to IoT Hub or IoT Central.
 
-To learn more about how to use the device SDKs, see [What is Azure IoT device and application development?](../iot-develop/about-iot-develop.md).
+To learn more about how to use the device SDKs, see [What is Azure IoT device and application development?](../iot-develop/about-iot-develop.md).  
 
 ### Embedded device SDKs
 
@@ -30,6 +30,28 @@ Use the embedded device SDKs to develop code to run on IoT devices that connect
 
 To learn more about when to use the embedded device SDKs, see [C SDK and Embedded C SDK usage scenarios](../iot-develop/concepts-using-c-sdk-and-embedded-c-sdk.md).
 
+### Device SDK lifecycle and support
+
+This section summarizes the Azure IoT Device SDK lifecycle and support policy. For more information, see [Azure SDK Lifecycle and support policy](https://azure.github.io/azure-sdk/policies_support.html).
+
+#### Package lifecycle
+
+Packages are released in the following categories. Each category has a defined support structure.
+
+1. **Beta** - Also known as Preview or Release Candidate. Available for early access and feedback purposes and **is not recommended** for use in production. The preview version support is limited to GitHub issues. Preview releases typically live for less than six months, after which they're either deprecated or released as active.
+
+1. **Active** - Generally available and fully supported, receives new feature updates, as well as bug and security fixes. We recommend that customers use the **latest version** because that version receives fixes and updates.
+
+1. **Deprecated** - Superseded by a more recent release. Deprecation occurs at the same time the new release becomes active. Deprecated releases address the most critical bug fixes and security fixes for another **12 months**.
+
+#### Get support
+
+If you experience problems while using the Azure IoT SDKs, there are several ways to seek support:
+
+* **Reporting bugs** - All customers can report bugs on the issues page for the GitHub repository associated with the relevant SDK. 
+
+* **Microsoft Customer Support team** - Users who have a [support plan](https://azure.microsoft.com/support/plans/) can engage the Microsoft Customer Support team by creating a support ticket directly from the [Azure portal](https://portal.azure.com/signin/index/?feature.settingsportalinstance=mpac).
+
 ## IoT Hub service SDKs
 
 [!INCLUDE [iot-hub-sdks-service](../../includes/iot-hub-sdks-service.md)]