Outlook Admin Center: Calendar Reminder Policies Explained

What is an Exchange default reminder policy?

It's a mailbox-level configuration, set per user or pushed across a tenant with PowerShell, that controls whether calendar reminders fire, how long before an event they appear, and whether a sound plays with them. There's no single toggle in the Exchange admin center labeled "reminder policy" — instead, admins reach these settings through the Set-MailboxCalendarConfiguration cmdlet, which modifies mailbox calendar settings for Outlook on the web, affecting how the user's calendar looks and how reminders work, and how meeting invitations, responses, and notifications are sent to the user.

The three parameters that matter most are RemindersEnabled, DefaultReminderTime, and ReminderSoundEnabled. Exchange administrators can use Set-MailboxCalendarConfiguration to configure reminder behavior for individual mailboxes in Outlook on the web, with the most relevant settings being RemindersEnabled, DefaultReminderTime, and ReminderSoundEnabled. These settings only govern Outlook on the web and new Outlook for Windows — they don't touch how iPhone notifications behave once an event reaches a device, which is a separate layer covered in our guide on Outlook calendar reminder settings.

How do admins change the default reminder time for a tenant?

Admins run Set-MailboxCalendarConfiguration against one mailbox or pipe a filtered list of mailboxes into it to apply the setting org-wide. The cmdlet accepts a fixed set of intervals — 00:00:00, 00:05:00 (5 minutes), 00:10:00 (10 minutes), 00:15:00 (15 minutes) which is the default, 00:30:00 (30 minutes), 01:00:00 (1 hour), 02:00:00 (2 hours), 03:00:00 (3 hours), 04:00:00 (4 hours), 08:00:00 (8 hours), 12:00:00 (12 hours), 1.00:00:00 (1 day), 2.00:00:00 (2 days), 3.00:00:00 (3 days), 7.00:00:00 (7 days), 14.00:00:00 (14 days) — there's no free-text value outside this list.

A common tenant-wide rollout looks like this: get-mailbox -resultsize unlimited -filter {isResource -eq $false} | Set-MailboxCalendarConfiguration -RemindersEnabled:$true -DefaultReminderTime:00:15:00 -ReminderSoundEnabled:$true, which resets every non-resource mailbox back to the 15-minute default with sound on. The same pattern with $false values is also what admins run before a mailbox migration to suppress reminder noise mid-cutover, as documented in one migration runbook that recommends turning off for all MBX users before migration and restoring afterward.

There's an important dependency: once RemindersEnabled is false, DefaultReminderTime and ReminderSoundEnabled no longer have an effect on reminder behavior. Setting a new default time on a mailbox where reminders are off does nothing until reminders are re-enabled.

Can admins disable calendar reminders entirely?

Yes — setting RemindersEnabled to $false turns off reminders for Outlook on the web and new Outlook, and the dependent settings stop mattering once it's off. A representative command: Set-MailboxCalendarConfiguration -Identity james@meetingroom365.com -RemindersEnabled $false disables calendar reminders for James, and once RemindersEnabled is false, DefaultReminderTime and ReminderSoundEnabled no longer have an effect on reminder behavior.

This is scoped per mailbox, not global by default — admins who want it tenant-wide pipe a mailbox list into the same cmdlet, the same technique used in the bulk reminder-time example above. It's also account- and client-specific in a way that trips people up: a change made through PowerShell against the OWA calendar configuration does not touch the desktop Outlook client's own default reminder setting, which is account-specific, applies to the calendar for the primary mailbox, and does not affect other users' calendars or shared calendars, and is only available in desktop Outlook for Windows or Mac, not in Outlook on the web or the mobile apps. That split is a frequent cause of tickets — a reminder policy pushed from the admin center can look like it did nothing if the user is checking desktop Outlook instead of OWA.

How is a reminder policy different from a calendar sharing policy?

They're unrelated settings that live in different parts of the Exchange admin center and are frequently confused because both get called "calendar policy." Reminder settings are mailbox properties set via Set-MailboxCalendarConfiguration; sharing policies control what other people can see on a user's calendar and are managed separately.

Exchange Online has a default sharing policy that applies to all users in the organization, defining the default behavior when users share their calendars internally or with external users. Admins manage it by going to the Exchange Admin Center and navigating to Organization > Sharing, a completely different screen from anything involving reminders. Confusing the two is why "fix our calendar policy" tickets sometimes arrive at the wrong team — reminder timing and sharing visibility are configured, verified, and troubleshot independently.

Why doesn't an admin reminder policy make an iPhone ring?

Because Set-MailboxCalendarConfiguration only governs Outlook on the web and new Outlook — it has no path to the iOS notification system that decides whether an alert makes a sound, shows on the lock screen, or gets held back by Silent mode or Focus. Once a reminder leaves Exchange and reaches a phone, it becomes a standard notification, and standard notifications are muted the same way any other app notification is muted.

This is the gap documented across our troubleshooting library: see why Outlook reminders don't ring on iPhone even with a correct admin-side reminder time, and the broader explanation in why Outlook reminders differ between desktop and mobile. A tenant-wide 15-minute default reminder policy still produces a silent banner on a phone in Focus — the admin center has no setting for that, because it's an iOS permission problem, not an Exchange configuration problem.

Pealo addresses this by converting calendar events into native Outlook calendar alarms that actually ring using AlarmKit, which bypasses Silent mode and Focus the way an iPhone alarm does, regardless of what the Exchange reminder policy is set to upstream.

How do admins verify a reminder policy actually applied?

Run Get-MailboxCalendarConfiguration against the same mailbox and read back the exact properties that were changed, rather than assuming the command succeeded. One practical guide warns that admins should read back the same property that was modified, and not verify RemindersEnabled by looking only at DefaultReminderTime, or confuse WorkingHoursTimeZone with the mailbox's regional TimeZone setting.

A quick check pulls the three core fields at once: Select-Object RemindersEnabled, DefaultReminderTime, ReminderSoundEnabled shows whether reminders are active, the current default reminder interval, and whether reminder sounds are enabled. For bulk rollouts, spot-check a handful of mailboxes after the pipeline run rather than trusting a single success message, since filtered Get-Mailbox queries can silently exclude resource mailboxes or shared mailboxes depending on how the filter was written.