Hello Anon4343,
Thank you for the information.
Few groups from on-prem AD are not syncing to azure.
This is due to empty information on "Display Name" attribute. By filling the field "Display Name" these groups are syncing to Entra ID.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We've made changes to an on-premises Active Directory group and not all of the changes are synchronizing.
We're using the Entra Cloud Sync Azure AD Connect Provisioning Agent version 1.1.1586.0 . This is the latest version.
In the Cloud Sync provisioning logs, we can see that it's referencing the new on-premises Active Directory group name. How do we rename the Entra ID group name to match?
Hello Anon4343,
Thank you for the information.
Few groups from on-prem AD are not syncing to azure.
This is due to empty information on "Display Name" attribute. By filling the field "Display Name" these groups are syncing to Entra ID.
Hello Anon4343,
Thank you for posting the query in Microsoft Q&A.
Renaming on-premises Active Directory group name not syncing to Entra ID while using cloud sync tool.
This issue occurs for one of the following reasons:
We suggest you to use the IdFix DirSync Error Remediation Tool to find objects and errors that prevent synchronization to Microsoft Entra ID. It displays object attribute values that would be reported as errors by the supported directory synchronization tool.
Please follow the steps mentioned in the below document to run IdFix tool.
https://microsoft.github.io/idfix/Step%203%20-%20Query%20and%20fix%20invalid%20attributes/
Please refer the below document
Entra Cloud Sync contains a default attribute mapping for DisplayName. The attribute mapping is an Expression such as:
IIF(IsPresent([displayName]), [displayName], [cn])
Take a look at the "Apply this mapping" setting and make sure it is set to Always, not Only During Object Creation.
Also, what happens when you do a Provision on Demand against that object?
We opened a ticket with Microsoft support and found that filling in the DisplayName attribute of the group resolved the issue.