Merge pull request #231357 from yossi-y/main

Remove irrelevant error messages

Author: prmerger-automator[bot]

articles/azure-monitor/logs/customer-managed-keys.md

@@ -462,18 +462,6 @@ Deleting a linked workspace is permitted while linked to cluster. If you decide
 
 - Error messages
 
-  **Cluster Create**
-  -  400 — Cluster name is not valid. Cluster name can contain characters a-z, A-Z, 0-9 and length of 3-63.
-  -  400 — The body of the request is null or in bad format.
-  -  400 — "SKU" name is invalid. Set "SKU" name to capacityReservation.
-  -  400 — Capacity was provided but "SKU" is not capacityReservation. Set "SKU" name to capacityReservation.
-  -  400 — Missing Capacity in "SKU". Set Capacity value to 500, 1000, 2000 or 5000 GB/day.
-  -  400 — Capacity is locked for 30 days. Decreasing capacity is permitted 30 days after update.
-  -  400 — No "SKU" was set. Set the "SKU" name to capacityReservation and Capacity value to 500, 1000, 2000 or 5000 GB/day.
-  -  400 — Identity is null or empty. Set Identity with systemAssigned type.
-  -  400 — KeyVaultProperties are set on creation. Update KeyVaultProperties after cluster creation.
-  -  400 — Operation cannot be executed now. Async operation is in a state other than succeeded. Cluster must complete its operation before any update operation is performed.
-
   **Cluster Update**
   -  400 — Cluster is in deleting state. Async operation is in progress. Cluster must complete its operation before any update operation is performed.
   -  400 — KeyVaultProperties is not empty but has a bad format. See [key identifier update](#update-cluster-with-key-identifier-details).
@@ -483,19 +471,8 @@ Deleting a linked workspace is permitted while linked to cluster. If you decide
   -  400 — Cluster is in deleting state. Wait for the Async operation to complete and try again.
 
   **Cluster Get**
-    -  404 — Cluster not found, the cluster may have been deleted. If you try to create a cluster with that name and get conflict, the cluster is in soft-delete for 14 days. You can contact support to recover it, or use another name to create a new cluster. 
-
-  **Cluster Delete**
-    -  409 — Can't delete a cluster while in provisioning state. Wait for the Async operation to complete and try again.
-
-  **Workspace link**
-  -  404 — Workspace not found. The workspace you specified doesn’t exist or was deleted.
-  -  409 — Workspace link or unlink operation in process.
-  -  400 — Cluster not found, the cluster you specified doesn’t exist or was deleted. If you try to create a cluster with that name and get conflict, the cluster is in soft-delete for 14 days. You can contact support to recover it.
+  -  404--Cluster not found, the cluster might have been deleted. If you try to create a cluster with that name and get conflict, the cluster is in deletion process. 
 
-  **Workspace unlink**
-  -  404 — Workspace not found. The workspace you specified doesn’t exist or was deleted.
-  -  409 — Workspace link or unlink operation in process.
 ## Next steps
 
 - Learn about [Log Analytics dedicated cluster billing](cost-logs.md#dedicated-clusters)