The feature itself is small but useful. Compliance teams have been waiting for it, and the delays tell you something about how much weight to give any roadmap date.
What Microsoft says is changing
The Message Center post, MC920304, states it directly: admins will be able to customize the alert frequency per policy as well as adjust the email alerts frequency and recipients within the policy creation wizard by navigating to the new alerts page. Microsoft also says this new feature is available by default. The notice doesn't mention an opt-in switch, a migration step or any required preparation.
The change comes down to three settings, all set per policy:
- Alert frequency: how often a given policy produces alerts.
- Email alert frequency: how often notification emails go out.
- Recipients: who gets those emails.
All three sit on a new Alerts page inside the policy creation wizard.
Microsoft hasn't published the rest. There's no list of frequency options, no word on whether recipients can be distribution groups as well as individual people, and nothing on what existing policies will inherit. The notice only mentions the policy creation wizard, so it's also unclear whether you can change these settings on a policy that already exists. Until documentation or the preview answers those questions, don't assume.
Section summary: This is a change to how alerts are delivered and configured. Nothing in the announcement says detection rules, classifiers or match logic are changing.
Alerts are not policy matches
The difference matters here. In its Communication Compliance investigation documentation on Microsoft Learn, Microsoft says an alert is not the same as a policy match. An alert is usually built from several policy matches. Once a set number of matches is reached, the alert is created and an email goes to the alert recipient. The Alerts page in the portal shows the last 30 days of alerts, grouped by policy matches and sorted by severity.
So the new settings affect when people get told, and who gets told. They don't decide what gets flagged. If your policies are producing too many false positives, changing alert frequency won't fix that. You still need to tune the conditions, classifiers and scope. Microsoft hasn't claimed the feature reduces false positives or changes how much investigators have to review.
Speed of alerts has been a problem in this product before. In an earlier preview, Microsoft said alerts are surfaced within one hour of policy match detection rather than the standard 24-hour alert timeframe. There was a catch: the update applied only to new policies that are created, and alerts for existing policies would still have 48-hour latency. That's one reason to check carefully how the new alert settings treat policies you already have, once Microsoft says.
A timeline that keeps moving
There's more history to this rollout than the roadmap entry shows. When MC920304 first appeared in October 2024, the plan was much sooner. M365 Admin, a site that archives Microsoft's admin notices, captured that original version: Public Preview begins mid-November 2024, with General Availability starting early February 2025.
Microsoft has revised the notice several times since then. The March 9, 2026 version says: Public Preview: We will begin rolling out October 2026 (previously late July 2025) and expect to complete by end of October 2026 (previously mid-Aug 2025). For worldwide GA, Microsoft says only that it will announce this timeline in a future update.
The roadmap entry has changed too. An archived copy of roadmap item 181825 from earlier this year showed GA date: October CY2026, Preview date: July CY2025. The roadmap now says January 2027, which means GA has moved back at least one more quarter. The Message Center archive also records a newer version of MC920304, dated October 22, 2026, flagged as changing the end date. Its summary still says the preview has been delayed.
| Point in time | Public preview target | GA target |
|---|---|---|
| Original notice (Oct 2024) | Mid-Nov to late Dec 2024 | Early Feb 2025 |
| Before March 2026 update | Late July to mid-Aug 2025 | — |
| March 9, 2026 Message Center update | October 2026 | "Future update" |
| Earlier 2026 roadmap snapshot | July 2025 (listed) | October 2026 |
| Current roadmap (Oct 2026) | July 2025 (listed) | January 2027 |
The safest reading is that the roadmap lists January 2027 for GA, but the latest Message Center notice hasn't confirmed it. Microsoft's roadmap page says its dates are estimates and all information is subject to change. With this feature's history, take that warning seriously.
Section summary: The preview was due to finish in October 2026 but hadn't been confirmed as complete when this was written. GA is an estimate, not a commitment.
Government clouds have their own roadmap entry
Roadmap 181825 covers only Worldwide (Standard Multi-Tenant) tenants. Government tenants have a separate item. Roadmap ID 529852, published December 2, 2025, describes the same feature: admins will be able to customize the alert frequency per policy as well as adjust the email alerts frequency and recipients within the policy creation wizard. It's tagged for GCC, GCC High, DoD and is also listed as in development, for General Availability only.
If you run a government tenant, track 529852 rather than 181825. Features usually reach government clouds after commercial ones, and this one hasn't fully reached commercial tenants yet.
Why compliance teams should care
Communication Compliance is the Purview tool for spotting conduct and regulatory problems in workplace messages. Microsoft says it provides the tools to help organizations detect business conduct and regulatory compliance violations (e.g. SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content.
Those are very different kinds of risk, and they call for different responses. A policy watching for possible market manipulation probably needs fast notification to a small regulatory team. A broad policy for inappropriate language might be better handled with a scheduled batch to HR. Today, per-policy control over alert behavior is limited, and that's the gap Microsoft says this feature will close. Our view, based on how compliance operations usually work and not on any Microsoft claim:
- Routing: Each policy's alerts can go to the team that owns that risk, so one shared inbox doesn't have to cover everything.
- Noise control: Low-severity, high-volume policies can be set to notify less often, which leaves room for the urgent ones.
- Audit story: Settings documented per policy should make it easier to show regulators who gets notified about what, and how quickly.
There's a downside too. Analysis from Cloudscout, a service that tracks Message Center posts, warns that without proper preparation, the new alert customization feature may lead to an overwhelming number of alerts for admins, causing alert fatigue and potential oversight of critical compliance issues. More settings also mean more ways to get them wrong. A policy set to notify too rarely, or to notify someone who left the company last spring, is a quiet failure that nobody notices until an auditor asks.
The privacy model isn't changing. Microsoft restates the existing safeguards: usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. These are current product features, not new parts of this update. Still, anyone added as an alert recipient should already hold the right Communication Compliance role.
What admins can do now
Microsoft hasn't published setup steps, so this is preparation, not a procedure. It's practical advice based on the controls Microsoft has described:
- Track both roadmap IDs and MC920304. Commercial tenants should watch 181825. GCC, GCC High and DoD tenants should watch 529852.
- List your current policies. For each one, write down who currently gets alerts and how urgent its risk category really is.
- Choose recipients ahead of time. Map each policy to an owning team. Check that those people hold the right Communication Compliance role group, such as Investigators or Analysts.
- Test in preview before relying on it. When the new Alerts page appears in your tenant, create a test policy. Check that the frequency and recipient settings behave as you expect before applying them to production policies.
- Assume nothing about existing policies. Until Microsoft documents how current policies are handled, check them after the rollout rather than assuming they picked up new defaults.
The bottom line
This is a useful operational improvement. Communication Compliance alerts can go to the right people at a sensible pace, set policy by policy. It's not a new detection capability. It started as a "late 2024" feature and is still a preview with no confirmed GA date, so plan for it but don't commit to dates around it. Get your recipient lists in order now, test once the preview lands, and treat January 2027 as an estimate.