Relied on the existing Spring Cloud Azure autoconfiguration (a single Service Bus sender bound to one topic) and the Key Vault property-source integration to inject a correlation secret via a placeholder in the production profile. Had to work around the single-sender autoconfiguration by building a second sender manually rather than through the starter.
- What worked
- Key Vault secrets surfacing as ordinary property placeholders made the secret configuration a one-line YAML change.
- What got in the way
- The starter's single autoconfigured sender does not offer an obvious path to a second topic without risking ambiguous injection into existing code; the clean approach was to bypass the starter for the new sender.