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: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 20:51 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Purview | Insider risk management- Insider risk management for risky agents

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
516032

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 21 May 2026 early May 2026, late May 2026 → mid-June 2026, end of July 2026
  • Seen 9 Mar 2026 late March 2026, late April 2026 → early May 2026, late May 2026
  • Seen 30 Jan 2026 early December 2026, late December 2026 → late March 2026, late April 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated May 20, 2026: We have updated the timeline. Thank you for your patience.  Introduction As AI agents become deeply embedded in enterprise ecosystems, they are evolving beyond simple tools or workflows into an autonomous digital workforce. These agents can interpret user intent, access and manipulate enterprise data, execute actions on behalf of users, and even make real-time decisions. In many ways, they operate like human insiders only with machine-speed data processing capabilities. To govern and protect these agents effectively, organizations require visibility into their activities, contextual understanding of their actions, and the ability to flag or block risky behavior. Now, Insider Risk Management can be extended to detect and remediate potentially risky agent activities. Features: Copilot Studio & Azure AI Foundry Integration: Detect potentially risky activities of agents hosted on Copilot Studio, Azure AI Foundry, and Agent 365 platforms Risky AI Usage Policies: Define and enforce policies specific to AI agents accessing sensitive data or performing high-risk actions. IRM for Agent Users: Extend IRM in Purview to govern agent-driven workflows and protect organizational data. This message is associated with Microsoft 365 Roadmap ID 516032. When this will happen: Public Preview: We will begin rolling out early December 2025 and expect to complete by mid-January 2026. General Availability (Worldwide): We will begin rolling out mid-June 2026 (previously early May) and expect to complete by end of July 2026 (previously late May). How this affects your organization: On the Overview page in the Insider Risk Management solution, you will be able to access the overall risk profile of agents deployed in your organization. The Risky Agents policy will be automatically deployed for all agents hosted on Copilot Studio and Azure AI Foundry across your organization. Alerts from this policy will be generated when an agent’s activity exceeds the thresholds configured in this automatically deployed Risky Agents policy. These alerts can be found under Agents > Alerts on the left pane. What you can do to prepare: Review the public facing documentation to learn more about this exciting new offering: Learn about Insider Risk Management policy templates | Microsoft Learn Review the new Insider Risk Management interface in the Microsoft Purview portal, which now includes separate sections for Users and Agents. Review and tune the Risky Agents policy based on your organization’s requirements. If you don’t wish to track agent activities, you can delete the automatically deployed Risky Agents policy.  Learn more: Help dynamically mitigate risks with Adaptive Protection | Microsoft Learn Create and manage Insider Risk Management policies | Microsoft Learn Learn about Insider Risk Management policy templates | Microsoft Learn

What changed

Between archive captures, newest first
  1. Updated March 9,May 20, 2026: We have updated the timeline. Thank you for your patience.  Introduction … complete by mid-January 2026. General Availability (Worldwide): We will begin rolling out early May mid-June 2026 (previously late March)early May) and expect to complete by late Mayend of July 2026 (previously late April).May). How this affects your organization: On the Overview page in the Insider …

  2. Updated January 30,March 9, 2026: We have updated the timeline. Thank you for your patience.  Introduction … complete by mid-January 2026. General Availability (Worldwide): We will begin rolling out late Marchearly May 2026 (previously early December)late March) and expect to complete by late AprilMay 2026 (previously late December).April). How this affects your organization: On the Overview page in the Insider …

    • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

    Updated January 30, 2026: We have updated the timeline. Thank you for your patience.  Introduction As AI agents become deeply embedded in enterprise ecosystems, they are … complete by mid-January 2026. General Availability (Worldwide): We will begin rolling out early Decemberlate March 2026 (previously early December) and expect to complete by late December 2026.April 2026 (previously late December). How this affects your organization: On the Overview page in the Insider …

  3. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
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 26 Oct 20:51 UTC · 272 of 272 readable · 271 fully read · documentation 469/469 current