title: Service Bus Forwarding to another Service Bus
body: <p>I need to create an architecture that receives messages from different Azure Service Bus topics. Those topics are in the same Service Bus Namespace. To do so, I can create one subscription for every topic. The architecture should be able to start receiving messages from more topics if needed.
  The architecture needs to have its own Service Bus Namespace to receive messages, using queues or topics.</p>
  <p>I don't want to create an Azure Function for every topic/subscription, Instead I want to be able to implement only one Azure Function to receive all messages from the different topics.</p>
  <p>As an example:</p>
  <p>I have a Service Bus Namespace &quot;<strong>ServiceBusNamespace1</strong>&quot;</p>
  <p><strong>ServiceBusNamespace1</strong> contains the following topics and subscriptions:</p>
  <ol>
  <li><strong>topic1</strong> -&gt; subs1</li>
  <li><strong>topic2</strong> -&gt; subs2</li>
  <li><strong>topic3</strong> -&gt; subs3</li>
  </ol>
  <p>I have another Service Bus Namespace &quot;<strong>ServiceBusNamespace2</strong>&quot;</p>
  <p><strong>ServiceBusNamespace2</strong> contains the following topic and subscription:</p>
  <ol>
  <li><strong>topic4</strong> -&gt; subs4</li>
  </ol>
  <p><strong>I need that topic4 receives messages from topic1 and topic2.</strong></p>
  <p>I can do this with &quot;auto-forwarding&quot; option if topic4 is in ServiceBusNamespace1. But I need topic4 to be in another Service Bus Namespace.</p>
  <p>Is there any way of achieving this?</p>
  <p>I tried using Service Bus Event Subscription, but I cannot use custom schema for Event Grid.</p>