High Volume Email: Continued support for Basic Authentication & other important updates

A) This is very confusing.  We have a solution named "High Volume Email" intended for sending email to internal recipients only.
And you have "Azure Communication Services email" for sending high volume email to external recipients.
I feel like Microsoft purposefully names their product to confuse customers.  Ironic part is it confuses their support engineers as well.

B) So if a client has a security and safety system that sends an email notification, to external recipients, in case of fire or break-in they need to sign up for the  "Azure Communication Services email"?  A solution that Microsoft needs 5 web pages to explain the solution and how to implement it.

I understand there are some entities out there abusing the heck out if Microsoft's email solution, but that doesn't mean you should treat all of your customers like this.

C) Thanks for having an HVE guide that says it can be used to send to external recipients (<2k / day) and then changing that after we get several customers migrated over from the old smtp.office365.com solution. (extreme sarcasm and frustration here).