Merge pull request #296473 from bishal41/manage-secrets

Move secrets related content to Manage Secret page

Author: prmerger-automator[bot]

articles/iot-operations/secure-iot-ops/howto-manage-secrets.md

@@ -49,5 +49,7 @@ You can use **Manage secrets** for asset endpoints and data flow endpoints to ma
 
 You can delete synced secrets as well in manage secrets. When you delete a synced secret, it only deletes the synced secret from the edge, and doesn't delete the contained secret reference from key vault. 
 
-> [!NOTE]
-> Before deleting a synced secret, make sure that all references to the secret from Azure IoT Operations components are removed.
+> [!WARNING]
+> Directly editing **SecretProviderClass** and **SecretSync** custom resources in your Kubernetes cluster can break the secrets flow in Azure IoT Operations. For any operations related to secrets, use the operations experience UI.
+>
+> Before deleting a synced secret, make sure that all references to the secret from Azure IoT Operations components are removed.

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

@@ -17,8 +17,6 @@ This article lists the known issues for Azure IoT Operations.
 
 - If you prefer to have no updates made to your cluster without giving explicit consent, you should disable Arc updates when you enable the cluster. This is due to the fact that some system extensions are automatically updated by the Arc agent. To disable updates, include the `--disable-auto-upgrade` flag as part of the `az connectedk8s connect` command.
 
-- Directly editing **SecretProviderClass** and **SecretSync** custom resources in your Kubernetes cluster can break the secrets flow in Azure IoT Operations. For any operations related to secrets, use the operations experience UI.
-
 - During and after deploying Azure IoT Operations, you might see warnings about `Unable to retrieve some image pull secrets (regcred)` in the logs and Kubernetes events. These warnings are expected and don't affect the deployment and use of Azure IoT Operations.
 
 - If your deployment fails with the message `Error occurred while creating custom resources needed by system extensions`, you have encountered a known sporadic failure that will be fixed in a future release. As a workaround, use the [az iot ops delete](/cli/azure/iot/ops#az-iot-ops-delete) command with the `--include-deps` flag to delete Azure IoT Operations from your cluster. When Azure IoT Operations and its dependencies are deleted from your cluster, retry the deployment.