The Evolution of Exchange Online Toward High-Bandwidth
After nearly two years of development and testing, Microsoft is about to launch High-Volume Email (HVE) in general availability for Exchange Online. This solution addresses a major challenge for modern organizations: managing large volumes of emails in a shared environment like Microsoft 365.
Technical Context
Exchange Online is not designed to host mailboxes generating massive email traffic. Limitations such as the external throughput limit at the tenant level exist to protect shared infrastructure.
The Challenges of Volume in the Microsoft 365 Ecosystem
Microsoft 365 environments naturally impose throughput restrictions to maintain the stability of the shared service. These limitations include notably tenant traffic thresholds and external recipient limits. While Microsoft initially considered implementing a specific external throughput limit for mailboxes, this project was abandoned in January 2026.
HVE Solution Architecture
High-Volume Email is a distinct and paid service, built on top of Exchange Online, capable of processing several hundred thousand emails daily. This solution targets two main use cases:
- Massive internal communications between employees
- Automated notifications generated by business applications
Feature Evolution
Microsoft removed the ability to send to external recipients in 2025 to simplify HVE. External sends are now managed by Azure Email Communication Services (ECS).
General Availability and Pricing Model
The message center notification MC1243552 confirms the end of the preview period and the launch of general availability for the end of March 2026. Despite the usage-based billing model, Microsoft offers a promotional free period until May 2026.
Progressive Migration Strategy
The Microsoft 365 roadmap (reference 382633) details a multi-phase approach:
General Availability Phase
Official launch of HVE with all production features available by the end of March 2026.
Promotional Period
Free use of the service until May 2026 to allow organizations to test and validate their implementation.
Billing Activation
Implementation of the usage-based payment model starting in May 2026.
Integration with Business Applications
High-Volume Email is particularly aimed at line-of-business applications that need to send emails as part of their processes. Usage via PowerShell with the Send-MailMessage cmdlet remains similar to traditional methods for user or shared mailboxes.
Authentication and Technical Constraints
Currently, HVE supports basic authentication for SMTP submission, facilitating the integration of existing applications with minimal code changes. However, this functionality will be removed in September 2028.
Critical Deadline
All client submissions to Exchange Online will eventually need to use OAuth. The removal date for basic authentication for SMTP AUTH will be announced in the second half of 2027.
1# Example of sending via HVE with basic authentication2$credentials = Get-Credential3Send-MailMessage -From "hve@contoso.com" -To "team@contoso.com" -Subject "System Notification" -Body "Message" -SmtpServer "smtp.office365.com" -Credential $credentials -UseSslConfiguration and Deployment
The implementation of High-Volume Email requires special attention to conditional access policies. The Microsoft-managed policy blocking legacy authentication must be modified to exclude HVE accounts.
Resolution of Common Errors
The most common error during configuration concerns authentication:
15.7.57 Client not authenticated to send mail. Error: 535 5.7.139 Authentication unsuccessfulVerify Conditional Access Policies
Identify and modify policies blocking legacy authentication to exclude HVE accounts.
Configure Exceptions
Add HVE accounts to the exclusions of the relevant security policies.
Test Connectivity
Validate the configuration with test scripts before production deployment.
Economic Model and Cost Projections
Although Microsoft has not yet communicated the final pricing grid for HVE, a comparison with Azure Email Communication Services suggests a similar structure. For ECS, sending one million 0.2 MB average messages costs $274.
Evaluation Period
Take advantage of the free period until May 2026 to evaluate performance and calculate the projected costs for your organization.
Limitations and Strategic Considerations
Standard Exchange Online throughput restrictions exist for fundamental security reasons, including spam prevention and protection against tenant compromises. HVE and ECS's paid model naturally discourages malicious uses.
Alternatives and Competitive Ecosystem
If High-Volume Email does not fully meet organizational needs, several third-party services remain available. Microsoft's competitive advantage lies in native integration with the Microsoft 365 ecosystem, but this integration cannot compensate for major functional limitations.
Recommendations for Adoption
Organizations with regular needs for sending large volumes of internal messages should:
- Test HVE during the free promotional period
- Evaluate the impact on existing applications
- Plan migration to OAuth before the 2028 deadline
- Calculate projected costs based on current volumes
Useful Links
- Official High-Volume Email Documentation
- Azure Email Communication Services
- Microsoft 365 Roadmap - HVE
- PowerShell Example Script
- Azure Active Directory Error Codes
Glossary of Terms
High-Volume Email (HVE): Microsoft's paid service allowing the sending of large volumes of internal emails via Exchange Online.
Azure Email Communication Services (ECS): Azure solution dedicated to sending external emails in volume, complementary to HVE.
Basic Authentication: Authentication method using username and password, gradually replaced by OAuth.
SMTP AUTH: Authentication protocol for email submission via SMTP.
External Throughput Limit: Restriction on the number of emails that can be sent to external recipients.
OAuth: Modern authorization standard replacing basic authentication to secure access.
Conditional Access: Azure AD security policies controlling access to resources based on defined criteria.
