I sent an email from BC Online "Compose email" as a BC licensed user from our O365 "noreply" shared mailbox to an external recipient, but it arrived as I had sent it under my name. This is an unwanted bug.

I do have SendAs permissions, and I can go to Outlook Web, switch the sender to the shared mailbox with the same recipient, and then I receive it from noreply as the sender.

Why is BC acting like that?

Second thought: since SMTP with basic AUTH was announced to be turned off for M365 tenants, the email configuration for BC is a nightmare.

We need the customer's IT to configure SendAs permissions to that shared mailbox for all users with a BC license (it doesn't work with a security group; it must be done one by one) - I suspect because it verifies the Exchange Online license. Getting GDAP for Exchange config is a dream; without it is all explanation handled by email, and it feels so unnecessary.

There is an option to set multitenant app registration, but that is also a heavy configuration, and it needs to be redone at the latest in 730 days. Last but not least: email config is done per company in each environment - it is always missing somewhere.

Could a BC team think of a built-in email solution or some other workflow for this?

Vote to show that you have the same difficulties.