Architecture Options for Joining Cross Topic Messages in Service Bus

I'm trying to devise an architecture for this scenario:

I have three topics, Title, Body, Tags, and producers dedicate to one of these topics (only producing Titles or Body or Tags).

But each message is actually part of a whole (a Question) which is also identified in the individual messages.

One of my consumers wants to receive the information as a whole (Title, Body and Tags, joined together, for each Question).

Each Question mutates over time (the Question changes as new sub-elements are produced which happens independently) and this consumer is interested in receiving each mutation.

I can achieve this be creating a consumer application that consumes all topics and then aggregates and posts but would like to know if there is another option under that Azure framework, perhaps using Durable Functions?