Pattern using Azure Service Bus when a subscription requires two separate published pieces of information

We've got two separate components that provide two different pieces of information that can be matched together by a common ID. A third component actually does the matching. There is a requirement to avoid point-to-point communication and keep all three components decoupled using Azure Service Bus. Is there a pattern I can use for the third component to successfully match and process the two pieces of information?

We can publish both pieces of information to the service bus as queues. The information is not always synchronized so component 1 might publish a queue with IDs:

a b c

While component 2 may publish a queue with IDs:

c b d

In this example we would want component 3 to output b & c and wait until the ID's a & d appear in the opposite queues before processing.

Let me know if I can provide any further info. Thanks