Connecting the App
With the Entra app registration in place, the last step is to enter its values on the Elevate Approvals Setup page, turn the connection on, and confirm it works. All of this lives directly on the Setup page; there is no separate endpoint record to create.
Set up the endpoint
Enter these fields:
| Field | What to enter | Where it comes from |
|---|---|---|
| Endpoint Code | Any label you like (for example PROD) | You choose it |
| Base URL | The Elevate API's base URL for your environment | Equerra provides this during onboarding |
| OAuth Token Endpoint URL | https://login.microsoftonline.com/{your-tenant-id}/oauth2/v2.0/token, using your own Directory (tenant) ID | Your own Entra tenant, always, even against Equerra's Elevate API |
| OAuth Client ID | Application (client) ID | Your own app registration |
| Client Secret | The secret Value (not the Secret ID) | Your own app registration |
| OAuth Scope | Equerra's Elevate API Application ID URI plus /.default, for example api://<equerra-app-id>/.default | Equerra's app registration; ask Equerra to confirm it for your target environment |
| Enabled | Set to true | You choose it |
See Entra App Registration for how to obtain the values that come from your own app registration.
Once every field is entered:
- Choose Test Connection in the actions ribbon. If the portal answers with a success response, the connection is good. If it fails, see Troubleshooting.
The Tenant ID field is read-only. It fills in once the portal accepts the first sync from this connector.
Once Test Connection succeeds, continue with the Entity Registry to choose what to sync, or jump to the Onboarding Checklist in the Admin Guide for the full order of setup steps across both BC and the portal.