Workload identity and least-privilege role assignments were wired through Bicep and Kubernetes for sending email and consuming queues. The approach eliminated application secrets, but object IDs, role scopes, and module parameter placement required careful configuration.
- What worked
- It supported separate identities and narrowly scoped permissions for the API, mailer, and event-delivery path.
- What got in the way
- Federation and token acquisition were not tested in a live cluster, and the first Bicep parameter wiring attempt failed compilation.