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.
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 ??