clear dirsync errors from dashboard
within settings ---> dirsync errors, there is no way to clear out old errors that have been resolved. We also get weekly emails saying we have dirsync errors in which we do not have any current ones, rather it is a summary of old errors we have that makes us think we have current synchronization errors. This has came up on a support posting: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_other-mso_o365b/how-to-clear-dirsync-error-report/97b43be7-5155-4a75-b69e-9782efdd161b
please add a way to clear out old errors from this dashboard.
Fix this already.
I just spent far too much time attempting to investigate sync errors which were already resolved. Please reconsider allowing us to clear these alerts. This is extremely user unfriendly.
The Azure AD Connect card in the Office 365 admin center has a red icon warning message that 'We found DirSync object errors <current time>'. Clicking on that warning lists the errors, but only by clicking each individually can you view the REAL time these errors were last found during sync (which was days ago). Both have long since been resolved, but nothing within our admin panel indicates that.
The red status for DirSync in the admin center does not make sense for resolved errors. Furthermore, reporting the current date or time in that warning message instead of the actual date/time of the last error is worse than useless. This masks new, unresolved errors by training admins to ignore the DirSync status altogether.
I am also still having this with errors dating back to February. just wasted over an hour trying to find a problem that wasn't even there.
Henrik Hansen commented
Its really annoying, especially if you have 10 or more old errors which have been resolved, i just spent 3 working days on trying to fix this with no luck.
JC Ryan commented
This has been an issue all year. Once a week I get asked when this error is going to be fixed and I fixed it months ago.
Same issue here. Dashboard shows old DirSync errors that were resolved months ago. Syncs since have completed without issue but it's definitely frustrating that the dashboard continually seems to indicate there is an issue when it's just old issues that have already been resolved.
Can't believe this is still a problem. Come on Microsoft... Fix the **** problem.
This only began to be a problem for us around the end of 2018. Have opened support tickets with Microsoft & have been referred here of all places. This is not a "feature request" - something isn't working that was working. For now, the only workaround I have is to remove the object from an OU that syncs, allow sync to occur, and then put it back to its original location. Sync error gone. Pretty annoying.
Gio Pineda commented
This is very annoying. it needs to get fixed sooner rather than later. It makes no sense that we cant get rid of the error if there really isnt a DirSync problem
I agree this is an annoying issue, there should be an option to clear a sync error message once the issue has been resolved.
We also have this problem. DirSync errors are resolved, but the dashboard still shows the (old) errors. Very confusing! How can we clear the errors from the dashboard?
We are receiving this constantly and all previous errors still remain months after they have been resolved.
It has to be checked daily and the warning is constantly on the dashboard.
Any fix to this bug on the roadmap?
Tessa Thompson commented
I just worked with support on this and you don't have to purge and re-create but you do have to update the attribute that was found to be duped, let it sync which will clear it, then you can set it back to the original value and it won't get flagged again if the dupe was fixed. Still klugey, these should auto-fix, but much better than purging prod objects.
Please add this feature. Waiting 90 days or having to purge the object and re-create it is annoying. Thanks.
any update on this?
We also have this issue. Two errors will not clear, even after I have worked with a Microsoft rep to make sure the account does not have any of the proxy email addresses.
Honestly this shouldn't even be a thing. The error should either clear automatically once the error condition is resolved, and then archived into another section, or just clicking on errors (whether or not there is one) will show you previous ones, with an option to manually clear it for those of us who don't want to wait for propagation to occur and this to rectify itself.
It's messy and as an MSP who answers to clients, trying to sell this as a "feature" rather than a missing implementation is just not going to fly, it seems like we are ignoring problems with their Tenant in their eyes.
I have the same issue now.
And we're 8 month later!
Does Microsoft even listen to Uservoice ??