A subject access request reaches IT as a ticket from the privacy team: find everything we hold about this person in Microsoft 365 and get it out as files. The tool is eDiscovery in the Microsoft Purview portal, and the whole job is four steps and a hand-over.
Your part ends when the export lands. The privacy team then has to remove other people's personal data from every file before anything goes to the requester, and that step is usually where the one-month clock is lost. This page is written so the export you produce makes that step possible.
Video lesson. Watch the same four steps worked through on an example request: the route and licence, a search scoped to one person, the export settings, the hand-over, and a recording of where the export goes next.
Step 1: Pick the Purview route and check the licence
Microsoft Purview offers three eDiscovery solutions: Content Search, eDiscovery (Standard) and eDiscovery (Premium). The classic experiences were retired on 31 August 2025, so everything now runs in the new eDiscovery experience in the Purview portal. For a subject access request you need search and export, which Content Search and eDiscovery (Standard) both provide. Standard adds a case with its own members and holds, which is the right container for a request that may be questioned later.
Licensing: Microsoft states that both administrators and users working eDiscovery cases need a Microsoft 365 E3 or E5 licence, and that eDiscovery (Premium) needs Microsoft 365 E5 or a related E5 add-on (E5 Compliance, or E5 eDiscovery and Audit). Premium adds review sets, custodian workflow and analytics. None of those is required to collect and export a DSAR, so an E3 tenant can run the whole request on Standard. Permissions are assigned through the eDiscovery Manager role group; you can see your own on the eDiscovery overview page.
One thing Premium does have is a review-set Annotate view with area redactions. It is manual, one document at a time, and the committed output is a PDF. Our page Can Microsoft Purview redact documents? explains why that is not a plan for a mailbox-sized request. If your privacy team used Priva Subject Rights Requests, Microsoft moved that work to eDiscovery (Premium) in May 2026.
Step 2: Search for one person, not the whole tenant
A case search can cover Exchange Online mailboxes, SharePoint sites, OneDrive accounts, Microsoft Teams, Microsoft 365 Groups and Viva Engage in one query. Microsoft's former User Data Search tool is retired; its job now sits in ordinary eDiscovery search. Two kinds of location matter for a DSAR. The requester's own mailbox and OneDrive are added as data sources by name, SMTP address or site URL, and everything in them is in scope. Other people's mailboxes, shared sites and Teams channels are searched for the requester's identifiers: full name, email address, employee number, and any aliases the privacy team gives you.
Scope is the privacy team's decision, not yours, and the law backs them: UK GDPR requires a reasonable and proportionate search, and the ICO's guidance explains what that means. Ask for the identifiers and the date range in writing, run the query, and read the statistics before you export. The hit counts by location tell the privacy team whether the scope is right, and a search you can describe in one paragraph is the one that survives a complaint. Our guide to reasonable and proportionate DSAR searches covers the standard.
Step 3: Export with attachments intact
The export options decide whether the privacy team receives a complete set or a partial one. Choose PSTs for messages, not individual .msg files, because a .msg export does not carry the content of attached messages. Set the PST package size to 1 GB or 2 GB rather than the 5 GB default. Turn on cloud attachments at their latest version, or files that were shared as links never reach the disclosure. SharePoint and OneDrive files come out as native documents; take the latest version unless the privacy team asks for history. For Teams, the option to organise conversations into HTML transcripts gives reviewers threaded chats with participants and timestamps.
Include partially indexed items. That set holds scanned and image-only documents, and the default leaves them out. Keep folder and path of source, friendly names, and separate folders per location, and condense paths to the 259-character limit. Export items with the items report, not the report alone. The full settings table lists every option with the reason for each.
Timing: an export that runs for more than seven days is cancelled automatically, so split a large mailbox by date range. Packages expire 14 days after creation and cannot be recovered, so download promptly. Downloads run through the browser from the case's Exports tab; Microsoft recommends the current Edge and a tool such as 7-Zip for the ZIP packages.
Step 4: Hand over, and know what happens next
What you hand to the privacy team is the ZIP packages, the items.csv report, and a one-paragraph note of the locations, identifiers and date range you searched. That note becomes part of the record of the response. Keep your own copy of the export until the response has gone out and the retention period the privacy team sets has passed.
What happens next is redaction. Every file in the export is read for other people's personal data: colleagues named in emails, third parties in attachments, other staff in HR notes. The requester's own information must stay; everyone else's must go, and each decision needs a record. SafeRedact takes the export as you produced it, in 11 file types including PST, reads attachments as documents in their own right, keeps the requester's data, flags other people's for a reviewer to decide once per person, and writes an audit trail and review decision log into the disclosure pack. Documents are processed in the browser; only extracted text and the case's data subject details are sent for detection, and no document is stored on our servers. Mailboxes up to 2 GB and 25,000 messages per PST file are supported, which is why the PST package size in step 3 matters.
If you are the one forwarding this page, the two things the privacy team will ask you for are the export in PST form with attachments included, and the search note. Get those right and the rest of the request is theirs to run.
Hand the Export to Something Built for It
Run the Purview export through detection and review in the browser. Evaluate on 500 of your own documents first, free.
Set up your organisationRelated Guides
Sources
- Microsoft Learn, eDiscovery solutions in Microsoft Purview (Content Search, Standard, Premium; licensing note)
- Microsoft Learn, eDiscovery features and components (licence requirement for admins and users, permissions)
- Microsoft Learn, Create a search for a case in eDiscovery (searchable locations, data sources)
- Microsoft Learn, Export search results in eDiscovery (formats, package sizes, 7-day and 14-day limits)
- Microsoft Learn, Group and view items in a review set (Annotate view and committed redactions)
- ICO, right of access: how do we find and retrieve the relevant information?
Microsoft, Microsoft 365, Microsoft Purview, SharePoint, Exchange Online, OneDrive, Teams and Viva Engage are trademarks of Microsoft Corporation. SafeRedact is not affiliated with or endorsed by Microsoft. Purview behaviour and licensing described here reflect Microsoft's public documentation as of November 2026; consult Microsoft Learn and your licensing agreement for the current position. This page is informational, not legal advice.