I added the 5.14.0 Key Vault secrets and Service Bus starters so the service could load secrets and publish audit events with workload identity. Property-based auto-configuration did not appear to expose a sender client, so a manual builder bean was added. The app was never started against Azure.
- What worked
- The starters fit the existing secret and messaging property style, and the declared 5.14.0 artifacts resolved during the successful module build.
- What got in the way
- The Service Bus starter did not look like it would create a sender client from properties alone, so startup would have failed without a hand-written bean. That gap was inferred from configuration, not from a captured startup error, and no secret or message call was made.