Data Consistency Score (DCS) is a (somewhat) new feature for Office 365 migrations that scores the fidelity of migrated data, allowing admins to identify inconsistencies and integrity issues between ...
Updated May 27, 2021
Version 1.0
Blog Post
16 MIN READ
Migrations with Data Consistency Score (DCS) – more than you ever wanted to know!
Mihai_Grigoruta
Microsoft
Microsoft
1. DCS will be performed by EXO right after the submitting the batch and before starting the actual migration, right?
DCS will be used in the entire migration process since we check the items that will be migrated. DCS will be used after submitting and starting the batch if no Bad Items or Large Items Limit are specified. As items are being copied during migration, the score is dynamically calculated during the entire migration process. When score is Investigate or Poor, action needs to be taken by admin in order to complete the migration (switchover if we are talking about Hybrid or Google Workspace migrations that need completion of the batch).
2. The reports to be pulled and inspected to "investigate" will be before performing the actual data migration, or during migration or after migration at 95%? Which one is it?
Strictly speaking from DCS point of view, you would need to inspect the migration reports if you receive a Score of Investigate or Poor during migration (at any phase you get that). When Score is Good (not Perfect) you might want to check why is that. Some parts of the report (Mailbox verification / missing items) will only be available after you try to complete once. However normal bad items and large items will be available for inspection as soon as they are encountered.
3. Do you have a TechCommunity blog with troubleshooting mailbox corruption caused by Outlook client? Please share.. Time to ask users to cleanup their mess!
We are not aware of such article or fact (Outlook client causing corruptions at the mailbox level).
4. If Outlook client causes mailbox corruption, why can't server win by reparing it and pushing it down to the client? The "Exchange" idea of "sync across all devices" is defeated here, is it?
As mentioned above, we are not sure of what Mailbox corruptions caused by Outlook client you refer to. Regardless of how the corruption was introduced, by which client, as the corruption already took place, we can't repair it or migrate it, it is invalid and we wouldn't know at server side what would be the desired valid values to be set there.