Remove preview messages

Author: dominicbetts

articles/iot-operations/connect-to-cloud/howto-configure-adlsv2-endpoint.md

@@ -372,7 +372,7 @@ If you select **Create new**, enter the following settings:
 | Set activation date | If turned on, the date when the secret becomes active. |
 | Set expiration date | If turned on, the date when the secret expires. |
 
-To learn more about secrets, see [Create and manage secrets in Azure IoT Operations Preview](../secure-iot-ops/howto-manage-secrets.md).
+To learn more about secrets, see [Create and manage secrets in Azure IoT Operations](../secure-iot-ops/howto-manage-secrets.md).
 
 # [Bicep](#tab/bicep)
 

articles/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint.md

@@ -172,7 +172,7 @@ After you select **Add reference**, if you select **Create new**, enter the foll
 | Set activation date | If turned on, the date when the secret becomes active. |
 | Set expiration date | If turned on, the date when the secret expires. |
 
-To learn more about secrets, see [Create and manage secrets in Azure IoT Operations Preview](../secure-iot-ops/howto-manage-secrets.md).
+To learn more about secrets, see [Create and manage secrets in Azure IoT Operations](../secure-iot-ops/howto-manage-secrets.md).
 
 # [Bicep](#tab/bicep)
 

articles/iot-operations/connect-to-cloud/howto-configure-mqtt-endpoint.md

@@ -615,7 +615,7 @@ If you select **Create new**, enter the following settings:
 | Set activation date | If turned on, the date when the secret becomes active. |
 | Set expiration date | If turned on, the date when the secret expires. |
 
-To learn more about secrets, see [Create and manage secrets in Azure IoT Operations Preview](../secure-iot-ops/howto-manage-secrets.md).
+To learn more about secrets, see [Create and manage secrets in Azure IoT Operations](../secure-iot-ops/howto-manage-secrets.md).
 
 # [Bicep](#tab/bicep)
 

articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md

@@ -17,7 +17,7 @@ This article provides instructions for enabling secure settings if you didn't do
 
 ## Prerequisites
 
-* An Azure IoT Operations instance deployed with test settings. For example, follow the instructions in [Quickstart: Run Azure IoT Operations Preview in GitHub Codespaces](../get-started-end-to-end-sample/quickstart-deploy.md).
+* An Azure IoT Operations instance deployed with test settings. For example, follow the instructions in [Quickstart: Run Azure IoT Operations in GitHub Codespaces](../get-started-end-to-end-sample/quickstart-deploy.md).
 
 * Azure CLI installed on your development machine. This scenario requires Azure CLI version 2.64.0 or later. Use `az --version` to check your version and `az upgrade` to update, if necessary. For more information, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
 
@@ -154,7 +154,7 @@ To set up secrets management:
 
     ---
 
-Now that secret synchronization setup is complete, you can refer to [Manage secrets for your Azure IoT Operations Preview deployment](./howto-manage-secrets.md) to learn how to use secrets with Azure IoT Operations.
+Now that secret synchronization setup is complete, you can refer to [Manage secrets for your Azure IoT Operations deployment](./howto-manage-secrets.md) to learn how to use secrets with Azure IoT Operations.
 
 ## Set up a user-assigned managed identity for cloud connections
 

articles/iot-operations/discover-manage-assets/howto-use-media-connector.md

@@ -22,7 +22,7 @@ The media connector:
 
 ## Prerequisites
 
-A deployed instance of Azure IoT Operations. If you don't already have an instance, see [Quickstart: Run Azure IoT Operations Preview in GitHub Codespaces with K3s](../get-started-end-to-end-sample/quickstart-deploy.md).
+A deployed instance of Azure IoT Operations. If you don't already have an instance, see [Quickstart: Run Azure IoT Operations in GitHub Codespaces with K3s](../get-started-end-to-end-sample/quickstart-deploy.md).
 
 ## Deploy the media server
 

articles/iot-operations/discover-manage-assets/howto-use-onvif-connector.md

@@ -12,11 +12,11 @@ ms.date: 11/06/2024
 
 # Configure the connector for ONVIF (preview)
 
-In Azure IoT Operations, the connector for ONVIF (preview) enables you to control an ONVIF compliant camera that's connected to your Azure IoT Operations Preview cluster. This article explains how to configure and use the connector for ONVIF to perform tasks such as reading and writing properties to control a camera or discovering the media streams a camera supports.
+In Azure IoT Operations, the connector for ONVIF (preview) enables you to control an ONVIF compliant camera that's connected to your Azure IoT Operations cluster. This article explains how to configure and use the connector for ONVIF to perform tasks such as reading and writing properties to control a camera or discovering the media streams a camera supports.
 
 ## Prerequisites
 
-A deployed instance of Azure IoT Operations. If you don't already have an instance, see [Quickstart: Run Azure IoT Operations Preview in GitHub Codespaces with K3s](../get-started-end-to-end-sample/quickstart-deploy.md).
+A deployed instance of Azure IoT Operations. If you don't already have an instance, see [Quickstart: Run Azure IoT Operations in GitHub Codespaces with K3s](../get-started-end-to-end-sample/quickstart-deploy.md).
 
 An ONVIF compliant camera connected to your Azure IoT Operations cluster. If you don't have a camera, you can use a simulator such as the [ONVIF RTSP simulator](https://arcjumpstart.com/simulate_an_onvif_camera_with_rtsp).
 

articles/iot-operations/manage-mqtt-broker/howto-configure-brokerlistener.md

@@ -380,7 +380,7 @@ To enable TLS with automatic certificate management, specify the TLS settings on
 
 ### Verify cert-manager installation
 
-With automatic certificate management, you use cert-manager to manage the TLS server certificate. By default, cert-manager is installed alongside Azure IoT Operations Preview in the `cert-manager` namespace already. Verify the installation before proceeding.
+With automatic certificate management, you use cert-manager to manage the TLS server certificate. By default, cert-manager is installed alongside Azure IoT Operations in the `cert-manager` namespace already. Verify the installation before proceeding.
 
 1. Use `kubectl` to check for the pods matching the cert-manager app labels.
 

articles/iot-operations/manage-mqtt-broker/overview-broker.md

@@ -17,7 +17,7 @@ ms.service: azure-iot-operations
 
 [!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
 
-Azure IoT Operations features an enterprise-grade, standards-compliant MQTT broker that is scalable, highly available, and Kubernetes-native. It provides the messaging plane for Azure IoT Operations Preview, enables bi-directional edge/cloud communication and powers [event-driven applications](/azure/architecture/guide/architecture-styles/event-driven) at the edge.
+Azure IoT Operations features an enterprise-grade, standards-compliant MQTT broker that is scalable, highly available, and Kubernetes-native. It provides the messaging plane for Azure IoT Operations, enables bi-directional edge/cloud communication and powers [event-driven applications](/azure/architecture/guide/architecture-styles/event-driven) at the edge.
 
 ## MQTT compliance
 

docfx.json

@@ -1183,8 +1183,8 @@
         "articles/iot-central/**/*yml": "Azure IoT Central",
         "articles/iot-dps/**/*.md": "Azure IoT Hub Device Provisioning Service",
         "articles/iot-dps/**/*.yml": "Azure IoT Hub Device Provisioning Service",
-        "articles/iot-operations/**/*.md": "Azure IoT Operations Preview",
-        "articles/iot-operations/**/*.yml": "Azure IoT Operations Preview",
+        "articles/iot-operations/**/*.md": "Azure IoT Operations",
+        "articles/iot-operations/**/*.yml": "Azure IoT Operations",
         "articles/iot/**/*.md": "Azure IoT",
         "articles/iot/**/*yml": "Azure IoT",
         "articles/jenkins/**/*.yml": "Jenkins",