Creates or updates a service namespace. Once created, this namespace's resource manifest is immutable. This operation is idempotent.

Creates or updates a Service Bus queue. This operation is idempotent.

Creates a new rule and updates an existing rule

Creates or updates a topic in the specified namespace.

Deletes an existing namespace. This operation also removes all associated resources under the namespace.

Deletes a queue from the specified namespace in a resource group.

Deletes a subscription from the specified topic.

Deletes a topic from the specified namespace and resource group.

Gets a description for the specified namespace.

Returns a description for the specified queue.

Retrieves the description for the specified rule.

Returns a subscription description for the specified topic.

Gets all the available namespaces within the subscription, irrespective of the resource groups.

Gets the available namespaces within a resource group.

List all the rules within given topic-subscription

List all the subscriptions under a specified topic.

Send raw HTTP request to Azure Service Bus

Receive messages from a queue. Receive messages from a queue will remove the message from the queue.

Send multiple plain text messages to a queue.

Azure Service Bus uses OAuth 2.0 Authentication to authenticate the security principal (a user, a group, or service principal) running the application.
Create and Register your Microsoft application with an Azure AD tenant. For more information refer to https://learn.microsoft.com/en-us/azure/service-bus-messaging/authenticate-application

The first step in using Azure AD to authorize Service Bus entities is registering your client application with an Azure AD tenant from the [Azure portal](https://portal.azure.com/)

Menu > All Services > Azure Active Directory

- Select Add > App registration
- Name the App and set the Supported Account types to 'Accounts in any organizational directory (Any Azure AD directory - Multitenant)'.
- In Redirect URI set the first field to “Web”. In the second field enter https://oauth2.prismatic.io/callback and select Register.

Create a client Secret

- Navigate to your app registration in the Azure portal if you aren't already on the page.
- Select **Certificates & secrets** on the left menu.
- Under **Client secrets**, select **New client secret** to create a new secret.

Set the Permissions to the Service Bus API

- If your application is a console application, you must register a native application and add API permissions for **Microsoft.ServiceBus** to the **required permissions** set. Native applications also need a **redirect-uri** in Azure AD, which serves as an identifier; the URI doesn't need to be a network destination. Use `https://servicebus.microsoft.com` for this example, because the sample code already uses that URI.

Assign Azure roles using the Azure portal

- Assign one of the [Service Bus roles](https://learn.microsoft.com/en-us/azure/service-bus-messaging/authenticate-application#azure-built-in-roles-for-azure-service-bus) to the application's service principal at the desired scope (Service
- Bus namespace, resource group, subscription). For detailed steps, see [Assign Azure roles using the Azure portal](https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal).

Now, configure the OAuth 2.0 connection in Prismatic. Add an Azure Service Bus OAuth 2.0 Connection config variable:

- Use the **Application (client) ID** value for the **Client ID** field.
- Use the **Client Secret** for the same named field.
- If you didn't select Multitenant when creating the Azure application, you will need to replace the **Authorize URL** and **Token URL** with ones specific to your tenant.

Save your integration and you should be able to authenticate a user through Azure Service Bus with OAuth 2.0.


[Connection String](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues?tabs=connection-string#get-the-connection-string)

The Connection String authentication method is required for any integrations using the following actions:

1.  Send Messages from Queue
2.  Receive Messages from Queue

Additionally, in an integration, ensure when using these actions, the connection is configured to the Connection String authentication type.

Creating a new namespace automatically generates an initial Shared Access Signature (SAS) policy with primary and secondary keys, and primary and secondary connection strings that each grant full control over all aspects of the namespace. See [Service Bus authentication and authorization](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues?tabs=connection-string) for information about how to create rules with more constrained rights for regular senders and receivers.

A client can use the connection string to connect to the Service Bus namespace. To copy the primary connection string for your namespace, follow these steps:

1.  On the Service Bus Namespace page, select Shared access policies on the left menu.
2.  On the Shared access policies page, select RootManageSharedAccessKey.

In the Policy: RootManageSharedAccessKey window, select the copy button next to Primary Connection String, to copy the connection string to your clipboard for later use. Paste this value into the connection configuration of your Prismatic integration.


Interact with message queues and publish-subscribe topics (in a namespace)

[Azure Service Bus](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview) is a fully managed enterprise message broker with message queues and publish-subscribe topics (in a namespace).


Receive and validate webhook requests from Azure Service Bus for webhooks you configure.

To trigger webhook calls within Service Bus, you need to make use of Azure Event Grid and Logic Apps. Follow these steps to build the webhook integration:

1. Register Microsoft.EventGrid resource provider to the subscription:

   - Navigate to Azure account subscriptions.
   - Open the subscription settings.
   - Go to Resource Providers.
   - Register Microsoft.EventGrid resource.

2. Create a Service Bus namespace: [Create a Service Bus Namespace](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#create-a-service-bus-namespace)

3. Receive messages by using Logic Apps: [Receive Messages by Using Logic Apps](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#receive-messages-by-using-logic-apps)

4. Add a step to receive messages from Service Bus via Event Grid: [Add a Step to Receive Messages from Service Bus via Event Grid](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#add-a-step-receive-messages-from-service-bus-via-event-grid)

5. Add a foreach loop: [Add a Foreach Loop](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#add-a-foreach-loop)

6. Add an HTTP action to post to Prismatic integration trigger:

- Within the For Each loop, select "Add an action."
- In the "Search connectors and actions" text box, enter "HTTP."
- Select the HTTP action.
- Select POST for Method.
- Add the Prismatic Integration flow URL to the URI Input.
- For the Body, add this expression: `base64ToString(items('For_each')?['ContentData'])`.

7. Add another action in the foreach loop to complete the message: [Add Another Action in the Foreach Loop to Complete the Message](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#add-another-action-in-the-foreach-loop-to-complete-the-message)

To test the webhook, send a message to the Topic Subscription using Service Bus Explorer. This should trigger the integration with Prismatic.


Action Name	Action Description
Create or Update Namespaces	Creates or updates a service namespace. Once created, this namespace's resource manifest is immutable. This operation is idempotent.
Create or Update Queue	Creates or updates a Service Bus queue. This operation is idempotent.
Create or Update Rules	Creates a new rule and updates an existing rule
Create or Update Subscription	Creates a topic subscription.
Create or Update Topic	Creates or updates a topic in the specified namespace.
Delete Namespace	Deletes an existing namespace. This operation also removes all associated resources under the namespace.
Delete Queue	Deletes a queue from the specified namespace in a resource group.
Delete Rule	Deletes an existing rule.
Delete Subscriptions	Deletes a subscription from the specified topic.
Delete Topic	Deletes a topic from the specified namespace and resource group.
Get Namespaces	Gets a description for the specified namespace.
Get Queue	Returns a description for the specified queue.
Get Rule	Retrieves the description for the specified rule.
Get Subscriptions	Returns a subscription description for the specified topic.
Get Topic	Gets all the topics in a namespace
List Namespaces	Gets all the available namespaces within the subscription, irrespective of the resource groups.
List Namespaces By Resource Group	Gets the available namespaces within a resource group.
List Queues	Gets the queues within a namespace.
List Rules	List all the rules within given topic-subscription
List Subscriptions	List all the subscriptions
List Subscriptions By Topic	List all the subscriptions under a specified topic.
List Topics By Namespace	Gets all the topics in a namespace
Raw Request	Send raw HTTP request to Azure Service Bus
Send Multiple Messages to Queue	Send multiple plain text messages to a queue.
Send Message to Queue	Send a single message to a queue.
Receive Messages from Queue	Receive messages from a queue. Receive messages from a queue will remove the message from the queue.

Azure Service Bus Connector

Integrate with customers’ other SaaS apps, fast

About the Azure Service Bus Connector

Actions

Triggers

Ready to get started?