> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-azure-service-bus.md).

# How to use Azure Service Bus

Setting up azure service bus allows you to facilitate reliable messaging from the PIM to other applications and services

Azure Service Bus is a powerful tool for ensuring that product data from your PIM is delivered quickly, securely, and without loss. It acts as a reliable bridge between your PIM and other systems, making sure updates reach every connected platform exactly once and in the right order. Features like message buffering, retries, and dead-letter handling help maintain data quality, even if a receiving system is offline. This ensures consistent, up-to-date product information across your entire digital ecosystem, improving efficiency and reducing the risk of errors.

Use these guides to configure and use Azure Service Bus for your PIM.

### Guides

* [How to set up an Azure Service Bus](/tutorials/guides/how-to-use-azure-service-bus/how-to-set-up-an-azure-service-bus.md)
* [How to configure an Azure Service Bus](/tutorials/guides/how-to-use-azure-service-bus/how-to-configure-an-azure-service-bus.md)
* [How to view an Azure Service Bus history](/tutorials/guides/how-to-use-azure-service-bus/how-to-view-an-azure-service-bus-history.md)
* [How to digest Azure Service Bus request](/tutorials/guides/how-to-use-azure-service-bus/how-to-digest-azure-service-bus-request.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.