You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-hub-device-update/support.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,27 +46,27 @@ The systems listed in the following tables are supported by Microsoft, either ge
46
46
47
47
Device Update for IoT Hub release assets and release notes are available on the [Device Update Release](https://github.com/Azure/iot-hub-device-update/releases) page. Support for the APIs, PnP Models, and device update reference agents is covered in the table.
48
48
49
-
Device Update for IoT Hub 1.0 is the first major release and will continue to receive security fixes and fixes to regressions.
49
+
Device Update for IoT Hub 1.0 is the first major release and continues to receive security fixes and fixes to regressions.
50
50
51
51
Device Update (DU) agents use IoT Plug and Play models to send and receive properties and messages from the DU service. Each DU agent requires specific models to be used. Learn more about how device update uses these models and how they can be extended.
52
52
53
53
Newer REST Service API versions support older agents unless specified. Device Update for IoT Hub portal experience uses the latest APIs and have the same support as the API version.
54
54
55
55
| Release notes and assets | deviceupdate-agent | Upgrade Supported from agent version | DU PnP Models supported | API Versions|
The latest API version, 2022-10-01 will be supported until the next stable release and the latest agent version, 1.x.x, will receive bug fixes and security fixes until the next stable release.
63
63
64
64
> [!NOTE]
65
-
> Users, that have extended from the reference agent and customized the agent, are responsible for ensuring the bug fixes and security fixes are incorporated. You will also need to ensure the agent is built and configured correctly as defined by the service to connect service, perform updates, and manage devices from the IoT hub.
65
+
> Users that have extended from the reference agent and customized the agent are responsible for ensuring the bug fixes and security fixes are incorporated. You will also need to ensure the agent is built and configured correctly as defined by the service to connect service, perform updates, and manage devices from the IoT hub.
66
66
67
67
> [!IMPORTANT]
68
68
> Every Microsoft product has a lifecycle. The lifecycle begins when a product is released and ends when it's no longer supported. Knowing key dates in this lifecycle helps you make informed decisions about when to upgrade or make other changes to your software.
69
-
> For Device Update for IoT Hub, no stable API or agent version will be deprecated without a replacing version. Deprecated stable versions will be available for no less than 3 years after deprecation is announced to allow users to migrate to in-support agent and API versions.
70
-
> Preview releases (Pre-releases) agents and APIs are not serviced after the release of the stable version. Preview versions are released to test new functionality, gather feedback, and discover and fix issues. Previews are available under Supplemental Terms of Use, and aren't recommended for production workloads.
71
-
> 0.7.0 (Pre-release) is not supported by the latest service and API versions.
69
+
> For Device Update for IoT Hub, no stable API or agent version will be deprecated without a replacing version. Deprecated stable versions will be available for no less than three years after deprecation is announced to allow users to migrate to in-support agent and API versions.
70
+
> Preview releases (Prereleases) agents and APIs are not serviced after the release of the stable version. Preview versions are released to test new functionality, gather feedback, and discover and fix issues. Previews are available under Supplemental Terms of Use, and aren't recommended for production workloads.
71
+
> 0.7.0 (Prerelease) is not supported by the latest service and API versions.
72
72
> With the latest stable release, we recommend that all current customers running 0.x.x upgrade their devices to 1.0.x to receive ongoing support.
0 commit comments