This can be caused by native Office 365 issues, or DMA service problems.
1. Check if O365 natively works ok
- Open https://portal.office.com/admin/default.aspx#ActiveUsersPage and see if the problem user exists. If they do go into properties and switch between the tab. Make sure no errors occur.
- On the DMA machine, install the Azure Active Directory Module for Powershell from http://technet.microsoft.com/en-us/library/hh974317.aspx and run the following command
Get-MsolUser -ObjectId $(Get-MsolUser -UserPrincipalName user.name@company.com).ObjectId
2. If above tests work, restart the DMA service and check if it solves the problem.
3. If there are still issues, on the DMA machine set the following registry value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\QsDMAgent\Config]
"LogLevel"="Full"
restart the service, rerun the migration and collect the debug logs to troubleshoot further
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center