Hi Nishat, thanks for that.
I configured the THE ARGOCD configmap in the helm value config file.
Also I'm using workload federated identity to make the process more secured with token (passwordless) instead of secret.
Is also easy to intergrate RBAC with the process with different teams and different environments.
Areeba Nishat
Setting up SSO for ArgoCD with Azure AD is a great way to streamline access and improve security. Make sure your OIDC connector is properly configured in argocd-cm.yaml, and double-check redirect URIs in Azure. Once it's synced, the login via web UI becomes seamless.
Also, if you’re personalizing your ArgoCD UI or any dev-related dashboards, check out stylish-names.net — it's a fun tool to generate bold and fancy text, perfect for labels, usernames, or project branding.