ChangeIntelIT change radar
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 · 7/9 advisories · checked 20:51 UTC Customize Public modeDiscuss ChangeIntel on Discord
MC1239176 Stay informedUpdated messageNew featureUser impactAdmin impact

Outlook: Delimiter setting admin policy

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.
Exchange Online
Microsoft 365 admin center

Rollout

Roadmap
557676

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 2 Jun 2026 mid-May 2026 → early July 2026
  • Seen 5 May 2026 April 2026 → mid-May 2026

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 June 2, 2026: We have updated the content and timeline. We are in the process of correcting an issue with setting the policy. We expect to complete in early July. Thank you for your patience.   Introduction We’re adding a new Exchange Online admin policy that gives admins more control over the default Mail Compose and Reply setting that determines whether commas are used as recipient separators. This message is associated with Microsoft 365 Roadmap ID 557676. When this will happen General availability (Worldwide): Rollout will begin in early April 2026 and complete by early July 2026 (previously mid-May). How this will affect your organization Who is affected Exchange Online administrators in New Outlook for Windows and Outlook for Web All users composing or replying to email in Outlook where no per‑user override is configured What will happen A new admin policy will be available to set the tenant‑wide default for “Use commas as recipient separators.” Admins can choose whether the default is on or off for all users. If the policy is in effect, all users will have their setting default to the admin's choice. Users may still toggle this setting in their Outlook client after the policy is set:  This update is especially useful for organizations whose contacts commonly use “Last name, First name” formats. No changes will occur automatically—tenants will retain existing behavior unless an admin modifies the policy. What you can do to prepare No action is required. If desired, you may configure the new admin policy after rollout if you want to establish a consistent default. You can set this value via Powershell with the command "Set-Organization Config -RecipientDelimeters <Boolean>." You may also consider the following actions:  Review your organization’s preferred recipient formatting conventions. Update internal documentation if your helpdesk or user‑training materials reference this setting. Compliance considerations No compliance considerations identified. Review as appropriate for your organization.

What changed

Between archive captures, newest first

  1. Updated May 5,June 2, 2026: We have updated the content and timeline. We are in the process of correcting an issue with setting the policy. We expect to complete in early July. Thank you for your patience.     Introduction We’re adding a new Exchange Online admin policy that gives admins … availability (Worldwide): Rollout will begin in early April 2026 and complete by mid-Mayearly July 2026 (previously mid‑April). mid-May). How this will affect your organization Who is affected Exchange Online administrators … can choose whether the default is on or off for all users. If the policy is in effect, all users will have their setting default to the admin's choice. Users may still changetoggle this setting in their Outlook client unless an admin enforces a after the policy that locks it:is set:  This update is especially useful for organizations whose contacts commonly use “Last …

  2. Updated March 19,May 5, 2026: We have updated the content.timeline. Thank you for your patience.  Introduction We’re adding a new Exchange Online … availability (Worldwide): Rollout will begin in early April 2026 and complete by mid‑April 2026.mid-May 2026 (previously mid‑April). How this will affect your organization Who is affected Exchange Online administrators …

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

    Updated March 19, 2026: We have updated the content. Thank you for your patience.  Introduction We’re adding a new Exchange Online admin policy that gives admins … How this will affect your organization Who is affected Exchange Online administrators in New Outlook for Windows and Outlook for Web All users composing or replying to email in Outlook where no per‑user … you can do to prepare No action is required. If desired, you may: may configure the new admin policy after rollout if you want to establish a consistent default. You can set this value via Powershell with the command "Set-Organization Config -RecipientDelimeters <Boolean>." You may also consider the following actions:  Review your organization’s preferred recipient formatting conventions. Update internal documentation if your helpdesk or user‑training materials reference this setting. Configure the new admin policy after rollout if you want to establish a consistent default. Compliance considerations No compliance considerations identified. Review as appropriate for your organization.

  4. · 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.

Shared roadmap ID 557676

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 20:51 UTC · 272 of 272 readable · 271 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.