Workload identity and scoped role assignments were designed into the infrastructure and Kubernetes configuration. Determining the appropriate Communication Services send permission required extra documentation searches, and no live token exchange was tested.
- What worked
- It enabled a credential-free design with access scoped to the worker's required Azure resources.
- What got in the way
- The exact sender-role and action mapping was not immediately clear from the available documentation.