@Oltmann, Kevin Thank you for reaching out to us, would like to review your configuration over the teams call so that we assist you better, however you mentioned above that you a created a sync rule to stop the export, which is not clear to me ?
If you are in the migration phase why not use staging mode option to stop the exports completely from the entra connect server.
It seems like the accidental delete prevention feature in Entra Connect cloud sync has been triggered due to the number of objects staged for deletion exceeding the threshold. This feature is designed to prevent accidental deletions of large numbers of objects in your on-premises directory that would affect many users and groups.
Regarding the objects that are staged for deletion, it's possible that they were inadvertently included in the scoping filter of Cloud Sync. It's also possible that they were previously synchronized with Entra ID Connect and were not properly excluded from the synchronization scope of Cloud Sync.
To investigate further, you can check the synchronization rules and scoping filters in both Entra ID Connect and Cloud Sync to ensure that the objects in question are properly excluded from synchronization. You can also review the logs and notifications in Cloud Sync to determine which objects are staged for deletion and why.
Before taking any action, it's recommended to thoroughly investigate the issue and understand the potential impact of deleting the objects.
We can connect offline and discuss further on this and understand the configuration and figure out how object deletion is being triggered.