Merge pull request #296640 from bishal41/brokercustomization

AIO - Broker customization (add important note)

Author: prmerger-automator[bot]

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

@@ -191,7 +191,7 @@ To customize the default Broker during deployment:
 
 # [Portal](#tab/portal)
 
-When you follow the guide to [deploy IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md), in the **Configuration** section, look under **MQTT broker configuration**. Here, you can [customize cardinality and memory profile settings](./howto-configure-availability-scale.md). To configure other settings, including disk-backed message buffer and advanced MQTT client options, use the Azure CLI.
+When you follow the guide to [deploy IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md), in the **Configuration** section, look under **MQTT broker configuration**. Here, you can [customize cardinality and memory profile settings](./howto-configure-availability-scale.md). To configure other settings, including disk-backed message buffer, and advanced MQTT client options, use the Azure CLI.
 
 # [Azure CLI](#tab/azure-cli)
 
@@ -207,6 +207,9 @@ Use the Azure portal or the Azure CLI to customize the default Broker resource.
 
 ---
 
+> [!IMPORTANT] 
+> You can't update the broker resource after the initial deployment. Configuration changes to cardinality, memory profile, or disk buffer aren't allowed post-deployment.
+
 ### View default Broker settings
 
 To view the settings for the default Broker:

articles/iot-operations/troubleshoot/known-issues.md

@@ -42,8 +42,6 @@ This article lists the known issues for Azure IoT Operations.
 
 - MQTT broker resources created in your cluster using Kubernetes aren't visible Azure portal. This is expected because [managing Azure IoT Operations components using Kubernetes is in preview](../deploy-iot-ops/howto-manage-update-uninstall.md#preview-manage-components-using-kubernetes-deployment-manifests), and synchronizing resources from the edge to the cloud isn't currently supported.
 
-- You can't update the Broker resource after the initial deployment. You can't make configuration changes to cardinality, memory profile, or disk buffer.
-
   As a workaround, when deploying Azure IoT Operations with the [az iot ops init](/cli/azure/iot/ops#az-iot-ops-init) command, you can include the `--broker-config-file` parameter with a JSON configuration file for the MQTT broker. For more information, see [Advanced MQTT broker config](https://github.com/Azure/azure-iot-ops-cli-extension/wiki/Advanced-Mqtt-Broker-Config) and [Configure core MQTT broker settings](../manage-mqtt-broker/howto-configure-availability-scale.md).
 
 - If a Broker only has one backend replica (`backendChain.redundancyFactor` is set to 1) upgrading Azure IoT Operations might fail. Only upgrade Azure IoT Operations if the Broker has more than one backend replica.