Azure disk persistent volumes are not being attached to nodes in the OCP cluster with the message: Identity not found

Though, identity does exists. 

This is the managed identity assigned to the cluster which has contributor on the resource group. 

The same identity can create managed-csi disks but cannot create managed-premium.

OCP 4.12.66

All the time in customer cluster

1. Request a volume from the 'managed-premium' storageclass
    

Volume is created but not attached to nodes. 

Volume should be attached to nodes when using legacy 'intree' plugin.

ServicePrincipal configured in kube-system has contributor and user access admin, the managed identity has contributor permission.
SP was used with subscription to create new resource group and other resources without issues.

Volumes requested through 'managed-csi' storageClass works without problems.

Issue is happening on some clusters, but not all of them.
Difference was noted that the 'cloud-provider-config CM where the 'userAssignedIdentityID' has a value, the issue happens.

When this CM doesn't have a value or is empty, the managed-premium storageclass works without problems.