---
title: "Discussion on \"Securely login to Argocd via web UI with SSO Azure Active Directory\" | Hashnode"
description: "Discussion on \"Securely login to Argocd via web UI with SSO Azure Active Directory\". Introduction\nIn modern DevOps environments, secure and centralized access control is critical — especially when managing production-grade Kubernetes clusters with GitOps tools like Argo CD. Rather than relying on local user accounts or static passwor..."
url: "https://hashnode.com/posts/securely-login-to-argocd-via-web-ui-with-sso-azure-active-directory/685eb5186318867900f30852"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Securely login to Argocd via web UI with SSO Azure Active Directory](https://georgeezejiofor.com/securely-login-to-argocd-via-web-ui-with-sso-azure-active-directory?utm_source=hashnode&utm_medium=feed)

Introduction In modern DevOps environments, secure and centralized access control is critical — especially when managing production-grade Kubernetes clusters with GitOps tools like Argo CD. Rather than relying on local user accounts or static passwor...

Jun 27, 2025 · 9 min read · georgeezejiofor.com  
Read the article

-   [#argocd](https://hashnode.com/tag/argocd)
-   [#gitops](https://hashnode.com/tag/gitops)
-   [#sso](https://hashnode.com/tag/sso)
-   [#workload-identity-federation](https://hashnode.com/tag/workload-identity-federation)
-   [#istio](https://hashnode.com/tag/istio)
-   [#aks](https://hashnode.com/tag/aks)

## Written by

[George Ezejiofor](https://hashnode.com/@georgeezejiofor)

@georgeezejiofor · London, United Kingdom

  
[View profile](https://hashnode.com/@georgeezejiofor)

Director & AI/ML Platform / MLOps Engineer at GeoCloudTech | Kubestronaut | Kubernetes, DevSecOps and MLOps for regulated industries

I'm an AI/ML Platform and MLOps Engineer and a Kubestronaut, with 13+ years in IT and 5+ in DevOps and DevSecOps. Through my consultancy, GeoCloudTech, I design secure, highly available Kubernetes platforms for regulated industries, on cloud and on-premises. What I build: - Kubernetes platforms: RKE2, AKS, EKS, GKE - MLOps: Kubeflow, KServe, MLflow, NVIDIA GPU Operator - DevSecOps: Vault, Kyverno, KubeArmor, Trivy, signed supply chains with Tekton and Cosign - GitOps and automation: Argo CD, Flux, Terraform, Ansible - Storage and identity: Rook Ceph, CloudNativePG, Keycloak - Observability and networking: Prometheus, OpenTelemetry, Cilium, Istio Most of what I publish comes from my multi-datacentre homelab: RKE2 on Proxmox, run through GitOps. My rule: build it, break it, understand it, then harden it. Every article is a real build, traps included. Certifications: Kubestronaut (CKA, CKAD, CKS, KCNA, KCSA), HashiCorp Terraform Associate.

## Responses 1

Markdown supported · ⌘↵ to post

[Areeba Nishat](https://hashnode.com/@arib)

[Jun 27, 2025](https://hashnode.com/posts/securely-login-to-argocd-via-web-ui-with-sso-azure-active-directory/685eb5186318867900f30852/comment/685eb643982762c52eaa599a)

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](https://stylish-names.net/) — it's a fun tool to generate bold and fancy text, perfect for labels, usernames, or project branding.

[George Ezejiofor](https://hashnode.com/@georgeezejiofor)

[Jun 27, 2025](https://hashnode.com/posts/securely-login-to-argocd-via-web-ui-with-sso-azure-active-directory/685eb5186318867900f30852/comment/685eb643982762c52eaa599a#reply-685ebd6b804a14e35289a174)

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.
