HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
High Volume Email for Microsoft 365 Public Preview
Microsoft 365 is introducing High Volume Email (HVE) for large-scale internal communications, allowing up to 100,000 recipients per day at no cost during Public Preview. It integrates with business applications and will feature a dedicated page and reports in the Exchange admin center. Rollout begins April 2024. No immediate action is required for preparation.
Exchange Online is designed with email sending limits that are determined by three key factors: Recipient Rate Limit, Recipient Limit, and Message Rate Limit. We’re excited to announce High Volume Email (HVE) for Microsoft 365, which caters to customers who have needs beyond these limits.
HVE uses a transactional model, where cost is based on the number of sent emails. During Public Preview, HVE is provided at no cost, and allows up to 100,000 recipients per day per customer. HVE is specifically designed for large-scale internal communications, seamlessly integrating with business applications and devices to facilitate mass mailing needs.
This message is associated with Microsoft 365 Roadmap ID 382633.
When this will happen:
Preview: We will begin rolling out early April 2024 and expect to complete by late April 2024.
Worldwide: We will begin rolling out late September 2024 and expect to complete by early October 2024
How this will affect your organization:
A new page for HVE will appear under Mail Flow in the left-hand nav of the Exchange admin center. This page enables admins to create and manage Mail User accounts that are enabled for HVE. These accounts will use a dedicated SMTP endpoint for sending email using HVE.
Additionally, a new report for HVE will appear under Mail Flow Reports. The report provides an overview of HVE usage in your tenant, broken down by individual accounts. If more granular reporting is needed, an admin can request a more detailed report.
What you need to do to prepare:
No action is needed to prepare for this change. You may consider updating your documentation as appropriate.
Message ID: MC765811
