# Azure event configuration tutorial

This guide steps you through configuring Microsoft Azure for Pismo event notification delivery. This requires you to do two things in Azure:

* Configure a Service Bus Topic in the Azure Portal – Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics (in a namespace). Service Bus is used to decouple applications and services from each other which help to balance workload.
* Grant permission to Pismo’s Service Principal – An Azure Service Principal is an identity created for use with applications, hosted services, and automated tools to access Azure resources. This access is restricted by the roles assigned to the Service Principal, giving you control over which resources can be accessed and at which level. Pismo's Service Principal needs to be visible in your Azure directory.

For this tutorial, you need:

* A Microsoft Azure account
* Your Azure Tenant ID (found in your Azure Active Directory)

> 🚧 About Microsoft Service Bus tiers
>
> Microsoft offers guaranteed latency and throughput only when using the [Azure Service Bus premium messaging tier](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-premium-messaging). The Standard tier does not offer these guarantees because it shares resources with other tenants, so its performance can vary. If your application has low latency requirements, the standard messaging tier is not recommended.

# Configure a Service Bus Topic in the Azure Portal

1. Go to **Service Bus** in the Azure portal. (Type **Service Bus**\<enter> in Search and it appears)

2. Select **+Create** from the top left. The **Create namespace** page appears.

3. Fill out all required fields.

   For **Pricing tier**, select **Standard** or **Premium**. Standard, at a minimum, is required to use topics.

4. Select **Review and create** and, then, **Create**

5. After deployment is complete, select **Go to resource**:

<Image title="servicebusSM.png" alt={600} align="center" className="border" border={true} src="https://files.readme.io/6d6d08d-servicebusSM.png" />

6. In the navigation menu, under **Entities**, select **Topics**.

<Image title="serviceBus4.png" alt={300} align="center" className="border" border={true} src="https://files.readme.io/451973a-serviceBus4.png" />

7. Select **+Topic** at the top of the screen. The **Create topic** screen appears.

8. Enter **Name** and configurations and select **Create**.

9. Click your newly-created topic and from its overview page, find its **Topic URL**.

At this point, you need to send Pismo your topic URL and tenant ID. Pismo then sends you back their Server Principal ID that you need for the following procedure.

**To grant permission to Pismo's Service Principal:**

1. Construct the following URL

   [https://login.microsoftonline.com/\<azure-tenant-id>/adminconsent?client\_id=\<pismo-service-principal-id>](https://login.microsoftonline.com/\<azure-tenant-id>/adminconsent?client_id=\<pismo-service-principal-id>)

2. Enter URL in browser

   You are presented with a Microsoft Login page to give permission to the Service Principal. Confirm that the Service Principal description matches the Pismo provided one and select **Accept**.

   **Note:** You might see a screen after this saying "Sorry, but we're having trouble signing you in." This is to be expected and is not an error.

3. Go back to the overview page for your newly-created Service Bus and, from the navigation, select **Access Control (IA)**.

4. Select **Add role assignment**.

5. Select **Azure Service Bus Sender** on the left-side and select **Next**.

<Image title="addroleassignSmall.png" alt={600} align="center" className="border" border={true} src="https://files.readme.io/5ad2e1d-addroleassignSmall.png" />

6. Select **+Select Members**.

7. On the **Select members** screen that appears on the right, select the Pismo Service Principal, then, select **Select**.

   The Pismo Service Principal should be listed under **Members**.

8. Click **Next**, then **Review and assign**.