Setup the Automation Connector for Power Platform
This article explains how to register the nBold Connector as a custom connector for Microsoft Power Platform.
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.
Here is an overview of the overall procedure:
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
App registrationsfrom the left menu
New registrationfrom the top bar
- Give the app a name, such as:
nBold Power Platform 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:
- From the
Overviewmenu, copy the
Application (client) ID, and keep it as we're gonna reuse it later.
- Open the
- Ensure that the
Access tokens (used for implicit flows)and
ID tokens (used for implicit and hybrid flows)options are checked from the
Implicit grant and hybrid flowssection, and save your updates if required.
- Open the
Certificates and secretsmenu 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 Power Platform Connector client secret
- Select the expiration option, and click
- Copy the
Secret Valuevalue (be careful, it will only be shown once), and keep it as we're gonna reuse it later.
You should use the
Secret Value, not the
- Open the
API permissionsfrom the left menu and click
Add a permissionfrom the top bar
Microsoft Graph, then
- From the permissions list, select:
- OpenId permissions >
- Directory >
- Group >
- InformationProtectionPolicy >
- Mail >
- User >
- OpenId permissions >
- Then click
Grant admin consent for...then
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. Import the nBold OpenAPI definition
Now that we've created the app registration, we're gonna use it to create our custom connector.
- To import the nBold API OpenAPI definitions for Power Automate and Power Apps, go to PowerApps or Power Automate.
The custom connector you're about to create will be available for both PowerApps and Power Automate, as they're sharing the same list of connectors.
- In the navigation pane, select
New custom connectorthen choose
Import an OpenAPI from URL
- Give your connector a name, such as :
- Paste this URL:
- Upload the connector logo that you can download from:
- Set the icon background color to:
- Ensure that the authentication type is set to
OAuth 2.0and the identity provider is set to
Azure Active Directory
- Paste the previously copied
- 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:
Create connector, then
3. Update the Power Platform Connector
To update your Power Platform connector:
- Open the updated connector definition from:
- Copy the whole content
- From Power Apps or Power Automate, open your custom connector from the
Data \ Custom connectorsmenu
- Click on
- From the left page, replace the content by pasting the updated connector definition
4. Next Steps
Here are a few interesting articles that may give you some guidelines and new ideas on how to use the nBold Connector:
- Top 5 Power Automate Flow Examples for Microsoft Teams - nBold
- Get started with Power Automate
- Power BI with Microsoft Teams: How to Manage Reports Effectively :::
Update your connector authentication
In case your Power Automate flow stops working, one of the possible reasons for that issue can be an expiration of a Power Automate connector authentification.
You can check it by looking at your client secret expiration date in Azure Active Directory.
To check it:
- Go to App registration in your Azure Active Directory portal
- Select your connector
- Click on Certificates & Secrets and check if your client secret has expired.
- If it is the case, you need to modify a secret value in the already excising connector in Power Automate, so that it is valid for 24 months.
Actions to do :
- Go to Azure Active Directory portal ==> App registration ==> Select your connector ==> Certificates & Secrets
- Add a new client secret that expires in 24 months
And then re-try the authentification:
- Go to Power Automate
- Click on Data ==> Custom Connectors
- Select your nBold connector
- Click on Edit
- Go to the Security tab, scroll down, and click edit
- Change Client secret with a new secret value from a new client secret that you just created in Azure Active Directory.
- Update a connector
It should be all up and running now 😉