đź’ˇ Our Technical Review in summary
Summary
- Microsoft is introducing a new Exchange Online administrative policy to manage the “Use commas as recipient separators” setting.
- This update targets the New Outlook for Windows and Outlook on the Web (OWA).
- The policy is designed to help organizations—particularly those using “Last Name, First Name” contact formats—prevent the email client from incorrectly identifying a single contact as two separate recipients when a comma is typed.
- Rollout is scheduled to begin in early April 2026 and reach completion by mid-April 2026.
Impact
- Administrative Control: IT admins can now set a tenant-wide default for recipient delimiters, ensuring consistency across the organization.
- User Experience: By default, no changes will occur automatically. Existing behaviors are retained unless the admin applies the new policy.
- Client Behavior: If configured, the policy dictates whether a comma acts as a trigger to complete a recipient entry. This is critical for users who manually type names in formats that include commas.
- Overrides: Unless a restrictive policy is enforced to lock the setting, individual users can still manually toggle this preference within their Outlook settings.
Action Required
- Evaluate Necessity: Determine if your organization’s naming conventions or user workflows benefit from disabling commas as separators to reduce addressing errors.
- Technical Implementation: To configure the policy after the rollout, use the Exchange Online PowerShell module with the following command:
Set-OrganizationConfig -RecipientDelimeters <Boolean>. - Update Documentation: If your internal helpdesk or onboarding materials include instructions for Outlook configuration, update them to reflect the new centralized default.
- Communication: If you plan to enforce a specific setting that overrides previous user preferences, notify staff of the change to avoid confusion during email composition.
Microsoft Official Update
Service: N/A
Category: stayInformed
Severity: normal
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 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‑April 2026.
[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:
- 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.
