# How to configure an Azure Service Bus

Under the "Azure Service Bus" tab, you can hover over a specific service bus and click the "Edit" ![](/files/3alF3Z9rnjD5JvoJK2yf) button. Scroll down to the "Events" section to start configuring the service bus.

<figure><img src="/files/qrvvNw2S9omVvs1ZkU6l" alt=""><figcaption><p>Showcasing Events</p></figcaption></figure>

The image above, shows an "Active" toggle, this determines if your azure service bus is active. Remember to enable it after you have finished configuring the service bus.

### Trigger events

Trigger events determine what events the service bus sends out messages for. So if you, for example, are interested in all events regarding products, creation, deletion and updates, you could expand the "products" section and enable all of them.

<figure><img src="/files/E1ZznwMO37MLMLsu7jG9" alt=""><figcaption><p>Example of events enabled</p></figcaption></figure>

Now if you have activated your azure service bus, it will add every product creation, deletion or update to the message queue. It quickly becomes obvious to see there is room for a lot of customization regarding which events your service bus triggers on.

### Advanced settings

Some events have advanced settings, you can configure these settings by clicking "Advanced settings" to the right of a toggle. These settings will allow you to further customize some events and when they should trigger. While the advanced settings can vary from event to event, they are overall quite similar.

We will show advanced settings for "Product updated" as an example.

<figure><img src="/files/T8FL7GVx0Zcf1AUqAhkR" alt=""><figcaption><p>Specific event with "Advanced settings"</p></figcaption></figure>

Here we can see two sections, "Trigger options" and "Setup request".

<figure><img src="/files/Yts1mzCL2Jy74y4Y2Ram" alt=""><figcaption><p>Advanced settings</p></figcaption></figure>

#### Trigger options

When you enable "Conditional triggering" more options will pop up. These trigger options are more specific, such as "Product structure updates".

<figure><img src="/files/bDHoOjLqh42AFhgZblLk" alt=""><figcaption><p>Additional trigger options</p></figcaption></figure>

We can also choose if it should trigger on attribute updates, such as; "Do not fire", "Fire on all", or "Fire on specific". If you choose "Fire on specific" you can choose which specific attributes to trigger on.

<figure><img src="/files/zqrRogCPxnZGyhiBtZJ1" alt=""><figcaption><p>Only fire if Color, BaseCostPrice, Brand or Description is updated</p></figcaption></figure>

#### Setup request

You can choose a data mode and see an example of the data output. The options are either; "Ids only" or "Change set".

"Ids only" will only contain the transaction uid and the ids of the products that were updated.

<figure><img src="/files/qhdbZ4zVL8YQHZ0dFwJv" alt=""><figcaption><p>Ids only example</p></figcaption></figure>

The "Change set" however, will contain the transaction uid, ids of the products that were updated and information about what was updated on the products.

<figure><img src="/files/tx63CL6x2u92HHRrYm9C" alt=""><figcaption><p>Change set example</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.struct.com/tutorials/guides/how-to-use-azure-service-bus/how-to-configure-an-azure-service-bus.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
