It's not designed for effective communication.
Here is a previous comment from k_sze about it. This is for a security process, so there is no excuse.
https://news.ycombinator.com/item?id=30368431
> MFA fatigue wouldn't be such a big problem if their MFA and SSO implementation was not so utter shit.
> Whenever I get a signin prompt, there is literally no way to tell what I'm signing in for.
> When the MS Authenticator app receives a MFA request notification, there is, yet again, no way to tell what service the request is for.
> To add insult to injury, when I need to signin again for a SharePoint guest account, it consistently fails to correctly redirect me back to the SharePoint folder.
> Microsoft's MFA is just security theatre. Take MS Teams for instance. Why does it ask me to sign in again, and yet still allow me to read messages that are already on the screen? Worse yet, the MS Teams desktop app can still receive new message notifications and display them while I have not re-logged in yet.
"How to use additional context in Microsoft Authenticator app notifications (Preview)": https://docs.microsoft.com/en-us/azure/active-directory/auth...
... and:
"How to use number matching in multifactor authentication (MFA) notifications (Preview)": https://docs.microsoft.com/en-us/azure/active-directory/auth...
But note the "PREVIEW" status, which seems to be the permanent state of affairs for any Microsoft security feature.
This doesn't excuse Microsoft in any way, but for any customers that are security conscious, at least now there are some options!
Our team used WebEx before, which was pretty bad, IMO, but some of that was probably due to it not being as tightly integrated as Teams was (we're a MS place).
The one thing I agree is bad and irritating is the inboxing. I'll be actively conversing on my PC and suddenly my phone will regurgitate the last 20 messages.