The SCIM microservice uses Azure AD authentication to call the Azure API. As part of the process for deploying the SCIM microservice, a service principal application used to authenticate the App Service that hosts the microservice must be registered in Azure.
Register the app
Log in to your Azure portal as a user with the necessary permissions to create an application in Azure AD.
In Azure, navigate to your Azure Active Directory.
On the Azure navbar, click App registrations.
On the App registrations page, click New registration.
Name the application, select the scope for the application (single or multitenant) and click Register.
Once the application is registered, copy the Application (client) ID, Directory (tenant) ID and Object ID from the Overview page. These values are used when configuring the SCIM app service.
The next step is to upload the base-64 encoded certificate that you have selected to authenticate to the application.The public key certificate that you upload to Azure must have a corresponding private key in the EmpowerID certificate store; otherwise, an error will occur when calling Azure’s API.
If you don’t have a certificate to use for authentication, you can create a self-signed certificate from IIS and export the certificate as .cert, .pem, or .crt format. For help with these tasks, see https://aboutssl.org/how-to-create-a-self-signed-certificate-in-iis/ and https://support.globalsign.com/ssl/ssl-certificates-installation/import-and-export-certificate-microsoft-windows.
Under Manage, click Certificates & secrets.
Under Certificates, click Upload certificate and upload the base-64 encoded certificate.
Under Client secrets, click New client secret. The secret is used by the application to prove its identity when requesting a token.
Enter a Description for the client secret, select when the secret Expires and then click Add.
Copy the secret. You will use it when configuring the SCIM app service.