Alex Morgan’s data subject access request has reached IT as a ticket from the privacy team: find everything the organisation holds about Alex in Microsoft 365 and get it out as files. Lesson 1 and Lesson 2 covered the review of two HR records. This lesson follows the ticket through Microsoft Purview eDiscovery to the review tool, from the IT side.
The clock is the reason the export matters. The organisation has one month to respond. IT’s 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 Alex, and that step is where the month is usually lost. The example states the facts: the request was received on 3 November 2026, and the privacy team has given IT three identifiers for Alex, the name, the work email address and the employee number, with a date range from 1 January 2024 to the date of the request. The job is four steps and a hand-over.
The route
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 (Microsoft Learn, eDiscovery solutions). A subject access request needs search and export, which Content Search and 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. Microsoft states that administrators and users working eDiscovery cases need a Microsoft 365 E3 or E5 licence, and that Premium needs E5 or an E5 add-on. An E3 tenant can run the whole request on Standard.
Premium does have an Annotate view with area redactions. It is manual, one document at a time, and the committed output is a PDF (Microsoft Learn, review set views). For a mailbox-sized request that is not a redaction plan. The job is to collect and export.
The search
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 Learn, create a search). Alex’s own mailbox and OneDrive are added as data sources by name, address or site URL, and everything in them is in scope. Other people’s mailboxes, the HR SharePoint site and the team’s Teams channel are searched for Alex’s identifiers: the name, the email address and the employee number, plus any aliases the privacy team supplies.
Scope is the privacy team’s decision, not IT’s, and the law backs them: UK GDPR requires a reasonable and proportionate search (ICO, finding and retrieving the information). Get the identifiers and the date range in writing, and read the statistics before exporting. 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.
Export settings
The export options decide whether the privacy team receives a complete set or a partial one. Choose PSTs for messages, not individual message files, because a message-file 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 the items with the items report, not the report alone.
Timing and the hand-over
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.
What lands in the example is two PST packages for Alex’s mailbox, one set of native files from OneDrive and the HR site, HTML transcripts for the Teams channel, and the items report, items.csv, listing every item exported with its source location. What IT hands to the privacy team is the ZIP packages, the items report, and a one-paragraph note of the locations, identifiers and date range searched. That note becomes part of the record of the response. IT keeps its own copy until the response has gone out and the agreed retention period has passed.
| Request | Alex Morgan, data subject access request, received 3 November 2026 |
|---|---|
| Identifiers | Name, work email address, employee number, aliases supplied by the privacy team |
| Date range | 1 January 2024 to the date of the request |
| Locations | Alex’s mailbox and OneDrive in full; other mailboxes, the HR SharePoint site and the team’s Teams channel searched for the identifiers |
| Format | PST packages at 2 GB, cloud attachments at latest version, native documents, Teams HTML transcripts, partially indexed items included |
| Delivered | ZIP packages, items.csv, one-paragraph search note; IT copy retained until the response has gone out and the retention period has passed |
Into the review tool
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. Alex’s own information must stay, everyone else’s must go, and each decision needs a record. The video shows a recording of a sample case in SafeRedact, with invented people.
A case starts with the data subject: the person who made the request, with any aliases, so their own details are kept. Then the export is loaded as IT produced it, PST packages included, and the files are counted before anything runs. In DSAR mode the subject’s data is kept and everyone else’s is flagged. The files are opened and read in the browser. Only the extracted text and the case’s data subject details go out for detection, no document is stored on a server, and detections are logged as they are found.
The dashboard shows every detection by type and by source, and flags the files a person should look at. Attachments are read as documents in their own right. Review is by person, not by page. Variants of a name are grouped, and one decision applies everywhere that person appears. The witness from Lesson 2 would be decided once and applied across the whole export, and the decision is recorded in the review decision log, with the reason where the reviewer enters one. When the review is complete, the reviewer attests that the redactions have been checked, and the redacted files, the processing summary, the audit trail and the review decision log download as one pack. PST files up to 2 GB and 25,000 messages are supported, which is why the package size matters.
The outcome and next step
The export now has a record another person can follow: the search note from IT, the items report from Purview, and the audit trail and decision log from the review. The response to Alex still has to be written: what is enclosed, what was withheld and why, and the supplementary information the right of access requires. That is the response letter, and it is the next lesson.
Watch the lesson by chapter
- 00:00 The ticket
- 01:04 The route
- 02:12 The search
- 03:19 Export settings
- 04:26 Timing and the hand-over
- 05:26 Into the review tool
- 06:32 Review and the pack
- 07:25 The outcome and next step
Frequently asked questions
Which Microsoft Purview eDiscovery solution should IT use for a DSAR?
A subject access request needs 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. Microsoft states that administrators and users working eDiscovery cases need a Microsoft 365 E3 or E5 licence, and that Premium needs E5 or an E5 add-on, so an E3 tenant can run the whole request on Standard. The classic eDiscovery experiences were retired on 31 August 2025; everything now runs in the new eDiscovery experience in the Purview portal.
Can Purview eDiscovery Premium redact the DSAR for us?
Premium has an Annotate view with area redactions. It is manual, one document at a time, and the committed output is a PDF. For a mailbox-sized request that is not a redaction plan. The Purview job is to collect and export; the redaction of other people’s personal data happens in a review tool, with a record of each decision.
How should the search be scoped for one person?
Add the requester’s own mailbox and OneDrive as data sources by name, address or site URL, so everything in them is in scope. Search other people’s mailboxes, the relevant SharePoint sites and Teams channels for the requester’s identifiers: name, work email address, employee number and any aliases the privacy team supplies, within the agreed date range. Scope is the privacy team’s decision, and UK GDPR requires a reasonable and proportionate search. Get the identifiers and the date range in writing and read the search statistics before exporting.
Should the mailbox be exported as PST or as individual messages?
PST, with the package size set to 1 GB or 2 GB rather than the 5 GB default. A message-file export does not carry the content of attached messages. Turn on cloud attachments at their latest version so that files shared as links reach the disclosure, include partially indexed items so that scanned and image-only documents are not left out, and export the items with the items report rather than the report alone.
How long do Purview exports take and how long are they kept?
An export that runs for more than seven days is cancelled automatically, so split a large mailbox by date range. Export packages expire 14 days after creation and cannot be recovered, so download promptly from the case’s Exports tab. These limits are Microsoft’s and are documented on Microsoft Learn; check the current position before relying on them.
What does IT hand to the privacy team?
The ZIP packages, the items report (items.csv, listing every item exported with its source location), and a one-paragraph note of the locations, identifiers and date range searched. That note becomes part of the record of the response. IT keeps its own copy until the response has gone out and the agreed retention period has passed.
Transcript
00:00 The ticket
Alex Morgan's data subject access request, a D-S-A-R under UK GDPR, has reached IT as a ticket from the privacy team: find everything the organisation holds about Alex in Microsoft 365 and get it out as files. This lesson follows the ticket through Microsoft Purview to the review tool. The clock is the reason the export matters. The organisation has one month to respond. IT's 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 Alex, and that step is where the month is usually lost. The example states the facts. The request was received on 3 November 2026. The privacy team has given IT three identifiers for Alex: the name, the work email address and the employee number, with a date range from 1 January 2024 to the date of the request. The job is four steps and a hand-over.
01:04 The route
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. A subject access request needs search and export, which Content Search and 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. Microsoft states that administrators and users working eDiscovery cases need a Microsoft 365 E3 or E5 licence, and that Premium needs E5 or an E5 add-on. An E3 tenant can run the whole request on Standard. Premium does have an Annotate view with area redactions. It is manual, one document at a time, and the committed output is a PDF. For a mailbox-sized request that is not a redaction plan. The job is to collect and export.
02:12 The search
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. Alex's own mailbox and OneDrive are added as data sources by name, address or site URL, and everything in them is in scope. Other people's mailboxes, the HR SharePoint site and the team's Teams channel are searched for Alex's identifiers: the name, the email address and the employee number, plus any aliases the privacy team supplies. Scope is the privacy team's decision, not IT's, and the law backs them: UK GDPR requires a reasonable and proportionate search. Get the identifiers and the date range in writing, and read the statistics before exporting. 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.
03:19 Export settings
The export options decide whether the privacy team receives a complete set or a partial one. Choose PSTs for messages, not individual message files, because a message-file export does not carry the content of attached messages. Set the PST package size to 1 or 2 gigabytes rather than the 5 gigabyte 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 the items with the items report, not the report alone.
04:26 Timing and the hand-over
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. What lands in the example is two PST packages for Alex's mailbox, one set of native files from OneDrive and the HR site, HTML transcripts for the Teams channel, and the items report, items dot C-S-V, listing every item exported with its source location. What IT hands to the privacy team is the ZIP packages, the items report, and a one-paragraph note of the locations, identifiers and date range searched. That note becomes part of the record of the response. IT keeps its own copy until the response has gone out and the agreed retention period has passed.
05:26 Into the review tool
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. Alex's own information must stay, everyone else's must go, and each decision needs a record. What follows is a recording of a sample case in SafeRedact, with invented people. A case starts with the data subject: the person who made the request, with any aliases, so their own details are kept. Then the export is loaded as IT produced it, PST packages included, and the files are counted before anything runs. In DSAR mode the subject's data is kept and everyone else's is flagged. The files are opened and read in the browser. Only the extracted text and the case's data subject details go out for detection, no document is stored on a server, and detections are logged as they are found.
06:32 Review and the pack
The dashboard shows every detection by type and by source, and flags the files a person should look at. Attachments are read as documents in their own right. Review is by person, not by page. Variants of a name are grouped, and one decision applies everywhere that person appears. The witness from the last lesson would be decided once and applied across the whole export, and the decision is recorded in the review decision log, with the reason where the reviewer enters one. When the review is complete, the reviewer attests that the redactions have been checked, and the redacted files, the processing summary, the audit trail and the review decision log download as one pack. PST files up to 2 gigabytes and 25,000 messages are supported, which is why the package size matters.
07:25 The outcome and next step
The export now has a record another person can follow: the search note from IT, the items report from Purview, and the audit trail and decision log from the review. The response to Alex still has to be written: what is enclosed, what was withheld and why, and the supplementary information the right of access requires. That is the response letter, and it is the next lesson. The sources for this lesson and information about SafeRedact are in the description.
How SafeRedact Fits
SafeRedact is browser-based redaction software for data subject access requests. Files never leave your browser: documents are processed client-side, only extracted text and the case's data subject details are sent for AI detection, and no documents are stored on servers. Detection text is never used for training and is deleted within 30 days. You name the data subject whose information should be preserved, and other individuals' personal information is flagged for redaction across every file in the case, including ZIP and Purview PST exports. Every detection is reviewed by a human before anything is exported, and the export package includes the redacted files, a processing summary, an audit trail and a review decision log. Supported formats: PST, PDF, DOCX, XLSX, EML, MSG, HTML, TXT, CSV, JSON, ZIP. A Data Processing Agreement is available and enterprise cases are priced per case, with the price set with you and shown before you download.
Make Every Redaction Decision Once
AI detection flags every identifier in the case. You decide whose it is, with the requester's data preserved and every decision recorded in the exported audit trail. Cases are priced per case, with a Data Processing Agreement available.
Set up your organisationDSAR: The Complete Guide
DSAR Redaction Guide (Pillar) What Is a DSAR? Employee DSAR Redaction ICO DSAR Guidance DSAR Redaction Mistakes DSAR Response Template DSAR Compliance Checklist Automate DSAR Redaction DSAR Redaction Cost DSAR Software Comparison CCPA DSAR Guide US State Privacy Laws DSAR Cost CalculatorSources
- 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?
- SafeRedact, Exporting a DSAR from Microsoft Purview (written guide)
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; the legislation, ICO guidance, and your counsel govern. The people, organisation and references in the worked example are invented. Frank is SafeRedact’s virtual narrator; his voice and likeness are generated with AI. The lessons are written and checked by SafeRedact.