Understanding How to Register Client Application in Microsoft Azure AD
Log in to portal.azure.com and perform the following configuration steps:
- Select Azure Active Directory in the left menu.
- Select App registrations.
- Select New application registration.
-
Enter the following information:
- Name: Enter a name for the application. For example,
JDESharePoint
. - Supported account types: Select Accounts in this organizational directory only.
- Redirect URI: This is the endpoint at which your app will receive responses from the Microsoft identity platform. You can enter a value if your organization has a Redirect URI or leave it blank.
- Name: Enter a name for the application. For example,
- Click Register.
After successful registration, you can see the application (client) ID in the Overview pane. You must add a client secret that will enable the app to authenticate user credentials and create a secure connection between EnterpriseOne and Microsoft Azure AD.
- Click Add a certificate or secret for Client credentials.
- Click New client secret.
- In Add a Client Secret, enter a description in the Description field. For example,
ClientSecretforSharePoint
. - In Expires field, use the drop-down to select the duration for which the client secret will be valid. You can use the recommended settings or define a custom value.
- Click Add.
Copy and save the populated secret string under Value. This acts as the application password for the communication between Microsoft Azure AD and EnterpriseOne. You must update the value later while configuring the softcoding record in EnterpriseOne.
After you have registered the client application in Microsoft Azure AD, you must configure the permissions the application needs. Grant the following permissions:
- Application
- Directory
- Files
- Sites
You need Administrator consent for all the above permissions. If you have admin privileges, you can use the option Grant admin consent to provide consent for all the permissions you added. Alternatively, you must request your administrator to grant access to the permissions.
For details on the permissions and consent, see “Introduction to permissions and consent” in Microsoft Azure AD documentation.