Holds, collections and review
Implementation so legal and compliance can actually run a matter — not a licence left unconfigured.

Microsoft Purview eDiscovery can place holds, collect content and support review. Enabling the workload is not an implementation. The work is deciding who may open a case, how a hold is authorised, how collections are scoped, and how review happens without becoming an ungoverned export.
Ghani Governance configures that path for UK organisations. We do not invent litigation case studies, and we are not a law firm. Product reference: Microsoft’s eDiscovery documentation.
Who can create a case, place a hold, collect, or review — named, not “everyone in IT”.
How a legal or investigation hold is requested, applied and released, with a written purpose.
Scoping a collection so it matches the matter, rather than pulling an entire mailbox estate.
Where licences allow, review-set workflow; where they do not, an honest path that does not pretend Premium features exist.
How a matter is opened, handed to counsel if instructed, and closed — written for the people who will do it.
All Purview services · UK and Greater Manchester service area
Licensing, audit, permissions, and whether any search or hold already exists.
Who authorises a hold, who collects, who reviews, who closes.
Cases, role groups and a pilot collection on a harmless scope.
Hold, collect, review or export — then check what was missed or over-collected.
Documented steps your legal or compliance owner can repeat.
No. We implement Microsoft Purview eDiscovery so your legal, compliance or instructed firm can place holds, collect and review. We do not conduct litigation or give legal advice on a matter.
Content search finds items. eDiscovery adds holds, collections, review (where licensed) and a documented chain so a matter can be run without ad-hoc exports. Implementation is making that path usable, not turning search on.
Not always. Holds and collections cover many matters. Review sets and advanced analytics depend on licensing and the kind of review you actually do. We say what your licences support before designing around a Premium feature.
A scoping conversation about what you need to protect, what is already configured, and what must not break.