Updated June 2, 2026: We are in the process of correcting an issue with setting the policy. We expect to complete in mid-June. 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 mid-June 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.
- Users may still change this setting in their Outlook client unless an admin enforces a policy that locks it:
![(Updated) Outlook: Delimiter setting admin policy [MC1239176] 6 user settings](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- 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.
Source: Microsoft
<<< [MC1239176] Archive
Tooltip: View earlier revisions of this post
Latest Posts
- Dynamics 365 Project Operations – Post project invoice proposals using multithreaded batch tasks [MC1390348]
![Dynamics 365 Project Operations - Post project invoice proposals using multithreaded batch tasks [MC1390348] 2 pexels pixabay 144243](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) New entry point for “Create pages with Copilot in SharePoint” [MC1324284]
![(Updated) New entry point for "Create pages with Copilot in SharePoint" [MC1324284] 3 pexels ekamelev 1685594](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Amazon MSK now offers AI Agent Skills to help developers operate MSK efficiently and accelerate migrations to MSK

- AWS HealthOmics now supports Nextflow profiles

![(Updated) Outlook: Delimiter setting admin policy [MC1239176] 1 (Updated) Outlook: Delimiter setting admin policy [MC1239176]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-philippedonn-1133957-1024x683.webp)
![(Updated) Outlook: Delimiter setting admin policy [MC1239176] 6 user settings](https://cxcs.microsoft.net/static/public/messagecenter/neutral/d53d4d89-2cf9-4b09-8916-ad98fa64e98e/51360c8601e14324e4cd6d6a0a45e002a951a767.png)
![Dynamics 365 Project Operations - Post project invoice proposals using multithreaded batch tasks [MC1390348] 2 pexels pixabay 144243](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-pixabay-144243-150x150.webp)
![(Updated) New entry point for "Create pages with Copilot in SharePoint" [MC1324284] 3 pexels ekamelev 1685594](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-ekamelev-1685594-150x150.webp)


