A managed identity, federated workload configuration, scoped role assignments, and client-ID wiring were designed for email, messaging, and database access. The approach eliminated a new secret, but deployment-specific identity values still had to be substituted.
- What worked
- It supported least-privilege, secretless access across the Azure services selected for the worker.
- What got in the way
- Federation was not tested in a live cluster, and the generated client ID still needed to be placed into the deployment manifest.