On your Azure Tenant the Nimbus Connector needs to be registred to establish a trust relationship between your app and the Microsoft identity platform. đ Refer to: https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app
- Go to portal.azure.com > App Registrations > New registration
- Name your application âLuware PowerAutomate connectorâ Â
âź The end result should look like this:
â Keep this page open as you will need the Application (client) ID to copy for later.
Create the Application SecretÂ
Sometimes also called an application password, a client secret is a string value your app can use in place of a certificate to identity itself.Â
đRefer to https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=client-secret#add-credentials
â Fill out your Flow config as follows. Â
- Use your Application ClientID (copied from the previous step), also use it as the Resource URL.
- Fill out the Client secret with secret created.
- Check via the table below that your App details are correct.
â Note that these values are unique to you. Screenshots below are just examples.
| Field | Description | Filled-out App |
|---|---|---|
| Auth Type | OAuth 2.0Â (automatically filled) |  Â |
| Identity Provider | â Attention: By default Generic OAuth 2 is selected â Select Microsoft Entra ID | |
| Client ID |
Application / Client ID (đsame as Resource URL) â Taken from Azure App Registration (Overview > "Application (client) ID") â See previous step above. |
|
| Client Secret |
Application / Client Secret â Taken from Azure App Registration (Certificates & secrets > Client secrets > New client secret > "Client Secret Value" â See previous step above. â Make sure to paste the secret itself, not the Secret ID. |
|
| Login URL | https://login.windows.net/Â (automatically filled) | |
| Tenant ID | common (automatically filled) | |
| Resource URL |
â Same as Application / Client ID â Taken from Azure App Registration (Overview > "Application (client) ID") â See previous step above. |
|
| Scope | https://graph.microsoft.com/User.Read (automatically filled) | |
| Redirect URL |
https://global.consent.azure-apim.net/redirect âWill be automatically filled in once the connector is created â See next step below. |
Create Connector
- Click "Create connector". âź The Redirect URL will be filled in automatically.
- â Copy the Redirect URL.
- Back in Azure, make sure to enter the Redirect URL in your Application Registration.Â
Show me how...
-
Add the Redirect URL:Â
-
Check your App registration. It should have at least 1 Redirect URL and 1 secret.Â
Test the connector
On the last page of the connector creation process you can test your connector. Click New Connection and sign in with the account with which you will be creating the flows.
đ€ Connection refused? Your tenant admin needs to give consent on User.Read Permissions during the Nimbus App registration. This will allow you to Sign-In on the connector on behalf of the tenant administrator.