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 · 8/9 advisories · checked 11:37 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Purview | Insider Risk Management: Granular trigger throttling

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

Rollout

Roadmap
382130

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 28 Mar 2025 early March 2025, late March 2025
  • Seen 13 Nov 2024 late January 2024 → late January 2025, early March 2025, late March 2025
  • Seen 5 Sep 2024 late May 2024, mid-June 2024, late December 2024 → late October 2024, late January 2024

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 March 28, 2025: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience. Coming soon, Microsoft Purview Insider Risk Management will be rolling out public preview of granular trigger throttling limits. When this will happen: Public Preview: We will begin rolling out late October 2024 (previously late August) and expect to complete by late January 2025 (previously late October). General Availability: We will communicate via Message center when we are ready to proceed. How this will affect your organization: With this update, we are introducing more granular trigger throttling limits to isolate the impact of a surge in noisy trigger volumes and prevent other policies from being affected. This ensures that organizations can receive critical alerts without being throttled by these limits. By default, these throttling limits will be applied: All sensitive triggers, including HR signals, Azure AD leavers, and custom triggers, will be limited to 15,000 per day per trigger. All other triggers will be limited to 5,000 per day per trigger. Additionally, the policy health warning messages will be enhanced to assist admins with appropriate permissions in effectively identifying and addressing noisy triggers. What you need to do to prepare: No action is needed from you to prepare for this rollout. You may want to notify your admins about this change and update any relevant documentation as appropriate. Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. You can access the Insider Risk Management solution in the Microsoft Purview compliance portal. Learn more: Insider risk management | Microsoft Learn

What changed

Between archive captures, newest first
  1. Updated November 13, 2024: WeMarch 28, 2025: After further review we have updated the rollout timeline below. Thank youdecided not to proceed with this change at this time. We apologize for your patience.any inconvenience. Coming soon, Microsoft Purview Insider Risk Management will be rolling out public preview of granular trigger throttling limits. This message is associated with Microsoft 365 Roadmap ID 382130. When this will happen: Public Preview: We will begin rolling out late … complete by late January 2025 (previously late October). General Availability: We will begin rolling out early March 2025 (previously late December) and expect communicate via Message center when we are ready to complete by late March 2025 (previously late January).proceed. How this will affect your organization: With this update, we are introducing …

  2. Updated September 5,November 13, 2024: We have updated the rollout timeline below. Thank you for your … Public Preview: We will begin rolling out late October 2024 (previously late May)August) and expect to complete by late January 20242025 (previously late October). General Availability: We will begin rolling out late January 2024early March 2025 (previously late December) and expect to complete by late January 2024.March 2025 (previously late January). How this will affect your organization: With this update, we are introducing …

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

    Updated September 5, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon, Microsoft Purview Insider Risk Management will be rolling out public … When this will happen: Public Preview: We will begin rolling out late MayOctober 2024 (previously late May) and expect to complete by mid-June 2024.late January 2024 (previously late October). General Availability: We will begin rolling out late DecemberJanuary 2024 (previously late December) and expect to complete by late DecemberJanuary 2024. How this will affect your organization: With this update, we are …

  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 11:37 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current