Skip to main content

Setup the Automation Connector for Logic Apps

This article explains how to register the nBold Connector as a custom connector for Azure Logic Apps.

⏱ Expected Duration

Creating the custom connector only requires a few operations that are described hereafter as a detailed step-by-step procedure. Assuming you have all the required access and permissions to execute it properly, it should take less than 10 minutes.

Procedure Overview

Here is an overview of the overall procedure:

graph LR %% Nodes s([Start]) subgraph azad[Azure AD] appreg(1. AD App Registration) end subgraph azla[Azure Logic Apps] customconnector(2. Create Azure Resource) importopenapi(3. OpenAPI import) logicapp(4. Logic App) end e([End]) %% Styles classDef startend fill:#9099d8, stroke-width:0px; class s startend class e startend %% Links s --> appreg appreg -->|Client id & secret| customconnector customconnector --> |Configure| importopenapi importopenapi --> |Use| logicapp logicapp --> e

1. Create a new app registration in Azure Active Directory

To securely access your Microsoft 365 environment through the Microsoft Graph APIs, the first step is to create a dedicated app registration. An Azure AD app registration identifies a third-party app such as nBold, and defines the permissions you wan to grant to it. To learn more, you can refer to How and why applications are added to Azure AD.

To create a new app registration, follow these steps:

  • Open your Azure Active Directory portal
  • Select App registrations from the left menu
  • Click New registration from the top bar
  • Give the app a name, such as:

nBold Logic Apps Connector

  • Select the option Accounts in this organizational directory only, as you want to restrict access to your own tenant.
  • Use this web redirection URL:

  • Click Register
  • From the Overview menu, copy the Application (client) ID, and keep it as we're gonna reuse it later.
  • Open the Authentication menu
  • Ensure that the Access tokens (used for implicit flows) and ID tokens (used for implicit and hybrid flows) options are chacked from the Implicit grant and hybrid flows section, and save your updates if required.
  • Open the Certificates and secrets menu and click New client secret. A client secret is a kind of a password for your app, so manage it carefully.
  • Give a name to your client secret such as:

nBold Logic Apps Connector client secret

  • Select the expiration option, and click Add
  • Copy the Client secret value (be careful, it will only be shown once), and keep it as we're gonna reuse it later.
  • Open the API permissions from the left menu and click Add a permission from the top bar
  • Select Microsoft Graph, then Delegated permissions
  • From the permissions list, select:
    • OpenId permissions >
      • email
      • offline_access
      • openid
      • profile
    • Directory >
      • Directory.AccessAsUser.All
    • Group >
      • Group.ReadWrite.All
    • InformationProtectionPolicy >
      • InformationProtectionPolicy.Read
    • Mail >
      • Mail.Send
    • User >
      • User.Read
      • User.Read.All
  • Click Add permissions
  • Then click Grant admin consent for... then Yes

You're done, you've created your app registration for the nBold Connector. You should also have saved for later the Application (client) ID and Client secret that we're gonna use in the next steps.

2. Create an Azure Custom Connector Resource

In Azure Logic Apps, you must first create the custom connector resource (steps below) before defining the behavior of the connector using an OpenAPI definition.

  • In the Azure portal, on the Azure services menu, choose Create a resource.
  • In New, enter logic apps custom connector in the search box as your filter. Select Logic Apps Custom Connector from the drop-down box.
  • In Logic Apps Custom Connector, select Create.
  • Provide details for registering your connector. When you're done, choose Review + create.

Once you've created the custom connector resource, the custom connector menu should open automatically. If it doesn't, you can go to the subscription and resource group you selected and open it directly. Now that you have a custom connector, you can define the connector's behavior.

3. Import the nBold OpenAPI definition

Now that we've created both the app registration and the logic apps resource, we're gonna use it to create our custom connector.

  • Go to the Azure portal, and open the Logic Apps connector you created earlier in Create an Azure Logic Apps custom connector.
  • In your connector's menu, choose Logic Apps Connector, then choose Edit.
  • Under Custom connectors, select REST
  • From Import mode, select OpenAPI URL and and paste this URL:

  • Click Import
  • From the General information section, give your connector a name, such as:


  • Upload the connector logo that you can download from:

  • Set the icon background color to:


  • Click Security
  • Ensure that the authentication type is set to OAuth 2.0 and the identity provider is set to Azure Active Directory
  • Paste the previously copied Client id and Client secret
  • Ensure that the login url is set to:

  • Ensure that the tenant ID is set to:


  • Set the resource URL to:

  • Set the scope to:

  • Click Update connector
  • From the Security page, copy the generated Redirect URL, and keep it as we're gonna reuse it later.
  • Navigate back to your app registration, open the Authentication menu
  • From the Web section, add the previously copied URL to the list of Redirect URIs
  • Click Save

4. Next Steps

Now that you've created the nBold connector, you can use it from your Azure Logic Apps environment. See the available Triggers and Actions for reference.

💡 To Go Further

Here are a few interesting articles that may give you some guidelines and new ideas on how to use the the nBold Connector: