Change Summary
Release Date | Release Version | Change Description | Link |
|---|---|---|---|
November, 2025 | 2025.3 | Configure Azure Application Credentials in Product Configurations | Configure Employee Entity for Import from Azure Entra ID into Microsoft Dynamics |
Overview
The TechnoMile Product Suite is natively built on the Microsoft Dynamics 365 platform, transforming the most advanced CRM into a Product Suite ready platform. The suite enables you to manage your Employee records by syncing data from Azure Entra ID into the Employee records on your instance.
You can configure the data to be synced such as the format of the data to be inputted into the Name field and whether records are synced only of Members from Entra ID or both Members and Guests.
Audience
Microsoft Dynamics Administrators
IT Support
Prerequisites
Ensure that TechnoMile's Baseline Package is already installed and configured. The version of this package must be 2025.3 or higher.
Configure Employee Entity for Import from Azure Entra ID into Microsoft Dynamics
IMPORTANT
The current solution includes an existing Power Automate Flow named Entra ID Sync With Employee Entity. However, this flow is to be deprecated in future releases. A new Graph-based Power Automate Flow named Entra ID Sync with Employee for Using Graph, has now been introduced to perform Entra ID synchronization leveraging Microsoft Graph. Ensure that ONLY one Power Automate Flow is active at any given time, as both flows provide the same functionality. Running both simultaneously may result in conflicts or redundant operations.
Login to your Microsoft Dynamics instance.
Click the funnel icon to access Advanced Find.
Advanced Find tab opens.
Select Product Configurations and click Results.
A list of Product Configurations displays.
Specify the JSON Value field as {"FirstName":true} and click Save.
IMPORTANT
This ensures that data from Entra ID is brought into Microsoft Dynamics as First Name being displayed first and Last Name being displayed second in the Name field of an Employee record. You can reverse this order by changing the JSON Value field to {"FirstName":false}.
Specify Value as true and click Save.
IMPORTANT
This ensures that data of both groups of users .i.e. Members and Guests such as Contractors from Entra ID are brought into Microsoft Dynamics as Employee records.
You can also choose to bring in only Member data as Employee records by changing Value to false. If the Value field is set to false, then call the Graph API:
GET https://graph.microsoft.com/v1.0/users/{AzureID}/licenseDetails
From this response, only users who have at least one license are consumed in iteration for creation/update of Employee. Also, ensure that the Directory.Read.All (delegated) permission is added SPN users.Specify Contains Secret as Yes if you are opting for Azure Key Vault, verify that the JSON Value field is blank, and click Save.
Else, specify Contains Secret as No, enter the following syntax into the JSON Value field, and click Save.
NOTE
For GCCH users, MS Token Base URL will be login.microsoftonline.us.
{ "Azure_TenantId": "*********************",
"Azure_ClientSecret": "****************",
"Azure_ClientId": "******************",
"MS_TokenBaseURL": "login.microsoftonline.com" }