ApplicationSet is not able to authenticate against Azure Repos using Workload Identity in AKS

[sweco-nltbim]

I am new to ArgoCD (currently using v3.3.9) and I was able to configure Workload Indentity within AKS to access my Azure Repos using a Service Principal. However when I am trying to deploy an ApplicationSet I get the following error:

2026-05-01T17:52:22.658779862Z {"error":"error generating params from git: error retrieving Git files: rpc error: code = Internal desc = unable to resolve git revision : failed to list refs: unexpected client error: unexpected requesting "https://dev.azure.com///_git//info/refs?service=git-upload-pack" status code: 302","generator":{},"level":"error","msg":"error generating params","time":"2026-05-01T17:52:22Z"}
2026-05-01T17:52:22.660511994Z {"applicationset":{"Namespace":"argocd","Name":"kgateway"},"error":"error generating params from git: error retrieving Git files: rpc error: code = Internal desc = unable to resolve git revision : failed to list refs: unexpected client error: unexpected requesting "https://dev.azure.com///_git//info/refs?service=git-upload-pack" status code: 302","generator":{"git":{"repoURL":"https://dev.azure.com///_git/","files":[{"path":"argocd/applications/kgateway/kgateway-crds-helm.yaml"}],"revision":"feature/B-15937","template":{"metadata":{},"spec":{"destination":{},"project":""}}}},"level":"error","msg":"error generating application from params","time":"2026-05-01T17:52:22Z"}
2026-05-01T17:52:22.660532010Z {"applicationset":{"Namespace":"argocd","Name":"kgateway"},"level":"error","msg":"unable to generate applications: error generating params from git: error retrieving Git files: rpc error: code = Internal desc = unable to resolve git revision : failed to list refs: unexpected client error: unexpected requesting "https://dev.azure.com///_git//info/refs?service=git-upload-pack" status code: 302","time":"2026-05-01T17:52:22Z"}

I tried to add a federated credential for the argocd-applicationset-controller and argocd-server and enabled workload identity for those 2 pods but unfortunately that did not solve the issue. It seems that the status 302 is a response that whatever pod is calling the url is not using workload identity and is not authenticated to do so.

This specific repo is using workload identity and the connection status is succesfull which means that the workload identity configured under the argocd-repo-server pod is doing its job:

Can anyone tell me what is wrong with my setup?

[sweco-nltbim]

EDIT: I found the issue. It was a wrong repository url in my ApplicationSet.