---
title: "How Do I Create an Azure Service Bus? - Lasernet FO Connector"
slug: "how-do-i-create-an-azure-service-bus"
description: "In this article, we will provide an example of how a Service Bus is created. However, for the latest information always refer to the Microsoft ® guide."
updated: 2026-02-05T11:41:51Z
published: 2026-02-05T11:41:51Z
canonical: "kb.lasernetgroup.com/how-do-i-create-an-azure-service-bus"
---

> ## 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 Create an Azure Service Bus?

## What Is an Azure Service Bus?

An Azure Service Bus is the mechanism that Lasernet uses to send messages.

The description given by Microsoft is: “Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics(in a namespace).”

For more technical information about the Azure Service Bus, refer to [Microsoft’s documentation](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview).

Creating and configuring the Azure Service Bus requires users to create new Azure resources. If you are unsure how to work in Azure, we advise you to contact your system administrator.

## Where Do We Use It?

Azure Service Buses are used in several locations in the Lasernet products, such as the connector to link Finance and Operations and Business Central to Lasernet or linking to Cloud Printers. The following is an example of Azure Service Bus referenced in the **Connections** form of Lasernet FO Connector.

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

## How Do I Create an Azure Service Bus?

This article provides an example of how a service bus can be created. However, for the latest information, always refer to Microsoft’s guides.

1. Navigate to the Azure portal and log in.

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

1. The **Service Bus** can be accessed from the list of services at the top of the page, or using the search bar.

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

1. Click the **Service Bus** icon. You will be taken to a page listing all currently configured service buses.

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

1. Click **Create**.

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

The following screen will be displayed:

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

| Field | Description |
| --- | --- |
| 1. Subscription | The Azure subscription to which the service bus will be billed, accept the default or check with your system administrator to confirm which subscription to use. |
| 1. Resource group | Resource Groups are used to help better organize Azure resources. Customers usually have a Lasernet resource group to select here. |
| 1. Namespace name | The name of the Azure Service Bus. If your organization has a naming convention, then be sure to follow it. |
| 1. Location | The location of the physical hardware that hosts the service bus. For a test instance, the default will be fine, but it is best practice to select the location closest to your Finance, Operations, and Lasernet resources for a production instance. If you are unsure, ask a system administrator. |
| 1. Pricing tier | For most use cases, the Basic Tier for Test and Production is sufficient. Unless you print 500K reports per month (or 250K per month using Cloud Print) you will not reach the limit of Basic Tier. |

1. Fill out the fields as shown:

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

1. Click **Review + create**.

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

Azure will run basic checks on your configuration and then display a “Validation succeeded” message.

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

1. Click **Create**.

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

Deployment will begin, and Azure will confirm it is in progress.

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

Once the deployment is complete, the following message will be displayed:

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

1. Click **Go to resource** to open the new service bus.

## Generate a Connection String for Lasernet

Once the service bus has been created, you need to get the information that allows Lasernet to use it to send messages. This is the connection string. After you have clicked **Go to resource** (in the previous section), you will be directed to this page:

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

1. Under **Settings**, click **Shared access policies**.

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

1. An access policy is ready for use. Click the **RootManageSharedAccessKey** policy and the following screen is displayed:

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

Different keys and strings are displayed.

1. Copy the **Primary Connection String** by using the copy icon.

The string can be copied into Lasernet FO Connector or into the Azure Service Bus input in Lasernet to enable the product to communicate using the Azure Service Bus.

An example:

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

## Create a Queue Name

In this example, the configuration also needs a **Queue name**. This can be created from within FO or the service bus.

1. From the **Resource Overview** page, select **Queues**.

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

1. Add a new **Queue**.

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

1. Give the queue a sensible name, keep the other fields at their defaults, and click **Create**.

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

> [!NOTE]
> Note
> 
> Microsoft defines the purpose of dead lettering as hold messages (this requires a dead-letter queue) that cannot be delivered to any receiver or messages that could not be processed.
> 
> For more information, visit this link: [https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dead-letter-queues](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dead-letter-queues)

When copying the connection string into FO, you will be able to select the queue name from the drop-down:

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