Changes note to warning

bishal41 · bishal41 · commit a14b732f2e7d · 2025-03-18T11:35:27.000-07:00
diff --git a/articles/iot-operations/secure-iot-ops/howto-manage-secrets.md b/articles/iot-operations/secure-iot-ops/howto-manage-secrets.md
@@ -49,7 +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]
+> [!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.
+> Before deleting a synced secret, make sure that all references to the secret from Azure IoT Operations components are removed.

Original file line number	Diff line number	Diff line change
`@@ -49,7 +49,7 @@ You can use Manage secrets for asset endpoints and data flow endpoints to ma`
`49`	`49`
`50`	`50`	`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.`
`51`	`51`
`52`		`-> [!NOTE]`
	`52`	`+> [!WARNING]`
`53`	`53`	`> 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.`
`54`	`54`	`>`
`55`		`-> Before deleting a synced secret, make sure that all references to the secret from Azure IoT Operations components are removed.`
	`55`	`+> Before deleting a synced secret, make sure that all references to the secret from Azure IoT Operations components are removed.`