Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 274/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 00:15 UTC Customize Public modeDiscuss ChangeIntel on Discord

Recorded 5 Nov 2026 at 17:01 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.

Microsoft Purview: Data Loss Prevention – Enhancements to Data Security Triage Agent

Adding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's ide…

What it said

Roadmap ID
557552
Status
Launched
General availability target
April CY2026
Preview target
February CY2026
Products
Microsoft Purview
Clouds
Worldwide (Standard Multi-Tenant)
Release phases
General Availability, Preview
Platforms
Web
Added to the roadmap
20 Feb 2026 00:00 UTC
Last changed
14 May 2026 23:15 UTC

Source evidence when recorded

Microsoft 365 roadmap
IncompleteRead 5 Nov 2026 at 15:56 UTC

Coverage describes the sources at this observation. A complete read then does not establish their current position.

Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (62)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 5 Nov 2026 · 17:01:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  2. 4 Nov 2026 · 15:02:25 UTC Last changed20 Feb 2026 00:00 UTC → 14 May 2026 23:15 UTC
  3. 4 Nov 2026 · 15:02:25 UTC Preview targetNot stated → February CY2026
  4. 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → April CY2026
  5. 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  6. 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
  7. 4 Nov 2026 · 15:02:25 UTC Link: Microsoft Purview/roadmap?topic=Microsoft%20Purview&period=all#items → No longer listed in this observation
  8. 4 Nov 2026 · 15:02:25 UTC Link: Purview/roadmap?topic=Purview&period=all#items
  9. 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=557552
  10. 4 Nov 2026 · 15:02:25 UTC SummaryAdding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's identity who was setting up the agent. This provides cleaner audit capabilities. → Adding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's ide…
  11. 4 Nov 2026 · 13:26:53 UTC Last changed14 May 2026 23:15 UTC → 20 Feb 2026 00:00 UTC
  12. 4 Nov 2026 · 13:26:53 UTC Preview targetFebruary CY2026 → Not stated
  13. 4 Nov 2026 · 13:26:53 UTC General availability targetApril CY2026 → Not stated
  14. 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  15. 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
  16. 4 Nov 2026 · 13:26:53 UTC Link: Purview/roadmap?topic=Purview&period=all#items → No longer listed in this observation
  17. 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=557552 → No longer listed in this observation
  18. 4 Nov 2026 · 13:26:53 UTC Link: Microsoft Purview/roadmap?topic=Microsoft%20Purview&period=all#items
  19. 4 Nov 2026 · 13:26:53 UTC SummaryAdding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's ide… → Adding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's identity who was setting up the agent. This provides cleaner audit capabilities.
  20. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  21. 4 Nov 2026 · 11:04:04 UTC Last changed20 Feb 2026 00:00 UTC → 14 May 2026 23:15 UTC
  22. 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → February CY2026
  23. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → April CY2026
  24. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  25. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  26. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft Purview/roadmap?topic=Microsoft%20Purview&period=all#items → No longer listed in this observation
  27. 4 Nov 2026 · 11:04:04 UTC Link: Purview/roadmap?topic=Purview&period=all#items
  28. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=557552
  29. 4 Nov 2026 · 11:04:04 UTC SummaryAdding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's identity who was setting up the agent. This provides cleaner audit capabilities. → Adding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's ide…
  30. 4 Nov 2026 · 10:01:18 UTC Last changed14 May 2026 23:15 UTC → 20 Feb 2026 00:00 UTC
  31. 4 Nov 2026 · 10:01:18 UTC Preview targetFebruary CY2026 → Not stated
  32. 4 Nov 2026 · 10:01:18 UTC General availability targetApril CY2026 → Not stated
  33. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  34. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  35. 4 Nov 2026 · 10:01:18 UTC Link: Purview/roadmap?topic=Purview&period=all#items → No longer listed in this observation
  36. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=557552 → No longer listed in this observation
  37. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft Purview/roadmap?topic=Microsoft%20Purview&period=all#items
  38. 4 Nov 2026 · 10:01:18 UTC SummaryAdding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's ide… → Adding below enhancements to Data Security Triage Agent in MS Purview - Metadata supported Custom Instructions (DLP only) : Earlier the agent only supported custom instructions which are related to content (E.g. Focus on alerts related to financial information). Now we also support instructions related to metadata. (E.g. Focus on alerts related to financial information for user Adam in last 20 days) - Consolidated Agent settings : Earlier we had seperate controls for deployment configuration and triggers. We are now merging them into a single view as the settings can be altered anytime and it becomes easier for admins and analysts to change them from single view. - Support for alerts with Non content contains condition (DLP only) : Till now we were showing alerts generated from non-content contains conditions as unsupported. (E.g. Condition = RecipientDomainIs matches and triggers alert, alert is unsupported). Now we are bringing the alerts into triage capability and determining categorization for them also - Agent Identity : Now the Triage agent can be deployed with Agent's own identity generated in Microsoft Entra. There won't be a need to have the agent run using the user's identity who was setting up the agent. This provides cleaner audit capabilities.
  39. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  40. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  41. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  42. 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=557552 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=557552
  43. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  44. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  45. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM557552
  46. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  47. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  48. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  49. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  50. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  51. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  52. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  53. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  54. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  55. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  56. 18 Oct 2026 · 14:54:30 UTC Link: Purview/roadmap?topic=Purview&period=all#items
  57. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  58. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  59. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  60. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  61. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  62. 14 Oct 2026 · 11:22:42 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 12 Nov 00:15 UTC · 274 of 275 readable · 272 fully read · documentation 469/469 current