HVE is mainly for internal messaging. It has some external capability but that’s not what it is designed for. If you want a service to handle things like sending newsletters out to customers, investigate ECS https://practical365.com/ecs-email-communication-services/

Ok not great, using it like you are through powershell is fine, but I know our network team has firewall alerts fire off mostly internal but to maybe 10 or 11 external isp emails.

To me that falls in the category of what HVE is used for, but then were already over the limit. I dont know how they decided on this. Pretty sure when I asked on the microsoft page they said they have no plans to change this in the general release.

You can’t send to more than 10 external recipients per minute. But wait until the software is GA to see what limits Microsoft sets at that point. I will say that I did not find the limitation to be a problem because I built the necessary pauses into PowerShell scripts to send messages. Each external recipient counts as 1 recipient, so sending one email to 200 recipients is sending to 200 recipients.

You just cant send more than 10 different external emails in under a minute?

I just want to confirm that as the rest of our staff has now asked about this. We have a very small need as a post secondary to send some external mail using a smtp relay (currently uses office 365 which will be depreciated). Most is internal and in a few years it will be almost 100% internal. But we just want to understand the exact limitation so hopefully my understanding above is correct.

You’ll have to wait for GA. I don’t work for Microsoft, so I can’t commit to anything on their behalf.

CA requires an app identity to apply restrictions. Maybe this will come through modern authentication for SMTP connections to HVE.

As far as i understood from first community feedback there ist currently no possibility to restrict the usage /login of HVE Accounts to trusted IPs via Conditional Access. We implemented those restrictions for our decentralized printer locations (scan2email) for the SMTP Client Auth submission (Basic Auth) method. Any info on this topic would be appreciated. Maybe we will have more info on GA.

The limitations will be different when HVE is GA. Don’t judge HVE capacity to send email based on the preview.

HVE accounts and passwords are like other Entra ID accounts. It’s up to you how to maintain/expire passwords.

For sure we don’t send a lot external but some get fired off to external addresses, the scary thing though is 10 messages per minute, hopefully the odd application we house does not exceed this, most is for internal I just can’t say there’s for sure a scenario where it might not exceed it. Wonder why this was not documented the only thing mentioned is 2000 per day.

Also do you know if hve accounts passwords will expire?

I was hoping this was a solution to some of our programs using office 365 smtp basic auth but seems there’s some real limitations.

It’s a preview, so some artificial limitations exist in the current impleementation. Also, HVE is intended more for internal than external communications. There is no rate limit for internal email, and the limit for external email emphasizes the target HVE is intended to serve.

Yes. in Powershell, it’s the Start-Sleep cmdlet. See the example script referenced in the article.