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
+46-8Lines changed: 46 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,24 +10,62 @@ ms.date: 11/11/2024
10
10
#CustomerIntent: As an OT professional, I want to manage Azure IoT Operations instances.
11
11
---
12
12
13
-
# Upgrade or rollback between versions
13
+
# Upgrade or downgrade between versions
14
14
15
15
Upgrade an Azure IoT Operations instance to a newer version or rollback to a previous version. Azure IoT Operations supports upgrade and rollback from version 1.0.x onwards. There is no support for upgrading from any preview version of Azure IoT Operations to any generally available (GA) version.
16
16
17
-
>[!NOTE]
18
-
>Currently, Azure IoT Operations has only one generally available version. Upgrade and rollback will be available once there are additional versions to upgrade or rollback between.
17
+
## Prerequisites
19
18
20
19
## Understand upgrade support
21
20
22
-
Upgrade and rollback are supported between N+2 or N-2 minor versions of Azure IoT Operations, or between any patch versions of the same minor version. The following table provides examples:
21
+
Upgrade and rollback are supported between N+3 or N-3 minor versions of Azure IoT Operations, or between any patch versions of the same minor version. The following table provides examples:
23
22
24
-
|Current version| Upgrade range | Rollback range |
Azure IoT Operations supports upgrading instances to new GA versions as they're released.
32
31
33
32
You can't upgrade from a preview installation to a GA version. To move to version 1.0.x, [uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) and reinstall the new version.
33
+
34
+
### [Azure portal](#tab/portal)
35
+
36
+
If your instance is eligible for an upgrade, the Azure portal displays an **Upgrade** option.
37
+
38
+
1. In the [Azure portal](https://portal.azure.com), navigate to your Azure IoT Operations instance.
39
+
1. Select **Upgrade** on the **Overview** page of your instance.
40
+
41
+
:::image type="content" source="./media/howto-upgrade/instance-upgrade.png" alt-text="Screenshot that shows the upgrade button enabled in the Azure portal.":::
42
+
43
+
1. The portal presents the Azure CLI command to upgrade your instance, prepopulated with your subscription, resource group, and instance details. Select the copy icon next to the CLI command.
44
+
45
+
1. Run the copied `az iot ops upgrade` command in any environment where you have the Azure CLI installed.
46
+
47
+
1. After the upgrade command completes successfully, refresh your instance to see the changes.
48
+
49
+
The **Version** value displayed on your instance's overview page reflects the version of the Azure IoT Operations instance. However, you may be prompted to upgrade if a required Arc extension has an available upgrade. You can tell that an upgrade was successful if the **Upgrade** option disappears from the instance overview page, even if it doesn't look like anything changed. You can check the versions of the Arc extensions for your Azure IoT Operation deployment on the **Extensions** page of your Arc-enabled cluster in the Azure portal.
50
+
51
+
### [Azure CLI](#tab/cli)
52
+
53
+
Use the [az iot ops upgrade](/cli/azure/iot/ops#az-iot-ops-upgrade) command to upgrade an existing Azure IoT Operations deployment to a newer version.
54
+
55
+
The upgrade command evaluates the entire Azure IoT Operations deployment for available updates, including the arc extensions that are installed in the `az iot ops init` command as well as the Azure IoT Operations instance.
56
+
57
+
---
58
+
59
+
## Downgrade
60
+
61
+
62
+
63
+
### [Azure portal](#tab/portal)
64
+
65
+
The Azure portal doesn't offer a version downgrade option. Instead, use the Azure CLI.
66
+
67
+
### [Azure CLI](#tab/cli)
68
+
69
+
Use the [az iot ops upgrade](/cli/azure/iot/ops#az-iot-ops-upgrade) command to roll back an existing Azure IoT Operations instance to a previous version.
Copy file name to clipboardExpand all lines: articles/iot-operations/get-started-end-to-end-sample/quickstart-deploy.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: kgremban
5
5
ms.author: kgremban
6
6
ms.topic: quickstart
7
7
ms.custom: ignite-2023, devx-track-azurecli
8
-
ms.date: 10/22/2024
8
+
ms.date: 01/30/2025
9
9
10
10
#CustomerIntent: As a < type of user >, I want < what? > so that < why? >.
11
11
---
@@ -166,8 +166,8 @@ Run the following CLI commands in your Codespaces terminal.
166
166
| Placeholder | Value |
167
167
| ----------- | ----- |
168
168
| <STORAGE_ACCOUNT_NAME> | A name for your storage account. Storage account names must be between 3 and 24 characters in length and only contain numbers and lowercase letters. |
169
-
| <SCHEMA_REGISTRY_NAME> | A name for your schema registry. |
170
-
| <SCHEMA_REGISTRY_NAMESPACE> | A name for your schema registry namespace. The namespace uniquely identifies a schema registry within a tenant. |
169
+
| <SCHEMA_REGISTRY_NAME> | A name for your schema registry. Schema registry names can only contain numbers, lowercase letters, and hyphens. |
170
+
| <SCHEMA_REGISTRY_NAMESPACE> | A name for your schema registry namespace. The namespace uniquely identifies a schema registry within a tenant. Schema registry namespace names can only contain numbers, lowercase letters, and hyphens. |
0 commit comments