The examples app is intentionally broad: it depends on Rest Client OAuth, Rest Client OAuth Endpoints, and Advanced Redirect URI so it can demonstrate all companion apps.
- Replace sample client IDs, secrets, certificates, tenants, and URLs with values from your own Microsoft Entra app registrations.
- Do not commit real secrets or private keys.
- Verify redirect URIs in Microsoft Entra ID match the redirect implementation you select.
- Grant the required Business Central API permissions and admin consent where needed.
- Enable public client flows if you run the Device Code sample.
The samples use the Business Central API scope:
https://api.businesscentral.dynamics.com/user_impersonation
The examples call:
https://api.businesscentral.dynamics.com/environments/v1.1https://api.businesscentral.dynamics.com/v2.0/<environment>/api/v2.0/companieshttps://api.businesscentral.dynamics.com/v2.0/<environment>/api/v2.0/customers
The endpoint sample expects a configured Table 50351 "Http Endpoint KFM" record. See Endpoint Getting Started for setup details.
The Device Code example uses placeholder client id values. Replace them with your own Microsoft Entra app registration client id, and ensure public client flows are enabled for that registration. Do not reuse another product's public client id (such as Azure CLI) for setup automation or production use.