BeyondERP.Newsletter
Menu

Setup step on the Microsoft Entra ID applications page · System administration

Set up Microsoft Entra ID applications

Use this page to let external systems connect securely to the system's services, running under the user account you choose.

Used by
Information technology manager
Business process
Administer system features
Menu item
SysAADClientTable
Main table
SysAADClientTable
Data entity
SysAADClientTableEntity
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA setup page where you register external applications by their Microsoft Entra client ID and link each one to a user account.
What you do hereUse this page to let external systems connect securely to the system's services, running under the user account you choose.
ExampleFor example, to let an external contract lifecycle management system use the data entities, an administrator adds its client ID and maps it to a service account that has the CLM integration role.
Microsoft Entra ID applications page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processAdminister system features
Menu pathSystem administration › Setup › Microsoft Entra ID applications
Set up firstUsers Microsoft Learn Set up Users
Used next byData management Microsoft Learn
Related pagesAssign users to roles Microsoft Learn
In this process Set up Shared categories · Set up Electronic signature parameters
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Set up Microsoft Entra ID applications

Use this page to let external systems connect securely to the system's services, running under the user account you choose.

Steps from Microsoft

  1. Go to System administration > Setup > Microsoft Entra ID applications.
  2. Select New.
  3. In the Client Id field, enter the application ID registered in Microsoft Entra ID.
  4. In the Name field, enter a name for the application.
  5. In the User ID field, select the service account the application runs as.
  6. Select Save.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExampleTable column
Client IdThe application (client) ID registered in Microsoft Entra ID.Microsoft Learn The application (client) ID GUID from the app registrationAADClientId
NameA descriptive name for the application.Microsoft Learn Name
User IDThe user account the application runs under; a dedicated service account is best.Microsoft Learn A dedicated integration user, not AdminUserId

Common errors and fixes

MessageWhat to do
The external app gets a token but every call is refusedThe client ID isn't on this page or its User ID lacks the roles the calls need. Add the record and give the service account the roles. Microsoft Learn

Test checklist

  1. Register the app in Microsoft Entra ID and note its client ID.
  2. Add a record with that Client Id, a Name and a dedicated service account in User ID.
  3. From the external app, get a token and read a data entity through OData.
  4. Try an action the service account's roles don't allow and check that it's refused.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Microsoft Entra ID applicationsOne record per external application, linked to a dedicated service account user that has only the roles the integration needsService calls run as the user selected in User ID. Learn uses Admin only as an example and says that, as a better practice, you should provision a dedicated service account with the correct permissions.Which user does each application run as?Linking the app to the Admin user, so the integration can do everything an administrator can.Test: The integration is limited to its service account's roles

Feature management and licence

Licence or add-inOn this system the page opens for Information technology manager. IT administrators register applications. No Feature management feature needs to be turned on for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyShared: the same records are used by every legal entity. Microsoft data model
Can it be undoneReversible: The User ID can be changed or the record removed at any time; the external app then runs as the new user or can't connect.
If you change it laterCalls from the application run with the security of the user in User ID, so that user's roles decide what the integration can read and change. Microsoft Learn
Technical architect

6Technical

Menu itemSysAADClientTable Checked in Dynamics 365
FormSysAADClientTable Checked in Dynamics 365
TableSysAADClientTableShown as “Microsoft Entra ID applications” in Record infoChecked in Dynamics 365
Data entitiesSysAADClientTableEntityAzure active directory applications Checked in Dynamics 365
Who can open itPrivilegesMicrosoft Entra ID applications SysAADClientTableMaintainDutiesMaintain system settings SysServerSettingsMaintain
1 security roleInformation technology manager SysServerITManager
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itInformation technology manager SysServerITManagerGive people one of these roles. On this system, 1 role can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=SysAADClientTable
Integrate withSysAADClientTableEntity data entity Checked in Dynamics 365
Data migrationSysAADClientTableEntity (Azure active directory applications): shared by all companies, in Microsoft's default template 400 - Warehouse management.Load order: Microsoft's default template 400 - Warehouse management loads Azure active directory applications at execution unit 1, level 30, sequence 10. Load the users first, because each record names a user.Load first: Users (User information)Checked in Dynamics 365
Table definitionSysAADClientTable columns and relations Microsoft data model
Everyone

8Sources

To cite this step: SA-SETUP-140, Set up Microsoft Entra ID applications. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SA-SETUP-140