A security administrator monitors Microsoft Purview DLP alerts, Teams remediation requests, and remediation progress.
Microsoft has a familiar problem with data loss prevention (DLP). Purview can find a spreadsheet full of Social Security numbers in seconds. Getting the person who saved it to clean it up can take weeks of email. Microsoft's answer is a new Data Security Triage Agent capability that sends the cleanup request to the user through Microsoft Teams.

The Microsoft 365 roadmap lists the feature as item 564615, "Microsoft Purview: Data Security Triage Agent – Sensitive Data Remediation through Microsoft Teams." It is marked In development. The roadmap metadata gives a preview date of June 2026 and a general availability date of December 2027, for the Web platform in the Worldwide (Standard Multi-Tenant) cloud. Microsoft says its roadmap dates are estimates and can change, so admins should plan around that window rather than treat it as a promise.

A security administrator monitors Microsoft Purview DLP alerts, Teams remediation requests, and remediation progress. What the feature does​

The roadmap describes a DLP function that automatically detects file(s) with a Data Loss Prevention (DLP) policy match "Needs Attention" alerts and pushes a remediation notification to the end user who last modified the file guiding them to remove sensitive data through targeted Microsoft Teams messages. Microsoft's examples of sensitive data include Social Security numbers, passwords and credit card numbers. The feature covers files in SharePoint and OneDrive.

Microsoft also sent a Message Center post, MC1326260, to tenants. It says the capability will automate user engagement by sending remediation requests directly to the last modifier of affected files through Microsoft Teams. The readiness steps in that notice tell admins to review your Data Loss Prevention policies and determine which policies will use remediation and to coordinate with your Teams administrator to deploy and manage the required app.

The roadmap also promises progress tracking. Microsoft says the closed-loop workflow ensures that remediation progress is tracked and confirmed, giving admins real-time visibility and control via the Data Security Posture Management dashboard.

Section summary: This feature gets a request to the right person. It doesn't remove sensitive data on its own. The agent finds the last person who modified the file, asks them in Teams to fix it, and tracks whether they did.

The mechanics from Microsoft's documentation​

Microsoft Learn already documents the workflow as a Preview feature, and it adds detail the roadmap leaves out:

  • Who gets the message: In the agent's setup flow, Microsoft says that for SharePoint/OneDrive alerts triaged as Needs Attention, the agent sends a Teams chat to the user who last modified the file and asks them to remove the sensitive information.
  • How often: Reminders go out once a day to the file's last modifier. One reminder can cover up to 10 files when several need fixing.
  • What the message contains: The file name and a description of the sensitive information that needs attention.
  • When it stops: Once the user fixes a file, it drops off the next day's reminder. If no files are outstanding, no reminder is sent.
  • Reminder duration: Admins set how many days the agent keeps following up on an unfixed file.

This feature is narrower than the triage agent as a whole. The Microsoft Purview Triage Agent in DLP triages alerts from policies that are scoped to Exchange, Teams, OneDrive, SharePoint, and devices (Endpoint) locations, only. Teams reminders, however, apply only to SharePoint and OneDrive files. The M365 Admin summary of the Message Center post says it does not apply to Endpoint or Teams-originated alerts. A DLP hit on a USB copy or a Teams chat message won't produce one of these reminders.

Prerequisites​

The agent runs on Microsoft Security Copilot, so turning on a Purview setting is not enough. According to Microsoft's documentation, you need:

  1. A tenant onboarded to Microsoft Security Copilot.
  2. Microsoft 365 data sharing turned on in Security Copilot.
  3. The Microsoft Purview plug-in turned on in Security Copilot.
  4. DLP licensing for your organization.
  5. Security Compute Units (SCUs) provisioned for the agent. How many it uses depends on the number and type of alerts processed.

On cost, Microsoft says the remediation capability itself costs nothing extra. The only cost is the SCUs needed to triage the DLP alert first. That means every reminder depends on an alert you have already paid to triage.

The agent also has documented scope limits that affect rollout planning:

  • It triages alerts only from DLP policies in active mode. Policies in simulation mode are ignored.
  • It can look back up to 30 days before enablement if the tenant has enough SCUs. Older alerts are out of scope.
  • It handles files up to 2 MB.
  • The automatic run schedule is set by Microsoft and can't be changed.
  • Admins can shorten the alert timeframe later, but not lengthen it.
  • The agent can be deployed from the Purview or Defender XDR portal. It can be managed, edited and disabled only from the Purview portal.

Setting it up: Purview side​

To turn on reminders, edit the agent's configuration in Purview. Microsoft's documentation describes settings for Trigger, alert timeframe, remediation reminders, reminder duration, and policy scope. Policy scope is the main control. Microsoft says to specify the policy scope of the triage agent to control which DLP policy alerts and which policies are eligible for remediation reminders. Remediation reminders must be enabled, and eligible policies must be a subset of the policies defined for agent triage.

To limit reminders to specific policies:

  1. In the Microsoft Purview portal, go to Agents > Explore agents.
  2. Select Go to agent for the Triage Agent in Data Loss Prevention.
  3. Select Edit agent > Agent configuration.
  4. Under Set agent scope, select Edit.
  5. In the Select policies panel, turn on the Remediation toggle only for the policies that should send messages to users.
  6. Select Select policies to save.

Microsoft confirms that users who violate policies that aren't enabled for remediation don't receive Teams messages from the agent.

Setting it up: Teams Admin Center​

This is where rollouts are most likely to fail. Two settings must be correctly configured for the Data Security Triage Agent to send remediation messages through Microsoft Teams. Microsoft also warns that the Purview admin or analyst who configures the triage agent might not have permissions to access the Microsoft Teams Admin Center. If that applies to you, you'll need your Teams admin's help.

Setting 1: Turn on org-wide Microsoft apps

  1. Sign in to the Teams Admin Center.
  2. Go to Teams apps > Manage apps.
  3. Select Actions > Org-wide app settings.
  4. Set the Microsoft apps toggle to On.
  5. Select Save.

Setting 2: Make the agent app available

  1. In Teams apps > Manage apps, search for Data Security Triage Agent and select it.
  2. Open the Users and groups tab.
  3. Check that Availability is set to Available to everyone (the org-wide default), or to the specific users or groups you intend to reach.

You don't need to push the app to users. Microsoft says Purview installs it for a user automatically when it sends that user a remediation message. The app only has to be available, not blocked.

Two controls with different strengths​

Admins can limit who gets messages in two ways, and they behave differently:

ControlWhereWhat it doesBest use
Policy scopePurview agent configurationLimits which DLP policies trigger remindersDay-to-day control over which files and locations generate requests
App availabilityTeams Admin CenterBlocks delivery to specific users or groupsGuaranteeing certain people never receive messages

Microsoft calls blocking the app a hard block. Even if an alert is triaged and a message is generated, a blocked user won't receive it. Setting availability to No one stops all remediation messages immediately. That gives you a quick off switch if a pilot sends the wrong messages to the wrong people.

Troubleshooting delivery​

Microsoft's documentation lists these common delivery problems:

  • No users receive messages: Check whether the org-wide Microsoft apps toggle is off, and whether the Data Security Triage Agent app is blocked.
  • Some users don't receive messages: Check the app's Users and groups settings for those users or groups.
  • Messages were sent but users don't see them: The user may not have opened Teams recently. Messages appear once they sign in.

Microsoft also flags a common mistake: the org-wide Microsoft apps toggle is on, but the agent app itself is blocked. Both settings have to be right.

Checking whether it worked​

You can check remediation status in two places. At the alert level, Microsoft says you can view remediation status at the alert level on the Triage Agent alert queue in the DLP solution. The statuses are:

  • Remediated: the user fixed every file in the alert.
  • In progress: the agent contacted the user, but not all files are fixed yet.
  • Error: the Teams message couldn't be sent.

At the file level, the Related assets section of each DLP alert lists every file with its own status. A file shows Remediated only when the user has removed all the detected sensitive information types in it. If only some or none were removed, it shows In progress.

One mismatch is worth noting. The roadmap mentions visibility through the Data Security Posture Management dashboard, while the current Learn documentation describes the alert queue and alert-level views. Expect the reporting surfaces to change before general availability.

The caveats​

The marketing line on the roadmap is cheerful. It says the agent handles the heavy lifting of pushing remediation requests directly to the end user, so Purview admins don't have to! Before you plan around it, consider three caveats. This is analysis based on the documented behavior, not Microsoft's own claims.

  1. "Last modifier" may be the wrong person. The person who last edited a file may not be the one who added the sensitive data, and may not own the file. Someone who fixed a typo in a shared workbook could end up getting daily Teams messages about payroll data they never added.
  2. The agent only asks. Nothing in the documentation says the agent edits files or removes data. If users ignore the reminders, the data stays where it is. Reminder duration and the In progress status help you find those cases, but people still have to follow up.
  3. The rollout needs communication, not just configuration. Unexpected DLP messages from a bot can look like phishing. Our earlier coverage of the triage agent made the same point: user-facing reminders need communications, legal, compliance, and escalation planning.

A sensible rollout​

  1. Confirm that Security Copilot onboarding, the Purview plug-in, Microsoft 365 data sharing and SCU capacity are in place.
  2. Turn on remediation for one narrowly scoped, high-confidence DLP policy, such as one covering credit card numbers in a single SharePoint site.
  3. In the Teams Admin Center, limit app availability to a pilot group.
  4. Tell the pilot users about the reminders before the first one arrives.
  5. Trigger a SharePoint or OneDrive "Needs Attention" alert, then confirm the message arrives and the status changes as expected.
  6. Watch SCU consumption before expanding the scope.

Adding Teams reminders to the DLP Triage Agent goes after a real gap in DLP: finding sensitive data is easy, but getting it cleaned up is not. The feature is in preview, depends on Security Copilot and SCUs, works only on SharePoint and OneDrive files, and relies on users doing the cleanup themselves. Configured carefully, it can replace a lot of manual follow-up email.

 

References

  1. Microsoft Purview: Data Security Triage Agent - Sensitive Data Remediation through Microsoft Teams Microsoft 365 Roadmap 2026-11-20T01:24:53.555720Z
  2. Microsoft Purview: Data Security Triage Agent - Sensitive Data Remediation through Microsoft Teams deltapulse.app
  3. Get started with the Microsoft Purview Triage Agent in Data Loss Prevention learn.microsoft.com