https://www.abc.net.au/news/2020-06-01/scammers-stealing-tho...
Also the fact that when you ask your login to be remembered the will just show you the email at the next login, without telling you if it's the personal or work account.
It is the worst login experience Iv've ever had, bar none, I am constantly amazed how they could ship that and always wonder what hellish dungeon of reasons there must be behind the decision to keep it as it is.
Yes, this can be confusing.
So you can have two accounts, say for ([email protected], Microsoft Account) and ([email protected], Contoso AD) - and there is no collision and no possible confusion on the system end. All the confusion is on the human end.
And there is a lot of confusion on the human end :)
However your organization may then do a deal with MS for Azure, or MSDN subscriptions, etc. And they’ll issue a login with the same email* address [email protected] — you now have two accounts tied to the same email, one which you created by yourself and one which your IT department created for you. There’s no way for you to change this second one. Typically authentication for the second one will happen via your org’s single sign on.
So the answer to “is this account personal or issued by your IT dept” really means — did you create the account yourself? Or was it provisioned for you by IT?
* Many orgs by default don’t use email to log in. Instead a “username” like jsmith is used instead. However while interfacing with Azure it seems to be a best practice to use email.
I had a family tech support session on this exact issue last week. A relative cleared her cookies and found her saved email and password for Facebook were logging her into a profile she'd never seen before. At some point Facebook had decided [email protected] and [email protected] were the same thing. We got around the issue by logging in using her account name gleaned from someone on her friends list.
Edit: sendmail and qmail, too, apparently: https://www.cs.rutgers.edu/~watrous/plus-signs-in-email-addr...
Easier to remember than a username because it's guaranteed to not be taken, so you can use the same email everywhere: [email protected]. Where as "alice" probably is taken.
Also should work with any email provider, it's part of the standard.
If the intent is to allow two people to have independent accounts even while using an email they both control, offloading that to the email protocol seems broken to me. It's the exact same email address from the perspective of security. Anything coming after the plus sign should be ignored for the DB key, but kept around for sending emails, so it can still be used for filtering those emails (for convenience, not security). So they could sign up either as
alice <[email protected]>
bob <[email protected]>
or as alice <[email protected]>
bob <[email protected]>
but that difference should only ever matter for their email filtering, not for identifying them.I think the logical next step is to give them the same password and see how bad my foot hurts afterwsrd.
I've actually built a system which did this years ago, over our initial protestations, and the reasoning went like this:
Our client (this was a white label product) has lots of elderly couples as customers, these are our end users and although they're on the Internet (makes sense, this is after all a web site you've white labelled so if you have customers without Internet that's a red flag right there) they only have one email address between them. So some end users want two accounts, but with one email address.
This made the login procedure a bit hairy and obviously there are scary corner cases for things like change password (Alice decides to use the same password as her husband Bob, now we can't tell their accounts apart!) but we felt that arguing with clients about why they should do Single Sign On (and thus eliminate the separate login for our white label product altogether) was more valuable than trying to change old people's minds about what constitutes a reasonable thing for two people to share.