So much has changed. One thing I've noticed recently is how often I search for something online and get no results. None. This happens most often when pasting error messages to a Google search inside of quotes. "Surely I cannot be the only one who's searched for this" is something I say out-loud on a regular basis. What happened? How is it possible that Google has not seen an error message before and suggests to remove the quotes? Maybe more people are searching and less people are posting. I don't know why else this may be. So here. I post an error and share some frustration.
Error: DeletingCloudOnlyObjectNotAllowed
This error indicates that a deleted object was recovered from the recycle bin in Azure AD before Azure AD Connect was able to confirm its deletion. Please delete the recovered object in Azure AD to fix this issue.
This is an AAD Connect sync issue related to Public Folders that are nowhere. I cannot find them in the cloud and they don't exist in local AD. I have been in contact with MS Support for months and have worked with two different engineers so far. I've deleted public folders from EAC and ran multiple syncs - deltas, initials, and fulls. I have used Remove-ADSyncToolsAadObject naively thinking that would do the trick, but it was just a different route to the same results.
Microsoft's error message points to support docs that are of no help. For example, browse the docs and see if you can find the error message above. In fact, search the web for DeletingCloudOnlyObjectNotAllowed. Google returns only two pages of results. Much of it is "Microsoft Answers" and is unrelated to my, apparently, one-of-a-kind issue. None of the results are to official MS documentation. Oh, there is a GitHub result buried in there, but it still gets me nowhere.
I'm not saying this is Google's fault. The content apparently isn't out there.
With the present and future being cloud based, it would be great if there were more tools to give insight into cloud based products. Take Azure AD for example. Where is the equivalent of ADSI Edit? PowerShell is great, but not everything is exposed which tends to leave us scratching our heads from time to time when troubleshooting things that should not be this hard to resolve.
If you found this while searching the same error, or if you've had this error before, I'd love to hear if and how you resolved it.
I guess that's all I got. Maybe in another decade or so I'll have something else to say.
