<commit_before>---
title: Azure Transports
summary: Azure transports enable Azure Storage Queues and Azure Service Bus as underlying NServiceBus transports, in cloud-hosting and hybrid scenarios.
tags:
- Cloud
- On-Premise
- Azure
- Transports
- Azure Service Bus
- Azure Storage Queues
redirects:
 - nservicebus/windows-azure-transport
related:
 - samples/azure/storage-queues
 - samples/azure/azure-service-bus
---

The Azure transports for NServiceBus enable the use of Azure Queues and Azure Service Bus as the underlying transports used by NServiceBus. It can be used in multiple scenarios:

 * Cloud hosting scenario: An NServiceBus endpoint is hosted as a cloud service and communicates with another endpoint located in another cloud service through the use of one of the Azure transports for NServiceBus.
 * Hybrid scenario: An NServiceBus endpoint is hosted on-premise and uses one of the Azure transports for NServiceBus to communicate with another NServiceBus endpoint hosted on a Cloud Service and/or on-premise.

As part of the Azure support for NServiceBus, you can choose between two options provided by the Azure platform:

-   Azure Storage Queues
-   Azure Service Bus

Each of these two options has separate features, capabilities, and usage characteristics. A detailed comparison and discussion of when to select which is beyond the scope of this document. To help decide which option best suits your application's needs, review the MSDN article "[Azure Queues and Azure Service Bus Queues - Compared and Contrasted](https://msdn.microsoft.com/library/azure/hh767287.aspx)".<commit_msg>Update azure-transport.md<commit_after>---
title: Azure Transports
summary: Azure transports enable Azure Storage Queues and Azure Service Bus as underlying NServiceBus transports, in cloud-hosting and hybrid scenarios.
tags:
- Cloud
- On-Premise
- Azure
- Transports
- Azure Service Bus
- Azure Storage Queues
redirects:
 - nservicebus/windows-azure-transport
related:
 - samples/azure/storage-queues
 - samples/azure/azure-service-bus
---

The Azure transports for NServiceBus enable the use of Azure Queues and Azure Service Bus as the underlying transports used by NServiceBus. It can be used in multiple scenarios:

 * Cloud hosting scenario: An NServiceBus endpoint is hosted as a cloud service and communicates with another endpoint located in another cloud service through the use of one of the Azure transports for NServiceBus.
 * Hybrid scenario: An NServiceBus endpoint is hosted on-premise and uses one of the Azure transports for NServiceBus to communicate with another NServiceBus endpoint hosted on a Cloud Service and/or on-premise.

As part of the Azure support for NServiceBus, you can choose between two options provided by the Azure platform:

-   Azure Storage Queues
-   Azure Service Bus

Each of these two options has separate features, capabilities, and usage characteristics. A detailed comparison and discussion of when to select which is beyond the scope of this document. To help decide which option best suits your application's needs, review the Azure article "[Azure Queues and Azure Service Bus Queues - Compared and Contrasted](https://azure.microsoft.com/en-us/documentation/articles/service-bus-azure-and-service-bus-queues-compared-contrasted/)".
{'fraction_non_alphanumeric': 0.0492550927333536, 'fraction_numerical': 0.0018242626938279112, 'mean_word_length': 4.614334470989761, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7469815', 'n_tokens_mistral': 804, 'n_tokens_neox': 779, 'n_words': 420}