---
title: "How Do I Add an Additional Azure Service Bus for a Specific Report?"
slug: "add-an-additional-azure-service-bus-for-a-specific-report"
description: "This article will demonstrate how to add another Azure Service Bus for a specific report. Follow the steps listed in the following article. "
updated: 2026-02-05T10:52:33Z
published: 2026-02-05T10:52:33Z
canonical: "kb.lasernetgroup.com/add-an-additional-azure-service-bus-for-a-specific-report"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Do I Add an Additional Azure Service Bus for a Specific Report?

This article demonstrates how to add another Azure Service Bus for a specific report. Follow these steps:

1. Create a new queue in Service Bus Explorer. In the example (FlemmingTest), `Transport Type` is located at the end of the string when selected.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-NB1T0J17.png)

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-HQC4WRYQ.png)

1. Create a new Azure Service Bus Input Port in Lasernet Developer. In the example, we have duplicated the existing one. The new one is called “Azure Service Bus – Copy”.
2. **Commit**/**Deploy** to make it available.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-PQVP00U9.png)

1. Create a new Connection in Lasernet FO Connector. In the example, it is called “FlemmingTestID”.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-01B197ZE.png)

1. Create a new server in Lasernet FO Connector and reference the new connection. In the example, the new server’s name is the same as the connection’s, with `_b` appended.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-U1AQFM7X.png)

1. Ensure the new server is placed after the default server (at the top) and toggle the **Active** button to **Yes**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-6KHA561F.png)

1. Select the report where you will run the batch, and set the new server as your choice. In the following example, the report is **SalesConfirmReplacement**, to which the new server is attached. All the other reports do not include a server selection, so they will use the default server.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-6C506BHP.png)

This report will now use this Azure Service Bus, while the others will use the original one.