Pods stuck in Init state in AKS Cluster after cluster reboot

I have an AKS cluster and vault is installed in Azure VM outside of the AKS cluster. I have a micro-services application consisting of multiple services running in multiple namespaces. The secrets required by the pods of the application are inserted using vault-agent as a sidecar. Everything works fine during the install process and application come up fine. However, we shutdown the cluster and the VM running vault server after business hours and restart it next day. When the cluster is restarted, the pods are getting stuck in Init state and I get 403 permission denied errors. However, if I delete and re-install the application everything works fine.

When I look at the status of vault server, I see the following error message:
Jan 10 14:01:30 vault-server01 vault[933]: 2023-01-10T14:01:30.324-0500 [DEBUG] auth.kubernetes.auth_kubernetes_da8c0187: failed to read local service account token, will use client token: error=“open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory”
Jan 10 14:01:30 vault-server01 vault[933]: 2023-01-10T14:01:30.341-0500 [DEBUG] auth.kubernetes.auth_kubernetes_da8c0187: login unauthorized: err=“{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"tokenreviews.authentication.k8s.io is forbidden: User \“system:serviceaccount:fi4-https:shared-https-wits-sa\” cannot create resource \“tokenreviews\” in API group \“authentication.k8s.io\” at the cluster scope","reason":"Forbidden","details":{"group":"authentication.k8s.io","kind":"tokenreviews"},"code":403}”
Jan 10 14:02:47 vault-server01 vault[933]: 2023-01-10T14:02:47.153-0500 [WARN] core.raft: skipping new raft TLS config creation, keys are pending
Jan 10 14:02:48 vault-server01 vault[933]: 2023-01-10T14:02:48.561-0500 [DEBUG] auth.kubernetes.auth_kubernetes_da8c0187: failed to read local service account token, will use client token: error=“open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory”
Jan 10 14:02:48 403 vault-server01 vault[933]: 2023-01-10T14:02:48.578-0500 [DEBUG] auth.kubernetes.auth_kubernetes_da8c0187: login unauthorized: err=“{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"tokenreviews.authentication.k8s.io is forbidden: User \“system:serviceaccount:fi4-https:shared-https-wits-sa\” cannot create resource \“tokenreviews\” in API group \“authentication.k8s.io\” at the cluster scope","reason":"Forbidden","details":{"group":"authentication.k8s.io","kind":"tokenreviews"},"code":403}”

I was able to recreate the issue by creating the same pod in 2 different namespaces both of which use the same service account to authenticate with vault. If I kill both the pods at the same time, I see that one of the pods is running successfully whereas the other is stuck in Init state.

Appreciate your help in resolving this issue