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-operations/deploy-iot-ops/howto-upgrade.md
+24-11Lines changed: 24 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,14 @@ author: dominicbetts
5
5
ms.author: dobett
6
6
ms.topic: how-to
7
7
ms.custom: devx-track-azurecli
8
-
ms.date: 03/03/2025
8
+
ms.date: 07/18/2025
9
9
10
10
#CustomerIntent: As an IT professional, I want to manage Azure IoT Operations instances.
11
11
---
12
12
13
13
# Upgrade to a new version
14
14
15
-
Upgrade an Azure IoT Operations deployment to a newer version. Azure IoT Operations supports upgrade from version 1.0.x onwards. There's no support for upgrading from any preview version of Azure IoT Operations to any generally available (GA) version.
15
+
Learn how to upgrade an Azure IoT Operations deployment to a newer version. There's no support for upgrading from any preview version of Azure IoT Operations to any generally available (GA) version.
16
16
17
17
## Prerequisites
18
18
@@ -21,9 +21,14 @@ Upgrade an Azure IoT Operations deployment to a newer version. Azure IoT Operati
21
21
22
22
## Understand upgrade support
23
23
24
+
Azure IoT Operations release versions can be preview or generally available (GA), you can find the latest version in the [Azure IoT Operations versions](https://aka.ms/aio-versions) document. The Azure IoT Operations CLI extension version is tied to the Azure IoT Operations version, so you need to ensure that you have the correct CLI extension version installed to perform an upgrade.
25
+
26
+
Azure IoT Operations supports the following upgrade scenarios:
27
+
24
28
- You can upgrade an existing Azure IoT Operations instance to any patch of the same minor version, or to the next minor version.
25
-
- Azure IoT Operations doesn't support downgrading between versions. To move to an older version, uninstall Azure IoT Operations and reinstall the desired version.
26
-
- You can't upgrade from a preview installation to a GA version, or from a GA version to a preview version, it has to be a fresh deployment. If this is the case, you need to [uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) and reinstall the new version. For more information, see [Upgrade to preview version](howto-upgrade.md#upgrade-to-preview-version).
29
+
- You can't downgrade between versions. To move to an older version, [uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) and reinstall the desired version.
30
+
- You can't upgrade from any preview version to a GA version. You need to [uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) and reinstall the new version.
31
+
- You can't upgrade from any GA version to a preview version. For more information on how to install a preview version, see [Upgrade to preview version](howto-upgrade.md#upgrade-to-preview-version).
27
32
28
33
> [!NOTE]
29
34
> Azure IoT Operations doesn't support live upgrades. Please expect some downtime during the upgrade process.
@@ -96,22 +101,30 @@ Use the following steps to upgrade your deployment to the latest version:
96
101
97
102
## Upgrade to preview version
98
103
99
-
Sometimes the latest version of Azure IoT Operations is in preview. During preview releases, version upgrade is blocked, so you need to uninstall Azure IoT Operations and reinstall the preview version.
104
+
Sometimes the latest version of Azure IoT Operations is in preview. Check the [Azure IoT Operations versions](https://aka.ms/aio-versions) document to see if the latest version is in preview. If it is, you can only install the preview version using the Azure CLI.
105
+
106
+
During preview releases, version upgrade is blocked, and you need to uninstall Azure IoT Operations and reinstall the preview version.
100
107
101
108
1. If you have an existing Azure IoT Operations instance, you need to [Uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) to do a new deployment.
102
109
1. Add the latest version of the Azure IoT Operations CLI extension with the `--allow-preview` flag.
103
110
104
111
```azurecli
105
112
az extension add --upgrade --name azure-iot-ops --allow-preview
106
113
```
107
-
> [!NOTE]
108
-
> If you don't want to install a preview version, you can upgrade your deployment to a specific version of Azure IoT Operations by specifying the related CLI extension version. Refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want and run the following command:
109
-
>
110
-
> ```azurecli
111
-
> az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
112
-
> ```
113
114
115
+
1. During preview releases, you can upgrade your deployment to a specific version of Azure IoT Operations by specifying the related CLI extension version. Refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want and run the following command:
114
116
117
+
```azurecli
118
+
az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
119
+
```
120
+
121
+
> [!NOTE]
122
+
> In preview releases, the `az iot ops upgrade` command doesn't work for upgrading to a preview version, but it works for configuring the Azure IoT Operations for observability. Add the following parameters to the `upgrade` command:
123
+
>
124
+
> | Parameter | Value | Description |
125
+
> | --------- | ----- | ----------- |
126
+
> |`--ops-config`|`observability.metrics.openTelemetryCollectorAddress=<FULLNAMEOVERRIDE>.azure-iot-operations.svc.cluster.local:<GRPC_ENDPOINT>`| Provide the OpenTelemetry (OTel) collector address you configured in the otel-collector-values.yaml file.<br><br>The sample values used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) are **fullnameOverride=aio-otel-collector** and **grpc.endpoint=4317**. |
127
+
> |`--ops-config`|`observability.metrics.exportInternalSeconds=<CHECK_INTERVAL>`| Provide the **check_interval** value you configured in the otel-collector-values.yaml file.<br><br>The sample value used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) is **check_interval=60**. |
0 commit comments