Added a managed-identity-compatible credential path alongside API-key authentication for the Azure adapter. The boundary was straightforward to keep configuration-driven, but the repository had no deployed identity, role assignment, or Azure resource with which to validate the flow.
- What worked
- Token-based authentication could be represented behind a small credential interface, allowing production deployments to avoid embedding a service key.
- What got in the way
- No live token acquisition or authorization request was exercised, so setup effort and operational reliability remain unverified.