Action group: real alert e-mails only start ~24h after the receiver confirms the OTP code, test e-mail arrives right away

Nikos Koulouridis 20 Reputation points
2026-10-21T10:56:28.61+00:00

Hi all,

We set up a new action group with 3 e-mail receivers for some security alerts, and we're seeing something we can't find in the docs.

What happens

  1. Each receiver gets the new one-time code e-mail and confirms it within the 30 min, then gets "You're now in the ... action group".
  2. The Test button on the action group works right away, the test e-mail arrives in minutes.
  3. But for about 24 hours after confirming the code, no real alert e-mail is sent.
    The alert history says "Action group ... executed", but our Exchange Online message trace has no record of any e-mail, from any sender, not delivered, not filtered, not failed.
  4. After ~24h, real alerts start arriving normally and keep working.

We saw it twice, same action group, different people

Receivers Code confirmed (UTC) Real alerts with no e-mail First real alert received
2 receivers 2026-10-08 09:14 7 2026-10-09 10:19
3rd receiver (added later) 2026-10-13 07:56 5 2026-10-14 09:04

In the 2nd case, the other 2 receivers got those same 5 alerts fine, so it's per receiver, not per action group.

What we ruled out

  • No alert processing rules on the subscription, all receivers show Enabled
  • Common alert schema on, location Global
  • Message trace without a sender filter, so azure-noreply@, azureemail-noreply@ and ******@mail.windowsazure.com are all covered
  • Nothing in quarantine or junk, no mail-flow changes on our side
  • No rate-limit notice, and the volume was low (a few alerts a day)
  • No Service Health events for those days

Questions

  1. Is a ~24h delay between confirming the code and getting real alert e-mails expected? If yes, is it documented anywhere?
  2. Why does the Test e-mail go out right away when real alerts don't? Right after adding someone, the test tells you everything works when it doesn't.
  3. Is there a way (portal or API) to see if a receiver is fully active, so we know when someone will actually get alerts?

Happy to share alert IDs privately if someone from Microsoft wants to look at the backend. Thank you!

Azure Monitor
Azure Monitor

An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.

0 comments No comments

Answer accepted by question author
Salamat Shah 990 Reputation points MVP
2026-10-21T12:11:43.98+00:00

Dear Nikos,

No, a ~24-hour delay is not documented or expected behavior for Azure Monitor Action Group email receivers after they successfully confirm the verification code.

No, publicly documented requirement says email receivers must wait ~24 hours after verification before receiving real alerts

Test notifications and alert-triggered notifications can follow different backend paths. A receiver can pass verification and receive test emails while still not being fully active in the production notification path.

There is no customer-facing portal or API field that definitively shows "fully active for production alerts" beyond Enabled/Verified status.

Recommendations:

It's better to open a support case, support can inspect the Azure Monitor notification backend and confirm whether notification generation was delayed or suppressed for those receivers.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.