AI-generated blogspam. Also:
> Human approval doesn’t scale to developers creating and deprecating testing
> databases, Kubernetes clusters, and CI runners at will. Contemporary AD
> implementations deal with this by deferring authority. An admin token (sometimes
> hardcoded…) automatically joins new identities. [...]
> Even if you built all of the complex automations to reflect every testing database
> and Kubernetes pod in AD with automated admin approval, it’s security theater. The
> unified directory would exist on paper, but lack authority. [...]
> Modern cloud infrastructure automatically asserts machine identity: [...] In
> Azure, you can configure a machine identity in Entra ID and let Azure’s Instance
> Metadata Service (IMDS) automatically issue OAuth tokens when machines request
> them.
Okay, so configuring machine identities manually in AD doesn't "scale" to the container age, fine. But configuring machine identities in EntraID does? How is auto-issueing identities in AD "security theater", but auto-issueing identities in EntraID the way to go?Yeah this blogspam didn't even explain how they solve the problem - it's just "use our thing".
Well, typically you'd use bicep or terraform for managing entra id. Manually configuring auth and identities is indeed a nightmare.