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

Microsoft Purview | Insider Risk Management: Custom Communication Compliance policy as IRM indicator

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

Rollout

Roadmap
489838

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 Oct 2025 mid-October 2025, late October 2025 → late November 2025, mid-December 2025
  • Seen 18 Sep 2025 mid-August 2025, early September 2025 → mid-October 2025, late October 2025
  • Seen 27 Jun 2025 late May 2025, early June 2025, mid-June 2025, early July 2025 → late July 2025, early August 2025, mid-August 2025, early September 2025

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, safely structured

Updated October 28, 2025: We have updated the timeline. Thank you for your patience.

Coming soon to Microsoft Purview | Insider Risk Management (IRM), admins will be able to select any Communication Compliance (CC) policy alerts as indicators in IRM policies. After this rollout, IRM admins can select any CC policies that they would like to bring into IRM and detect if a user has alerts for these selected CC policies. When an IRM alert is generated, admins can review if there are any alerts for the user in CC under the policies that are enabled as indicators. This feature will help admins and analysts view this information in IRM without switching to CC.

This message is associated with Microsoft 365 Roadmap ID 489838.

When this will happen

Public Preview: We will begin rolling out late July 2025 (previously late May) and expect to complete by early August 2025 (previously early June).

General Availability (Worldwide): We will begin rolling out late November 2025 (previously mid-October) and expect to complete by mid-December 2025 (previously late October).

How this will affect your organization

After this rollout, admins will be able to enable this indicator in IRM’s global settings for policy indicators. When enabled, this indicator can be selected in any IRM policy.

Using the indicator

  1. In IRM, go to Settings > Insider Risk Management > Policy indicators > Built-in Indicators. Open the Communication Compliance indicators > Detect messages matched by specific CC policies drop-down menu. Check the box and choose the CC policies to bring into IRM. Save the changes.
  2. To use in a policy: In the policy wizard for any IRM policy, configure the policies as applicable until you get to the Indicators page. Open the Communication Compliance indicators drop-down menu and check the box for Sending messages flagged by selected CC policies. Configure the rest of the policy as applicable.

These changes will be available by default for admins to configure.

What you need to do to prepare

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation.

Learn more: Configure policy indicators in insider risk management | Microsoft Learn (will be updated before rollout)

What changed

Between archive captures, newest first
  1. Updated September 18,October 28, 2025: We have updated the timeline. Thank you for your patience. Coming … 2025 (previously early June). General Availability (Worldwide): We will begin rolling out mid-Octoberlate November 2025 (previously mid-August)mid-October) and expect to complete by late October mid-December 2025 (previously early September).late October). How this will affect your organization: After this rollout, admins will be …

  2. Updated June 27,September 18, 2025: We have updated the timeline below. timeline. Thank you for your patience. Coming soon to Microsoft Purview | Insider … 2025 (previously early June). General Availability (Worldwide): We will begin rolling out mid-Augustmid-October 2025 (previously mid-June)mid-August) and expect to complete by early Septemberlate October 2025 (previously early July).September). How this will affect your organization: After this rollout, admins will be …

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

    Updated June 27, 2025: We have updated the timeline below. Thank you for your patience. Coming soon to Microsoft Purview | Insider Risk Management (IRM), admins will … When this will happen: Public Preview: We will begin rolling out late MayJuly 2025 (previously late May) and expect to complete by early June 2025.August 2025 (previously early June). General Availability (Worldwide): We will begin rolling out mid-Junemid-August 2025 (previously mid-June) and expect to complete by early July 2025.September 2025 (previously early July). How this will affect your organization: After this rollout, admins will be …

  3. · first version seen

Learn more

Links from the notice and their documentation checks

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.
  • 1 linked page has not been read yet.
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 27 Oct 15:46 UTC · 271 of 272 readable · 269 fully read · documentation 469/469 current