For latest updates on HVE, please see this post as well as this post.
Today we’re thrilled to announce the public preview of High Volume Email (HVE) for Microsoft 365. HVE is a new service designed...
Updated May 06, 2025
Version 5.0
Blog Post
josef-check Thank you for your questions:
- Is there any way to configure the authentication for this using conditional access? We will not allow SMTP Auth for any standard mailbox, but might want to allow it for HVE. Does the other Endpoint have a new AppID?
Should not be any different than configuring conditional access policies for standard users/mailboxes. We tested and applying CA policies to HVE accounts works the same. App id for Exchange is the same as well (00000002-0000-0ff1-ce00-000000000000); confirmed via Azure sign-in logs.
- The limit for 20 Accounts seems very low for large tenants. This might be fine for beta/testing, but for GA, we might want more accounts in order not to share Passwords to much between services/devices.
For GA we plan to increase the limit, but the number is not defined yet. If it will be needed for the Preview, we can apply exceptions for specific Customers.
- How is password management working? Does this integrate with existing password management policies?
Password management for HVE Accounts is the same as any other user type in Exchange.
- GraphAPI Integration: Is there any way to get reports about usage/logins using Graph? Also, can we create these accounts using Graph?
Yes, you can get usage report via Graph. No, we do not support HVE accounts creation using Graph.
- Does logging in the HVE Endpoint work using normal user credentials?
No, only HVE Accounts can authenticate against the HVE Endpoint.