Skip Public Folder Objects in AAD Sync Requests vs Crashing Sync
Sync jobs fail when a public folder is present
Change AAD Connect such that it skips over a public folder object, reports the skipped object in an event log, and keeps syncing
Rob de Jong (Azure AD IAM) commented
Makes sense, we're investigating this as a bug. No timeline to share right now.
Chris Allen commented
This makes sense to me. We should not crash the whole sync job due to an invalid recipient in a group. Let's just skip the invalid recipient and let the rest of the sync continue. With proper reporting in the event logs, we should be able to then clean it up and prevent it from erroring in the future. Please up vote this request.