The entry is marked In development. It targets a preview in December 2026 and general availability in March 2027 for the Worldwide (Standard Multi-Tenant) cloud. Microsoft's roadmap describes its dates as estimates that can change, so treat them as plans rather than promises.
What the roadmap entry says
According to the roadmap record:
- Scope: HVE currently sends only to recipients inside your organization. External Sending would add delivery to outside recipients such as customers and partners.
- Intended use: Operational and transactional mail, including notifications, alerts, receipts and required communications. The entry says the feature is not meant for marketing campaigns.
- How mail is sent: Apps and devices submit mail over SMTP and authenticate as an HVE account.
- Admin control: External sending is off by default. Admins turn it on for specific HVE accounts with a cmdlet. The entry doesn't name the cmdlet.
- Reputation safeguards: Throttling, quotas and suppression of problem recipients are built in.
- Billing: Charges are based on usage, per external recipient.
Summary: Microsoft plans to let selected HVE accounts send transactional mail outside the tenant. Each account has to be opted in, and external recipients are billed individually.
Why this matters: Microsoft removed this capability once already
HVE has already sent mail to external recipients once before. When Microsoft announced the public preview, its Exchange team described HVE as a service designed primarily for line of business applications and other high-volume SMTP Auth submissions that enables you to send internal messages beyond the current limits of Exchange Online. The preview limits listed External recipients · 2,000 per day (per tenant). Even then, Microsoft told customers to limit the volume to external recipients, as Azure Communication Services provides the solution for high volumes of external email.
Microsoft later took the feature away. Practical365 reported at the time that the Exchange Online High Volume Email (HVE) solution will only deliver messages to internal recipients from June 2025, and that Azure ECS is now the sole offering for sending large volumes of email to external recipients. The same outlet noted that some will say that Microsoft removed external email from HVE to force customers to pay for ECS. Petri also reported that the preview previously allowed up to 2,000 external recipients per day before Microsoft limited GA to internal recipients.
The current Microsoft Learn page for HVE still says external sending is unsupported. It lists the recipient scope as internal recipients within the tenant only, and it says HVE accounts cannot be used for external email delivery. Its comparison table marks HVE "No" for relaying to the internet through Microsoft 365, while SMTP client submission and SMTP relay are both marked "Yes." Microsoft's Exchange team takes the same line in its FAQ on tenant outbound limits, which says HVE is designed for sending high-volume email to internal recipients, not external recipients.
The roadmap item reverses that position, at least partly. The earlier preview had a simple daily external cap. The new design adds features found in commercial mail services: recipient suppression, quotas, a ban on marketing use, and billing for each external recipient.
Summary: Microsoft is restoring a capability it removed in mid-2025, this time with more safeguards and a stated restriction to transactional mail.
How HVE works today
External Sending builds on the existing service, so the current setup is the starting point. Microsoft Learn documents the following:
| Setting | Current HVE (internal only) |
|---|---|
| HVE accounts per tenant | Up to 100 |
| Recipients per message | Up to 50 |
| Max message size | 10 MB |
| Recipient/message rate limit | None listed |
| Connections | 100 concurrent per IP, or 250 authenticated per tenant |
| SMTP endpoint | smtp.hve.mx.microsoft (recommended); smtp-hve.office365.com slated for deprecation |
| Port / TLS | 587, TLS required |
| Authentication | HVE account credentials or OAuth token |
| Cloud | Worldwide (standard multi-tenant) |
Some other details from the documentation:
- Account type: HVE accounts are mail-enabled user objects, not mailboxes. They need no Microsoft 365 license and cannot receive mail. If recipients need to reply, set a Reply-To address with
Set-HVEAccountSettings. - Authentication: Microsoft recommends OAuth. If Security Defaults are enabled in Microsoft Entra ID, basic authentication is disabled, so HVE can only authenticate with OAuth.
- Billing setup: Each HVE account needs a Microsoft 365 pay-as-you-go billing policy tied to an Azure subscription. An account without a valid policy shows "Not active" and cannot send.
- Current price: HVE costs $0.000042 per expanded delivered recipient, which works out to $42 per million. Members of distribution lists are counted after the list is expanded.
Important: these are the limits and prices for internal HVE. The roadmap entry doesn't say whether the 50-recipient cap, connection limits, endpoint or $42-per-million rate will apply to external delivery. It only says external sending will be billed per external recipient. Don't build a budget on the internal rate yet.
Questions the roadmap entry leaves open
The roadmap entry leaves out several things admins will need:
- The cmdlet. It isn't named. A parameter on
Set-HVEAccountSettingsseems likely, but that is a guess. - Quota and throttle values. The entry promises them but gives no numbers.
- Suppression rules. It doesn't say what causes a recipient to be suppressed (hard bounces, complaints or both) or how to remove a suppression.
- Billing details. There is no price, and no word on whether bounced, retried or suppressed messages are charged.
- Relationship to tenant outbound limits. Microsoft's FAQ on the Tenant External Recipient Rate Limit (TERRL), the tenant-wide daily cap on external recipients, currently says HVE traffic doesn't count against that quota because HVE is internal-only. It's unclear whether that changes once HVE can reach external recipients.
- Sovereign clouds. Only Worldwide multi-tenant is listed.
HVE vs. Azure Communication Services: what to do now
For now, Microsoft's guidance for devices and apps that need to reach both internal and external recipients still points to Azure Communication Services Email. The roadmap doesn't say HVE External Sending will replace ACS. Expect the two to overlap, with HVE covering Exchange-administered transactional workloads such as scanners, line-of-business notifications and receipts, and ACS remaining the developer-oriented option.
Third-party email vendors have been pitching to these same customers. Retarus, for example, says that specialized providers concentrate on deliverability to external recipients. Keep in mind that the vendor sells a competing service.
A sensible plan before the December preview:
- Inventory apps and devices that currently send external mail through SMTP AUTH on user mailboxes, through SMTP relay or through ACS.
- Sort the mail into transactional and marketing. Only transactional mail fits the stated scope.
- Prepare OAuth for the apps that will use HVE, particularly if Security Defaults are on.
- Check your billing setup. HVE already needs pay-as-you-go billing linked to an Azure subscription.
- Review SPF, DKIM and DMARC for the domains your HVE accounts send from. External recipients' mail systems will check them in a way internal delivery never did. (This advice comes from general mail-administration practice, not from Microsoft's roadmap.)
Analysis
Microsoft pulled external sending from HVE in 2025 and is now putting it back, this time with suppression lists, per-recipient billing and an explicit ban on marketing mail. That suggests Microsoft wants to offer outbound mail on its own terms instead of watching tenants overload user mailboxes and run into TERRL. For admins, it could remove a second service from the printer-and-ERP problem.
The roadmap entry still leaves out the parts that decide whether the feature is practical: the limits, the price and how suppression works. The preview is due in December, so those answers may arrive soon. Until then, HVE remains internal-only, and the current Microsoft Learn documentation says so.
References
- Exchange: Enable High Volume Email (HVE) for External Recipients Microsoft 365 Roadmap · 2026-11-20T23:20:27.871175Z
- Stricter sending limits for Exchange Online: What the new Microsoft rules mean for your high-volume emailing retarus.com
- What Is Exchange Online HVE used for? petri.com