Overview
For customers who wish to Federate with Microsoft 365 when starting to use Access Control and perform User Synchronization with Active Directory (AD), this article explains the definitions and delivery method for the Synchronization Configuration file used by HENNGE Directory Sync Tool for AD Synchronization.
Notes
- The content of this article is based on the product information as of October 2026 and may be changed without prior notice.
Procedure
1. Determine the criteria for the Users to be synchronized.
The Users to be synchronized can be selected based on the following criteria.
※ The User object must be Valid.
※ If you would like to define criteria other than those listed below, please contact us using the form in Procedure 3.
-
Belongs to a specific OU
※ Users in child OUs under a specific OU will also be synchronized. Multiple OUs can be specified. -
Belongs to a specific security group (※2)
※ Users in child security groups (nested security groups) under a specific security group will not be synchronized.
Therefore, Target Users must belong directly to the specified security group. Multiple security groups can be specified. - The domain of the mail Attribute is a specific Value
- The domain of the UserPrincipalName Attribute is a specific Value
2. Determine the mapping between User Attributes in Access Control and Attributes in AD.
You can select from the following mappings.
※ If you would like to use a mapping other than the options listed below, please contact us using the form in Procedure 3.
| Attribute Value in Access Control | Attribute Value in AD | Description |
| Username |
samAccountName |
The Value of a Username cannot be changed after it has been synchronized. Only alphanumeric characters can be specified. Uppercase and lowercase letters are distinguished. |
| Family name | Surname | |
| Given name | GivenName | |
|
Name |
DisplayName |
|
| Microsoft 365 UPN |
UserPrincipalName |
Specify the Attribute Value in AD that corresponds to the Microsoft 365 UserPrincipalName (UPN). |
| Email Address |
UserPrincipalName |
Example) If the UserPrincipalName (UPN) Attribute in AD is user1@hennge.local and the mail Attribute is user1@hennge.com:
Because the .local domain cannot be used as a Microsoft 365 UserPrincipalName (UPN), which must be globally unique on the internet, it is not appropriate to map the UserPrincipalName (UPN) Attribute in AD to the Microsoft 365 UPN Attribute in Access Control. It is appropriate to map it to the mail Attribute.
3. Once the Target Users for Synchronization and the Attribute Value mapping have been finalized, enter the required information in the form below and Send it.
Please allow several business days for the Synchronization Configuration file to be created.
Notification Form for the HENNGE Directory Sync Tool Synchronization Configuration File
4. Based on the information entered in the form, HENNGE will create the Synchronization Configuration file and send it to you by email. The files to be sent and their descriptions are as follows.
These files will be used in future deployment procedures, so please be sure to save them in a location that can be accessed during deployment.
| File Name | Description |
| config.ini | The Access Control Tenant information and the Attribute Value mapping definitions are registered. |
Translation Disclaimer
This article has been automatically translated from the original Japanese version for your convenience.
While we strive to ensure accuracy, we cannot guarantee its reliability or completeness.
In the event of any discrepancies or questions regarding the content, the official Japanese version shall prevail.