I had the feature last week and thought it had disappeared from my MSDN tenant but turns out it's ediscovery admin only and I was logged in with manager credentials.
The report shows previously created holds (all, who knows? I haven't done comparison that yet).
Agree custodian name on the report would cause confusion and lead people to the wrong conclusion. "Is Bob on hold?" was never the correct wording for the question. This report doesn't also highlight/distinguish between criteria based holds vs "hold the whole location," which moves people further away from being able to answer the Bob question.
The ideal use of this report is for auditing expectation (what do I think is on hold) vs reality (what data locations are affirmatively on preservation hold). Organizations with complex needs should take this information and use it elsewhere to automate that audit.
I had the feature last week and thought it had disappeared from my MSDN tenant but turns out it's ediscovery admin only and I was logged in with manager credentials.
The report shows previously created holds (all, who knows? I haven't done comparison that yet).
Agree custodian name on the report would cause confusion and lead people to the wrong conclusion. "Is Bob on hold?" was never the correct wording for the question. This report doesn't also highlight/distinguish between criteria based holds vs "hold the whole location," which moves people further away from being able to answer the Bob question.
The ideal use of this report is for auditing expectation (what do I think is on hold) vs reality (what data locations are affirmatively on preservation hold). Organizations with complex needs should take this information and use it elsewhere to automate that audit.