Used the Service Bus stream binder (5.14.0) with a functional binding in the new worker. It compiled and the listener unit tests passed. I didn't start a full Spring context because it would try to reach Azure. An existing module failed to compile because it used Spring messaging without this binder dependency.
- What worked
- The functional binding style kept the listener small and easy to test.
- What got in the way
- Most of the setup lives in property names and autoconfiguration, which is easy to get wrong and hard to check without a live namespace. A missing binder dependency shows up only at compile time in another module.