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-deploy-iot-operations.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
147
147
```
148
148
149
149
> [!IMPORTANT]
150
-
> For preview releases, you need to append the `--allow-preview` flag to the `az extension add` command to install the [preview version](./howto-upgrade.md#upgrade-to-preview-version) of the Azure IoT Operations CLI extension.
150
+
> For [preview releases](./howto-upgrade.md#upgrade-to-preview-version), you need to append the `--allow-preview` flag to the `az extension add` command to install the preview version of the Azure IoT Operations CLI extension.
151
151
>
152
152
> ```azurecli
153
153
> az extension add --upgrade --name azure-iot-ops --allow-preview
@@ -170,6 +170,9 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
170
170
1. In the left menu, select **Namespaces**.
171
171
1. Then select **+ Create** to create a new namespace. Make sure to use the same resource group as your Arc-enabled Kubernetes cluster.
172
172
173
+
> [!NOTE]
174
+
> Namespace resources are available from [2507 preview release](https://github.com/Azure/azure-iot-operations/releases/tag/v1.2.35). If you're using an earlier release version, namespaces aren't available and you can skip this step.
175
+
173
176
1. To prepare the cluster for Azure IoT Operations deployment, copy and run the provided [az iot ops init](/cli/azure/iot/ops#az-iot-ops-init) command.
174
177
175
178
> [!TIP]
@@ -192,7 +195,7 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
192
195
```
193
196
194
197
> [!NOTE]
195
-
> The `--feature` configuration parameter isn't available in 2507 preview release.
198
+
> The `--feature` configuration parameter is only available in the [latest GA version](https://github.com/Azure/azure-iot-operations/releases/tag/v1.1.59). If you're using the [2507 preview release](https://github.com/Azure/azure-iot-operations/releases/tag/v1.2.35), this parameter isn't available.
196
199
197
200
* If you followed the optional prerequisites to set up your own certificate authority issuer, add the `--trust-settings` parameters to the `create` command:
Copy file name to clipboardExpand all lines: articles/iot-operations/deploy-iot-ops/howto-deploy-iot-test-operations.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,7 +134,7 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
134
134
135
135
136
136
> [!IMPORTANT]
137
-
> For preview releases, you need to append the `--allow-preview` flag to the `az extension add` command to install the [preview version](./howto-upgrade.md#upgrade-to-preview-version) of the Azure IoT Operations CLI extension.
137
+
> For [preview releases](./howto-upgrade.md#upgrade-to-preview-version), you need to append the `--allow-preview` flag to the `az extension add` command to install the preview version of the Azure IoT Operations CLI extension.
138
138
>
139
139
> ```azurecli
140
140
> az extension add --upgrade --name azure-iot-ops --allow-preview
@@ -153,6 +153,9 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
153
153
1. In the search box, type and select **Azure Device Registry**.
154
154
1. In the left menu, select **Namespaces**.
155
155
1. Then select **+ Create** to create a new namespace. Make sure to use the same resource group as your Arc-enabled Kubernetes cluster.
156
+
157
+
> [!NOTE]
158
+
> Namespace resources are available from [2507 preview release](https://github.com/Azure/azure-iot-operations/releases/tag/v1.2.35). If you're using an earlier release version, namespaces aren't available and you can skip this step.
156
159
157
160
1. Prepare the cluster for Azure IoT Operations deployment. Copy and run the provided [az iot ops init](/cli/azure/iot/ops#az-iot-ops-init) command.
158
161
@@ -176,7 +179,7 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
176
179
```
177
180
178
181
> [!NOTE]
179
-
> The `--feature` configuration parameter isn't available in 2507 preview release.
182
+
> The `--feature` configuration parameter is only available in the [latest GA version](https://github.com/Azure/azure-iot-operations/releases/tag/v1.1.59). If you're using the [2507 preview release](https://github.com/Azure/azure-iot-operations/releases/tag/v1.2.35), this parameter isn't available.
180
183
181
184
1. Once all of the Azure CLI commands complete successfully, you can close the **Install Azure IoT Operations** wizard.
Copy file name to clipboardExpand all lines: articles/iot-operations/includes/supported-versions.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,15 +3,16 @@ title: include file
3
3
description: include file with details of currently supported versions
4
4
author: dominicbetts
5
5
ms.topic: include
6
-
ms.date: 06/16/2025
6
+
ms.date: 07/30/2025
7
7
ms.author: dobett
8
8
---
9
9
10
10
Microsoft always supports three generally available (GA) versions of Azure IoT Operations at any one time: the latest version, and the two previous minor versions.
11
11
12
12
Currently, there are only two minor versions available. [Azure support](https://azure.microsoft.com/support/plans) is currently available for the following versions:
13
13
14
-
-[1.1.x](https://github.com/Azure/azure-iot-operations/releases/tag/v1.1.19) (latest GA version)
0 commit comments