Moved the relevant CREATE related TSGs into the error code section

Author: ReginaLin24

support/azure/azure-kubernetes/error-codes/aksoperationpreempted-error.md

@@ -0,0 +1,57 @@
+---
+title: AKSOperationPreempted error when performing a new operation
+description: Helps resolve the AKSOperationPreempted or AKSOperationPreemptedByDelete error when you perform a new operation on an Azure Kubernetes Service (AKS) cluster.
+ms.date: 10/28/2024
+ms.reviewer: rissing, chiragpa, erbookbi, jopalhei, dorinalecu, v-leedennis, v-weizhu
+ms.service: azure-kubernetes-service
+#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the OperationPreempted error code so that I can successfully perform a new operation an Azure Kubernetes Service (AKS) cluster.
+ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
+---
+# AKSOperationPreempted or AKSOperationPreemptedByDelete error when performing a new operation
+
+This article discusses how to identify and resolve the `AKSOperationPreempted` or `AKSOperationPreemptedByDelete` error that might occur when you try to perform a new operation but it has been preempted by another operation on a Microsoft Azure Kubernetes Service (AKS) cluster.
+
+## Symptoms
+
+When you try to perform a new operation on an AKS cluster, you receive one of the following error messages:
+
+- > Code: "AKSOperationPreempted"
+  > 
+  > Message: "This operation has been preempted by another operation with ID \<operation ID\>" 
+  
+  This message indicates that the operation has been preempted by another operation, and the GUID for the new operation is given in the error message.
+
+- > Code: "AKSOperationPreemptedByDelete"
+  > 
+  > Message: "This operation has been preempted by Deleting operation."
+  
+  This message indicates that the operation has been preempted by a delete operation.
+  
+## Cause
+
+This error usually occurs when an in-progress operation is interrupted by a subsequent operation that was issued before the in-progress operation is finished. The error will indicate the subsequent operation, which can be a delete or any other operation.
+
+## Solution
+
+To resolve this issue, use one of the following methods. Once there are no operations running, you can try to run your operation again.
+
+- Wait for the previous operation to complete.
+
+  You can check the status of the operation using the ID given in the error message with the follwing command:
+
+  ```azurecli-interactive
+  az aks operation show \
+      --resource-group myResourceGroup \
+      --name myCluster \
+      --operation-id "<operation-id>"
+  ```
+
+- Run an `abort` command to stop the previous operation.
+
+  For more information about how to abort an operation, see [Terminate a long running operation on an Azure Kubernetes Service (AKS) cluster](/azure/aks/manage-abort-operations). 
+
+## More information
+
+[General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/error-codes/invalidparameter-error.md

@@ -0,0 +1,82 @@
+---
+title: Troubleshoot the InvalidParameter error
+description: Learn how to troubleshoot the InvalidParameter error when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
+ms.date: 11/19/2024
+editor: v-gsitser
+ms.reviewer: rissing, chiragpa, erbookbi, jaewonpark, v-leedennis
+ms.service: azure-kubernetes-service
+#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the InvalidParameter error so that I can successfully create and deploy an AKS cluster.
+ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
+---
+# Troubleshoot the InvalidParameter error
+
+This article discusses how to identify and resolve the `InvalidParameter` error that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
+
+## Prerequisites
+
+- [Azure CLI](/cli/azure/install-azure-cli), version 2.0.81 or a later version. If Azure CLI is already installed, you can find the version number by running `az --version`.
+
+## Symptoms
+
+When you create an AKS cluster, the provided configurations are usually validated before the cluster is created. However, on rare occasions, a parameter passes validation before the AKS cluster is created but causes errors when the resources for the cluster are created. Errors that are related to invalid parameters might resemble the following examples:
+
+- Scenario: The selected VM size is not available
+
+    ```
+    Code="InvalidParameter"
+        
+    Message="**The requested VM size Standard_D4s_v3 is not available in the current region. The sizes available in the current region are: ExtraSmall_Internal, Small_Internal, Medium_Internal, Large_Internal, ExtraLarge_Internal, Standard_DC2as_v5, Standard_DC4as_v5, Standard_DC8as_v5, Standard_DC16as_v5, Standard_DC32as_v5, Standard_DC48as_v5, Standard_DC64as_v5, Standard_DC96as_v5, Standard_DC2ads_v5, Standard_DC4ads_v5, Standard_DC8ads_v5, Standard_DC16ads_v5, Standard_DC32ads_v5, Standard_DC48ads_v5, Standard_DC64ads_v5, Standard_DC96ads_v5, Standard_EC2as_v5, Standard_EC4as_v5, Standard_EC8as_v5, Standard_EC16as_v5, Standard_EC20as_v5, Standard_EC32as_v5, Standard_EC48as_v5, Standard_EC64as_v5, Standard_EC96as_v5, Standard_EC96ias_v5, Standard_EC2ads_v5, Standard_EC4ads_v5, Standard_EC8ads_v5, Standard_EC16ads_v5, Standard_EC20ads_v5, Standard_EC32ads_v5, Standard_EC48ads_v5, Standard_EC64ads_v5, Standard_EC96ads_v5, Standard_EC96iads_v5.\r\nFind out more on the available VM sizes in each region at <https://aka.ms/azureregions>."
+        
+    Target="vmSize"
+    ```
+- Scenario: Cluster names are unavailable or conflict with Azure reserved values
+
+   - Example 1
+
+    ```
+    Code="InvalidParameter"
+        
+    Message="The value of parameter name is invalid. Error details: "omsagent-aks-dev-microsoft" managed cluster name is invalid because 'MICROSOFT' and 'WINDOWS' can't be used as either a whole word or a substring in the name.. Please see https://aka.ms/aks-naming-rules for more details."
+    ```
+
+   - Example 2
+
+    ```
+    Message="The value of parameter name is invalid. Error details: "login" managed cluster name is invalid because 'LOGIN' and 'XBOX' can't be used at the start of a resource name, but can be used later in the name.. Please see https://aka.ms/aks-naming-rules for more details."
+     ```
+    
+   - Example 3
+
+    ```
+    Message=" The value of parameter name is invalid. Error details: "azure" managed cluster name is invalid because it is reserved.. Please see https://aka.ms/aks-naming-rules for more details.
+    Target: name"
+    ```
+## Cause
+
+This issue occurs because one of the following conditions is true:
+
+- The Azure Virtual Machine SKU isn't available in the selected region.
+- The service principal is invalid.
+- A virtual network, subnet, or route table is invalid.
+- An Azure CLI parameter is invalid.
+- The value of parameter name is unavailable or reserved by Azure.
+
+There might also be other reasons that your cluster creation attempt failed.
+
+## Solution
+
+In the following table, follow the link for the appropriate troubleshooting step.
+
+| Troubleshooting step | Reference link |
+| -------------------- | -------------- |
+| Check whether the SKU is available | [Resolve errors for SKU not available](/azure/azure-resource-manager/troubleshooting/error-sku-not-available) |
+| Verify that the service principal is valid | [Service principals together with AKS](/azure/aks/kubernetes-service-principal) |
+| Verify that any commands that were used to create the cluster are valid | [az aks](/cli/azure/aks#az-aks-create) (Azure CLI reference) |
+| Verify that any custom network resources that were used to create the cluster are valid | [Configure Azure CNI networking in AKS](/azure/aks/configure-azure-cni) and [Customize cluster egress with a user-defined route](/azure/aks/egress-outboundtype) |
+| Avoid using unavailable or Azure-reserved values for names | [Refer to the error messages provided](#symptoms)
+
+## More information
+
+- [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/error-codes/invalidresourcereference-error.md

@@ -0,0 +1,68 @@
+---
+title: Troubleshoot the InvalidResourceReference error code
+description: Learn how to troubleshoot the InvalidResourceReference errors when you try to create and deploy an Azure Kubernetes Service (AKS) cluster or update an AKS cluster.
+ms.date: 01/11/2024
+editor: v-jsitser
+ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, v-weizhu
+ms.service: azure-kubernetes-service
+#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the InvalidResourceReference error code so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
+ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
+---
+# Troubleshoot the InvalidResourceReference error code
+
+This article discusses how to identify and resolve the `InvalidResourceReference` errors that may occur when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster or update an AKS cluster.
+
+## Symptom 1
+
+When you try to create an AKS cluster, you receive the following error message:
+
+> Code="InvalidResourceReference"
+>
+> Message="Resource  
+> **/subscriptions/*\<subscription-id-guid>*/resourceGroups/MyResourceGroup/providers/Microsoft.Network/virtualNetworks/vnet-otcom/subnets/Subnet-AKS**  
+> referenced by resource  
+> **/subscriptions/*\<subscription-id-guid>*/resourceGroups/MC_MyResourceGroup_MyCluster-AKS_JAPANEAST/providers/Microsoft.Compute/virtualMachineScaleSets/aks-nodepool-vmss**  
+> was not found. Please make sure that the referenced resource exists, and that both resources are in the same region."
+>
+> Details=[]
+
+### Cause 1
+
+Here are the possible causes of this issue:
+
+- A mismatch exists between resources in different regions.
+
+    The example in [Symptom 1](#symptom-1) shows that the virtual network and the virtual machine scale set aren't in the same region. Because the resources are in different regions, it's impossible to create the scale set instance.
+
+- The referenced resource has been manually modified or deleted.
+
+### Solution 1
+
+If a mismatch exists between resources in different regions, review the resources to make sure that they're in the same region. In this example, either modify the region where the AKS cluster is being built, or create a new virtual network in the same region.
+
+If the referenced resource has been manually modified or deleted, it might be difficult to resolve this issue because it's unsupported to manually modify the underlying IaaS resources in the *MC_* resource group. A possible solution might be to recreate the deleted resource, reassociate it with the VMSS, and then trigger an update on the AKS cluster. However, as this is an unsupported scenario, the success of this solution can't be guaranteed.
+
+## Symptom 2
+
+When you try to update an AKS cluster, you receive the following error message:
+
+> Code="InvalidResourceReference"  
+> Message="Resource  
+> /subscriptions/*\<subscription-id-guid>*/resourceGroups/MC_MyResourceGroup/providers/Microsoft.Network/loadBalancers/kubernetes/frontendIPConfigurations/<frontendIP_ID> referenced by resource /subscriptions/*\<subscription-id-guid>*/resourceGroups/MC_MyResourceGroup/providers/Microsoft.Network/loadBalancers/kubernetes/**loadBalancingRules/<frontend_IP_rule> was not found.** Please make sure that the referenced resource exists, and that both resources are in the same region."  
+> Message="Resource  
+>
+> Details=[]
+
+### Cause 2 
+
+This issue might occur if the default outbound rule "aksOutboundRule" on the load balancer is manually modified. This unexpected modification typically occurs when the outbound IP is updated if you update the cluster without the `load-balancer-outbound-ips` parameter.
+
+### Solution 2
+
+Rerun the `az aks update` command with the `load-balancer-outbound-ips` parameter to update your cluster. Use the resource ID of the public IP as the parameter value. For more information, see [Update the cluster with your own outbound public IP](/azure/aks/load-balancer-standard#update-the-cluster-with-your-own-outbound-public-ip).
+
+## More information
+
+[General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/error-codes/linkedauthorizationfailed-error.md

@@ -0,0 +1,51 @@
+---
+title: Troubleshoot the LinkedAuthorizationFailed error code
+description: Learn how to troubleshoot the LinkedAuthorizationFailed error when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
+ms.date: 08/28/2024
+editor: v-jsitser
+ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis
+ms.service: azure-kubernetes-service
+#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the LinkedAuthorizationFailed error code so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
+ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
+---
+# Troubleshoot the LinkedAuthorizationFailed error code
+
+This article discusses how to identify and resolve the `LinkedAuthorizationFailed` error that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
+
+## Symptoms
+
+When you try to create an AKS cluster, you receive the following error message:
+
+> Reconcile VNet failed.
+>
+> Details: VNetReconciler retry failed:
+>
+> Category: ClientError; SubCode: LinkedAuthorizationFailed;
+>
+> Dependency: Microsoft.Network/virtualNetworks; OrginalError: Code="LinkedAuthorizationFailed"
+>
+> Message="**The client '12345678-1234-1234-1234-123456789098' with object id '123456789-1234-1234-1234-1234567890987' has permission to perform action 'Microsoft.Network/virtualNetworks/write' on scope '/subscriptions/*\<subscription-id-guid>*/resourceGroups/MC_MyRG_westeurope/providers/Microsoft.Network/virtualNetworks/aks-vnet'; however, it does not have permission to perform action 'Microsoft.Network/ddosProtectionPlans/join/action' on the linked scope(s) '/subscriptions/*\<subscription-id-guid>*/resourcegroups/ddos-protection-plan-rg/providers/microsoft.network/ddosprotectionplans/upmddosprotectionplan'** or the linked scope(s) are invalid.";
+>
+> AKSTeam: Networking, Retriable: false.
+
+## Cause
+
+A service principal doesn't have permission to use a resource that's required for cluster creation.
+
+## Solution
+
+Grant the service principal permissions to use the resource that's mentioned in the error message. The example output in the "Symptoms" section provides the following information.
+
+| Item | Value |
+| ---- | ----- |
+| Service principal | 12345678-1234-1234-1234-123456789098 |
+| Resource | /subscriptions/*\<subscription-id-guid>*/resourcegroups/ddos-protection-plan-rg/providers/microsoft.network/ddosprotectionplans/upmddosprotectionplan |
+| Operation | Microsoft.Network/ddosProtectionPlans/join/action |
+
+For more information about how to grant permissions to the service principal, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
+
+## More information
+
+- [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/error-codes/missingsubscriptionregistration-error.md

@@ -0,0 +1,51 @@
+---
+title: Troubleshoot the MissingSubscriptionRegistration error code
+description: Learn how to troubleshoot the MissingSubscriptionRegistration error when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
+ms.date: 09/16/2024
+editor: v-jsitser
+ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis
+ms.service: azure-kubernetes-service
+#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the MissingSubscriptionRegistration error code so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
+ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
+---
+# Troubleshoot the MissingSubscriptionRegistration error code
+
+This article discusses how to identify and resolve the `MissingSubscriptionRegistration` error that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
+
+## Symptoms
+
+When you try to deploy an AKS cluster, you receive the following error message:
+
+> Code="MissingSubscriptionRegistration"
+>
+> Message="**The subscription is not registered to use namespace 'Microsoft.OperationsManagement'.** See <https://aka.ms/rps-not-found> for how to register subscriptions."
+>
+> Details=[{
+>
+> "code": "MissingSubscriptionRegistration",
+>
+> "message": "The subscription is not registered to use namespace 'Microsoft.OperationsManagement'. See <https://aka.ms/rps-not-found> for how to register subscriptions.",
+>
+> "target": "Microsoft.OperationsManagement"
+>
+> }]
+
+## Cause
+
+You receive this error message for one of the following reasons:
+
+- The required resource provider isn't registered for your subscription.
+
+- The API version isn't supported for the resource type.
+
+- The location isn't supported for the resource type.
+
+## Solution
+
+To resolve this issue, follow the instructions in the "Solution" section of [Resolve errors for resource provider registration](/azure/azure-resource-manager/troubleshooting/error-register-resource-provider?tabs=azure-portal#solution). Replace the existing namespace with the namespace that's shown in the error message. In the example in the "Symptoms" section, the namespace is `Microsoft.OperationsManagement`.
+
+## More information
+
+- [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]