'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix AWS Managed Directory Not Updating After Microsoft Entra Connect Sync
Question details
Users are not appearing in an AWS managed directory despite Microsoft Entra Connect Sync reporting a successful synchronization.
- Product
- Microsoft Entra Connect
- Device & OS
- not provided
- Scenario
- Synchronizing hybrid identities between Microsoft Entra and an AWS managed directory.
- Observed behavior
- Synchronization reports success, but users do not appear. Duplicate-attribute errors and Event Viewer export error 6100 are observed during the process.
Ensure you have administrative access to both your Microsoft Entra ID and AWS Managed Directory environments to properly review sync logs and Event Viewer details.
Consult the Microsoft Exchange Hybrid Management Support Team
Since this involves complex hybrid identity and directory synchronization issues like duplicate attributes and error 6100, reaching out to the dedicated Microsoft Hybrid Management team is the most effective approach.
Export error 6100 and duplicate-attribute conflicts often indicate deeper issues with directory synchronization permissions or hybrid identity setups. Specialized assistance from Microsoft is recommended to investigate AWS directory integrations.
Open the Event Viewer on your sync server and collect detailed logs about the duplicate-attribute errors and export error 6100.
Visit the official Microsoft Exchange Hybrid Management Q&A forum at https://learn.microsoft.com/en-us/answers/tags/377/office-exchange-hybrid-management.
Click 'Ask a question' and provide a detailed description of your AWS directory integration issue, including permissions, export errors, and your synchronization logs, so the support agent can investigate.
Looking for a Lightweight Office Suite?
While IT administrators troubleshoot complex directory integrations like Microsoft Entra and AWS, you can rely on WPS Office for your daily documentation needs. WPS Office is a free, lightweight, and highly compatible alternative to Microsoft Office, perfect for creating IT reports, managing spreadsheets, and seamless teamwork.
- 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install the Software: Run the installer and follow the on-screen prompts to set up WPS Office on your computer.
- 3. Open and Edit Files: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office documents without any format loss.
Frequently Asked Questions
What does Event Viewer export error 6100 mean in Microsoft Entra Connect?
Error 6100 typically indicates an issue during the export phase of directory synchronization. It is often related to duplicate attributes or permission issues that prevent objects from being written correctly to the target directory.
Why does Entra Connect report success but users don't appear in AWS?
The synchronization process might successfully read and process data from the source directory (reporting a successful sync run), but fail to write to the destination (AWS managed directory) due to missing target permissions or unresolved attribute conflicts.
Can I resolve duplicate-attribute errors manually?
Yes, you can resolve duplicate-attribute errors by identifying the conflicting objects using the IdFix tool or Event Viewer logs, and modifying or removing the duplicate attributes directly in your on-premises Active Directory before forcing another sync.
