In this article:

  • Associating a Service Principal
  • How to authorize Service Principal from the Azure portal
  • Associating a Namespace in ServiceBus360
  • Creating a Composite Application

Associating a Service Principal in ServiceBus360

The first step to getting started with your account in ServiceBus360 is by associating a Service Principal. Azure Service Principal is an instance of an application that is within your Active Directory that is allowed access to one or more resources. In order to associate the Service Principal in ServiceBus360, the following values must be specified.

  1. Subscription ID
  2. Tenant ID
  3. Client ID
  4. Client Secret
  5. Authorize Service Principal

To associate a Service Principal in ServiceBus 360:

  1. Log in to your ServiceBus360 account
  2. Click the 'Settings (gear)' icon in the top right corner of your screen
  3. Click the 'Service Principal' tab in the left menu panel to open the Associate Service Principal blade
  4. Enter the Friendly name, Subscription Id, Tenant Id, Client Id, Client Secret details
  5. Click the 'Save' button to associate the Service Principal


In order for ServiceBus360 to access entities from Azure (like Logic Apps) in a secure and safe way, a Service Principal needs to be created and authorized correctly. Azure has “Role-Based Access Control (RBAC)”, and it allows to authorize a Service Principal to access certain resources based on the access permission.

How to get Azure Subscription Id?

Here is a quick step by step guide on how to get your Subscription ID from the New Azure Portal.

  1. Browse to https://portal.azure.com and Sign into your account.
  2. In the portal, navigate to the ‘Subscriptions’ tab in the left side menu. If the tab is not visible, then click on the ‘More services’ tab to find it.
  3. In the Subscriptions blade, all the subscriptions will be listed and copy the ID from ‘Subscription ID’ column.

How to get Azure Tenant Id?

The tenant ID is tied to ActiveDirectory in Azure:

  1. Navigate to Dashboard in the Azure portal
  2. In the portal, navigate to the ‘Azure Active Directory’ tab in the left side menu
  3. Click the Properties tab under the Manage section
  4. Click the Copy icon against the "Directory ID" to get the Azure Tenant ID

How to get the Client Id and Client Secret

In order for you to get the Client Id and Client Secret, you’ll first be required to create a Service Principal as explained below: 

  1. Login to your Azure Account
  2. Select Azure Active Directory and click App registrations
  3. Click on the “New Application Registration” link – this will open up a new blade to enter service principal details
  4. Enter a name for the Service Principal, keep the Application Type to default (Web App / API), in the “Sign-on Url” tab enter any URL - for example – http://localhost.

  5. Once the Service Principal is created successfully, it will be listed in the App Registration grid

  6. Click on the Service Principal > Copy the Application ID from Essentials window. This is your Client ID.

  7. Click on Keys under API Access from the Settings Blade > create a key by entering a name for the key. Select when it should expire and click on “Save”.

  8. Once it is saved, it will show you the Client Secret. This ID will be displayed only once, copy this value because you are not able to retrieve the key later.

Service Principals are service accounts in Azure. The Authorization hierarchy works top to bottom which means – if you’re authorizing someone to access a top-level resource, the authorization will be passed down to every resource under the top-level resource. For example – if you authorize a Service Principal to access a Resource Group – all the resources inside the Resource Group will be accessible.


How to Authorize Service Principal from Azure Portal

The first step is to authorize a Service Principal is to navigate to the resource you want the service principal to access. Let's take an example of authorizing the service principal to access a resource group.

  1. Navigate to the Resource Group > Click on “Access Control (IAM)”. As you click on Access Control – it will list all the service accounts which are authorized to access the selected Resource Group.
  2. Add new permission for the newly added Service Principal. Click on the “Add” button on the top left on this blade. It will ask you to select a role and user for new permission. Please refer to the image below. In the Role drop-down, you will find a lot of pre-defined roles scoped to specific resource types with different permissions- like Reader, Manager etc. Select “Contributor” from the list. On the next input- type the name of the service principal. It will list the service principals and users for the given name. You can select more than one Service Principal/User here. Select the desired Service Principal’s name and click “Save”.
  3. In few seconds the portal will notify you that the user has been added and can perform the operations with allowed permissions.


Associating a Namespace in ServiceBus360

A namespace can be associated with two ways in ServiceBus360. You can either choose to associate a namespace using the connection string details or the namespaces that are accessible through the associated Service Principals. However, you must first create a namespace in Azure and obtain the management credentials. 

Creating a namespace in Azure

  1. Log into the Azure portal
  2. In the left navigation pane of the portal, click New, then click Enterprise Integration, and then click Service Bus
  3. In the Create Namespace dialog, enter a namespace name. The system immediately checks to see if the name is available
  4. After making sure the namespace name is available, choose the pricing tier (Basic, Standard, or Premium)
  5. In the Subscription field, choose an Azure subscription in which the namespace has to be created
  6. In the Resource group field, choose an existing resource group to which the namespace will belong to, or create a new one
  7. In Location, choose the country or region in which your namespace should be hosted

  8. Click Create. The system now creates your namespace and enables it. You might have to wait several minutes as the system provisions resources for your account

Obtain the management credentials

  1. In the list of namespaces, click the newly created namespace name
  2. In the namespace blade, click Shared access policies
  3. In the Shared access policies blade, click RootManageSharedAccessKey. We recommend you to create a new Shared Access Policy with the name - ServiceBus360. Enable all the three claims - Manage, Send & Listen. You can use this policy to associate the namespace with ServiceBus360.

  4. In the Policy: RootManageSharedAccessKey blade, click the Copy button next to Connection string–primary key, to copy the connection string to your clipboard for later use. Paste this value into Notepad or a clipboard to associate this connection string in ServiceBus360.

Associating the Namespace using Connection String


  1. Log in to your 'ServiceBus360 account' 
  2. From the Home Dashboard, click the 'Settings (gear)' icon to navigate to the ServiceBus360 Settings section
  3. Click the 'Namespaces' tab from the left navigation panel to open the Associate Namespaces blade
  4. In the Associate Namespaces blade, click the 'Associate Namespace using ConnectionString' option and enter the following details:
    1. Friendly Name - It is an alias name of the Azure Namespace. This friendly name is valid only within ServiceBus360.
    2. Connection String - Enter the Connection String value, this is available in the Azure portal. A Connection String with Manage claims policy is necessary to operate on Azure Namespaces.
    3. Azure Namespace - This field is automatically filled once the correct Connection String is filled in the above field
    4. Select Azure Namespace Type - Select the appropriate namespace type as created in the Azure portal. Selecting wrong namespace type would not display the corresponding entities.
  5. Click the 'Save' button to complete the process and associate the namespace with ServiceBus360.
  6. You can view the confirmation message from the Notification section

Associating the Namespace using Service Principals

  1. Log in to your 'ServiceBus360 account' 
  2. From the Home Dashboard, click the 'Settings (gear)' icon to navigate to the ServiceBus360 Settings section
  3. Click the 'Namespaces' tab from the left navigation panel to open the Associate Namespaces blade
  4. In the Associate Namespaces blade, click the 'Associate Namespace available from Service Principals' option and select the namespaces
  5. Click on the checkbox against the namespace that you wish to associate with ServiceBus360
  6. Click the 'Save' button to associate the namespace
  7. You can view the confirmation message from the Notification section

Creating a Composite Application

Modern Azure Applications are built by putting together a solution that uses a minimum of 3 to 4 discrete technologies in Azure. ServiceBus360 Composite Application acts as a logical group of resources or entities from same or multiple Azure Subscriptions which you can manage and monitor as a single unit. To create a Composite Application in ServiceBus360:

  1. Log in to your 'ServiceBus360 account' 
  2. From the Home Dashboard, click the 'Settings (gear)' icon to navigate to the ServiceBus360 Settings section
  3. Click the 'Composite Applications' tab from the left navigation panel 
  4. Click the 'Create' button from the top menu to open the Add Composite Application blade
  5. Enter the Composite Application name and description 
  6. Click the 'Add' button to save the Composite Application
By default, the ServiceBus360 application will have a 'Default Application' that can only be edited.


The next step in creating a Composite Application is to associate the resources with the group. You can logically group any number of resources to one composite application depending on your business requirements. To associate resources:

  1. Log in to your 'ServiceBus360 account'
  2. In the home dashboard, click the 'Manage' button on the Composite Application 
  3. Click the 'Associate Resources' button
  4. Choose the resource type from the tabs and click the checkboxes against the resources to associate
  5. Click the 'Save' button to complete the process