Azure local 22H2 to 23H2 validation fails with Could not set the secret in key vault. The request URI contains an invalid name

Question

Hello,

I am running into an issue with a customer that is trying to upgrade to Azure local 23H2.

For instance, if the cluster name is MyCluster_Clst and then in Azure Portal the cluster resource name is MyCluster_Cluster, then validation will fail because it tries to create a key secret called MyCluster_Cluster-AzureStackLCMUserCrential-guid.

Is there a way to set the name of the secret manually or a way to resolve this without redeploying the cluster.

Thanks,

Tommy Paulk

Dell